Delay

[masterk]

Hi,

i have one question / problem. I bougt the Hotas Warthog. It is really great. I have setup up it with FSUIPC in FS9. All Axis works perfect :). .

But I have the problem that for example when i programmed a key for example "Shift+D" the command will be send for a long time. Can i disable this feature. I want only that the command will be send short and that was it ;). Keypress not to be held is enabled.

Thanks and have a nice day.

Christian

[Pete Dowson]

But I have the problem that for example when i programmed a key for example "Shift+D" the command will be send for a long time.

Sorry, what do you mean "send for a long time"?

Are you taslking about probramming a jpoystick button to send a keypress, or a keypress to send something else?

Can i disable this feature. I want only that the command will be send short and that was it . Keypress not to be held is enabled.

I need to know what you are doing first. If you are using the keyboard are you sure it isn't simply the keyboard's automatic repeat action you are seeing? FSUIPC can't stop the keyboard repeating.

Regards

Pete

[masterk]

Perhaps i can explain it in other words:

It is not so easy.

I found out that the command must be send for a longer time. For example i send the command trough the Joystick (shift+A) in FS and when i am changing to Word all i wrote is like this AJSDNSNS. In great letters. After round about 15 seconds i wrote in small letters. So i found out that the command must be send for a longer time than only for once. (I have enabled keypress not to be held)

Another problem is that i have for example Setup Shift+A on the Joystick key. With this combination i start the fuel lever. First time i push it it works without a problem. When i push the button again nothing happens. I must first push another button that is programmed through the FSUIPC before this button will work again. The button is a toggle.So it is alwas on when i switch it. I didn´t use the keyboard. I programmed the buttos for the joystick.

Best regards

Christian

[Pete Dowson]

Perhaps i can explain it in other words:

Well, the first step is to say what you are doing. Is this key press programming or joystick button programming. What are you assigning to? Basic information like that is missing.

I found out that the command must be send for a longer time. For example i send the command trough the Joystick (shift+A) in FS and when i am changing to Word all i wrote is like this AJSDNSNS. In great letters. After round about 15 seconds i wrote in small letters. So i found out that the command must be send for a longer time than only for once. (I have enabled keypress not to be held)

Er, now I am really confused! WHAT "command" are you sending? How are "joystick" and Shift+A related? Where does Word come into this?

Sorry, you need to tell me what you are actually doing. If you are pressing a joystick button, tell me that. Then tell me how you programmed it in FSUIPC, if that is actually what you are doing. Or tell me what keys on the keyboard you are pressing and how you programmed those.

Another problem is that i have for example Setup Shift+A on the Joystick key. With this combination i start the fuel lever. First time i push it it works without a problem. When i push the button again nothing happens. I must first push another button that is programmed through the FSUIPC before this button will work again. The button is a toggle.So it is alwas on when i switch it. I didn´t use the keyboard. I programmed the buttos for the joystick.

So, what is Shift+A supposed to do?

If you have set up a button to act like a toggle, then when you press it it either goes off to on, or on to off (unlike a button which goes off-on-off with one press). If you've only programmed FSUIPC to do anything when it is pressed, then obviously it will only do it on every alternate pressing. If you want to use a toggle like a normal button you have to program the press and the release, of course.

Regards

Pete

[masterk]

Well, the first step is to say what you are doing. Is this key press programming or joystick button programming. What are you assigning to? Basic information like that is missing.

It is joystickbotton prgramming. The combination is setup in the ifly section. There i have setup that shift+A will be for the fuel lever. Behind the button i programmed also Shift+A in the FSUIPC in the Button and switches section.

My big problem is that when i press the joystick toggle first time it works. When i took the toogle again it doesn´t work. First i musst push another toggle or button. I have setup the combination in both fields in the FSUIPC. For push and release.

Christian

[Pete Dowson]

It is joystickbotton prgramming. The combination is setup in the ifly section. There i have setup that shift+A will be for the fuel lever. Behind the button i programmed also Shift+A in the FSUIPC in the Button and switches section.

My big problem is that when i press the joystick toggle first time it works. When i took the toogle again it doesn´t work. First i musst push another toggle or button. I have setup the combination in both fields in the FSUIPC. For push and release.

Well, if FSUIPC is programmed to send Shift+A when you switch the toggle on and also when you switch it off, it will be doing so. You need to find out why that iFly aircraft doesn't recognise two separate identical key presses. FSUIPC doesn't care how many times you press and release a button, if it sees it being so operated it will do what you ask every single time.

Just to check you could try programming a different keypress of the release. Then, if the aircraft sees each press (or toggle on) you know that it is the aircraft which is in error. If you still have to press another button first, instead, then you know there is something wrong with the joystick or its driver.

Also you can check things using the logging facilities in FSUIPC. Enable Button/key logging, the press / release the button or operate the toggle and you will see what happens in the FSUIPC log file.

Regards

Pete

[masterk]

Hi,

here is the log. Perhaps you can see an error. I have pushed the toggle twice.

[Continuation log requested by user]

Module base=61000000

WeatherReadInterval=4

LogOptions=00000001

3978993 System time = 09/05/2011 16:00:25, FS2004 time = 15:58:28 (13:58Z)

3981271 Button changed: bRef=0, Joy=1, Btn=23, Pressed

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3981271 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

3981271 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

3981271 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

3981271 .. Key not programmed -- passed on to FS

3981318 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

3981318 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

3981318 .. Key not programmed -- passed on to FS

3984906 SendKeyToFS(00040041=[shft+A], KEYUP) ctr=0

3984906 Sending WM_KEYUP, Key=65 (Scan code 30), Ctr=1

3984906 KEYUP: VK=65, Waiting=0

3984952 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1

3984952 KEYUP: VK=16, Waiting=0

3986934 Button changed: bRef=0, Joy=1, Btn=23, Released

3986934 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3986934 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

3986934 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

3986934 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

3986934 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

3986934 .. Key not programmed -- passed on to FS

3986996 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

3986996 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

3986996 .. Key not programmed -- passed on to FS

3987199 KEYDOWN: VK=192, Waiting=0, Repeat=N, Shifts=1

3987199 .. Key not programmed -- passed on to FS

3987339 KEYUP: VK=192, Waiting=0

3988104 KEYDOWN: VK=192, Waiting=0, Repeat=N, Shifts=1

3988104 .. Key not programmed -- passed on to FS

3988213 KEYUP: VK=192, Waiting=0

3992596 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=5

3992596 .. Key not programmed -- passed on to FS

3992752 KEYUP: VK=18, Waiting=0

3995404 *** Entered Buttons option page ***

3995420 FirstButtonChange res=00000620 (0.6, 32)

3995451 FS Control Sent: Ctrl=66387, Param=0

3995451 FS Control Sent: Ctrl=66388, Param=0

3995451 FirstButtonChange res=0000011B (0.1, 27)

3998259 *** Exiting Buttons option page ***

[Pete Dowson]

here is the log. Perhaps you can see an error. I have pushed the toggle twice.

It looks fine. Here's where it sees your button being Pressed:

3981271 Button changed: bRef=0, Joy=1, Btn=23, Pressed

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3981271 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

which it correctly interprets as a request to send Shift+A. Then here's the Shift being pressed:

3981271 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

3981271 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

3981271 .. Key not programmed -- passed on to FS

and then the A:

3981318 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

3981318 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

3981318 .. Key not programmed -- passed on to FS

then 3 seconds later (because the button was still down I assume?) the KEYUP signals for first the A then the Shift:

3984906 SendKeyToFS(00040041=[shft+A], KEYUP) ctr=0

3984906 Sending WM_KEYUP, Key=65 (Scan code 30), Ctr=1

3984906 KEYUP: VK=65, Waiting=0

3984952 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1

3984952 KEYUP: VK=16, Waiting=0

That is all correct.

Here, another 2 seconds later is where you released or turned off the button:

3986934 Button changed: bRef=0, Joy=1, Btn=23, Released

3986934 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3986934 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

3986934 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

and again the same sequence, exactly (to start with), is sent:

3986934 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

3986934 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

3986934 .. Key not programmed -- passed on to FS

3986996 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

3986996 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

3986996 .. Key not programmed -- passed on to FS

BUT before it was completed with the KEYUPs, you or something else (not FSUIPC) is sending another keyprress twice -- for 192, which is the '@ key on my keyboard (ma be different in non-UK keyboards). This is arriving within 250 mSecs of you operating the "off" toggle of that switch, so if you didn't touch the keyboard yourself it sounds like you have some other software acting for your joystick switches/buttons.

3987199 KEYDOWN: VK=192, Waiting=0, Repeat=N, Shifts=1

3987199 .. Key not programmed -- passed on to FS

3987339 KEYUP: VK=192, Waiting=0

3988104 KEYDOWN: VK=192, Waiting=0, Repeat=N, Shifts=1

3988104 .. Key not programmed -- passed on to FS

3988213 KEYUP: VK=192, Waiting=0

Whatever's doing it is sending it twice in quick succession. I think that key is normally associated with the ATC window -- to call it and close it.

This interference in the keyboard sequence is causing the previous pressed Shift+A to be never released -- I guess the Windows routine discarded it when it saw the interfering key presses.

Check with a different aircraft loaded, like a default. That should tell you whether it is related to the aircraft or something else, something processing your buttons in parallel with FSUIPC.

Regards

Pete

[masterk]

Hi,

It looks fine. Here's where it sees your button being Pressed:

3981271 Button changed: bRef=0, Joy=1, Btn=23, Pressed

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3981271 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

which it correctly interprets as a request to send Shift+A. Then here's the Shift being pressed:

3981271 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

3981271 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

3981271 .. Key not programmed -- passed on to FS

and then the A:

3981318 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

3981318 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

3981318 .. Key not programmed -- passed on to FS

OK. But how long will the shift key will be pressed. I think that is my problem that the shift key would be send to long. With the ATC i found out. That was I ;).

So i have made an test. The shift key wouldn´t be relased. That is the big problem. But i didn´t know hoy to fix it.

Christian

[Andydigital]

What version of FSUIPC are you using?

Do you have some software installed for the HOTAS that came included with the joystick that lets you program the buttons and switches to do various things? If you have installed the software have you tried disabling this joystick software, it may be interfering with FSUIPC in some way.

[Pete Dowson]

OK. But how long will the shift key will be pressed. I think that is my problem that the shift key would be send to long.

as the log showed quite clearly, the Shift key is released immediately after the A key. Why do you think otherwise?

So i have made an test. The shift key wouldn´t be relased.

Where is the log showing this? If this happened then many thousands of users would be reporting problems, including myself!

So far it is looking like a problem of the aircraft. But show me a log without you pressing the '@ key in the middle!

Pete

[masterk]

Hi,

could you please check for me if this is OK. . I have made 2. If it is OK it is the Addon.

first

[Continuation log requested by user]

Module base=61000000

WeatherReadInterval=4

LogOptions=00000001

190695 System time = 10/05/2011 14:02:45, FS2004 time = 15:00:29 (13:00Z)

190695 WeatherOptions set, now 4000B6A7 (timer=0)

193519 Button changed: bRef=0, Joy=1, Btn=23, Pressed

193519 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=H1,23,K65,9

193519 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

193519 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

193519 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

193519 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

193519 .. Key not programmed -- passed on to FS

193566 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

193566 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

193566 .. Key not programmed -- passed on to FS

197778 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=5

197778 .. Key not programmed -- passed on to FS

197903 KEYUP: VK=18, Waiting=0

Second

LogOptions=00000001

543414 System time = 10/05/2011 14:08:38, FS2004 time = 15:05:39 (13:05Z)

545660 Button changed: bRef=0, Joy=1, Btn=23, Pressed

545660 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=H1,23,K65,9

545660 SendKeyToFS(00000041=[A], KEYDOWN) ctr=0

545660 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

545660 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

545660 KEYDOWN: VK=65, Waiting=0, Repeat=Y, Shifts=1

545660 .. Key not programmed -- passed on to FS

560012 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=5

560012 .. Key not programmed -- passed on to FS

560090 KEYUP: VK=18, Waiting=0

Thank you very much for your help

Christian

[Pete Dowson]

could you please check for me if this is OK. . I have made 2. If it is OK it is the Addon.

Instead of looking at the logs of keys being pressed, I'm looking at something very stange in the way you are programming your switch or button:

These lines

193519 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=H1,23,K65,9

193519 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

show that you are telling FSUIPC to hold the keys down (H) when the button is pressed or the switch is on. Why? It won't release the keys pressed until you release the button, and if it is a toggle switch that could be a looooonnnnggg time, could it not?

Worse, you've also programmed it to press Shift+A again when the button or switch is released or off. Why? If the keys have been held down till then, as they will have been, what do you think that does?

sorry if i missed these points before, but we were concentrating on the resulting keys. I hadn't realised you were doing odd experimental things with the programming!

[LATER]

Ah, I just looked at your earlier log, and you weren't doing such a strange thing then. Look:

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

which is okay -- sending Shift+A once when pressed, once when released. Why did you change it? If you want it held you shouldn't really try to send another keypress on release. That makes no sense.

Regards

Pete

[masterk]

Hi,

show that you are telling FSUIPC to hold the keys down (H) when the button is pressed or the switch is on

I have added a picture how i have set it up. I didn´t mark this opton or must i mark it? It is a toggle. When i switch it is on until i switch it off.

Worse, you've also programmed it to press Shift+A again when the button or switch is released or off. Why? If the keys have been held down till then, as they will have been, what do you think that does?

This i could change and try. I have setup in the ifly menu that i can use shift+A to start and stop the fuel lever. Perhaps I think to easy in this way ;).

Best Regards and thanks

Christian

[Pete Dowson]

I have added a picture how i have set it up. I didn´t mark this opton or must i mark it? It is a toggle. When i switch it is on until i switch it off.

You need to have it checked to stop it holding. As it says, in fact.

It was checked on okay in your previous logs, but the log with 2 tries you asked me to check most certainly had it on. It doesn't make sense to me to have it held -- though perhaps if you explained what you want this button or switch to do I'd understand better. First is it a button or an on/off toggle switch? What do you actually want it to do for you?

This i could change and try. I have setup in the ifly menu that i can use shift+A to start and stop the fuel lever.

Do you mean the start levers, the ones on the 737 just this side of the throttle levers? So you've programmed the same keystroke to toggle between "cutoff" and "idle"?

In that case you certainly do NOT want it held so you need the option to not hold it checked. You just want one keypress to set it one way and another to set it the other way. If you are using a press-button then you should only program the press, so the same button does both. If you are using a toggle switch then you program it as you did in the earlier logs and as not as you just showed in the picture.

I've not yet seen a complete log with it done properly and without the '@ keypress getting in the way.

Regards

Pete

[masterk]

Hi,

Sorry i didn´t understand that: You need to have it checked to stop it holding. As it says, in fact.

You mean that i have to enable Keypress not to be held.??

Do you mean the start levers, the ones on the 737 just this side of the throttle levers? So you've programmed the same keystroke to toggle between "cutoff" and "idle"?

Yes it is a togle to switch from cutoff to idle. That is correct. But i can program it in otherway and will try this.

I've not yet seen a complete log with it done properly and without the '@ keypress getting in the way

The keypress if from multicrew experince i think. It is a voice software. I didn´t switch a other toggle.

Sorry for a non native speaker it isn´t so easy. I have added a picture how i have setup it now.

Christian

[Pete Dowson]

You mean that i have to enable Keypress not to be held.??

Yes, if it is is a toggle switch you are using, then of course you don't want the keys held down. If they are held down all the time the toggle is in a specific position, the Shift and the A will be pressed down all that time. So no other use of A will work and nothing can be sent unshifted. Furthermore, when you switch the toggle the other way nothing will really happen since the keys are already held down. They will hjust release but the aircraft will not receive a new press -- how can it, there's no new press!

Regards

Pete

[masterk]

So,

i have changed it. I have now shift+a and h as commands. That works fine :)

13772938 System time = 10/05/2011 17:49:08, FS2004 time = 16:34:52 (15:34Z)

13775465 Button changed: bRef=0, Joy=1, Btn=23, Pressed

13775465 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

13775465 SendKeyToFS(00000048=[H], KEYUP) ctr=0

13775465 Sending WM_KEYUP, Key=72 (Scan code 35), Ctr=1

13775465 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

13775465 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K72,8

13775465 KEYUP: VK=72, Waiting=0

13775512 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

13775512 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

13775512 .. Key not programmed -- passed on to FS

13775559 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

13775559 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

13775559 .. Key not programmed -- passed on to FS

13786885 Button changed: bRef=0, Joy=1, Btn=23, Released

13786885 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

13786885 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K72,8

13786885 SendKeyToFS(00040041=[shft+A], KEYUP) ctr=0

13786885 Sending WM_KEYUP, Key=65 (Scan code 30), Ctr=1

13786885 SendKeyToFS(00000048=[H], KEYDOWN) ctr=1

13786885 KEYUP: VK=65, Waiting=0

13786931 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=2

13786931 KEYUP: VK=16, Waiting=0

13786994 Sending WM_KEYDOWN, Key=72 (Scan code 35), Ctr=1

13786994 KEYDOWN: VK=72, Waiting=0, Repeat=N, Shifts=0

13786994 .. Key not programmed -- passed on to FS

13788507 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4

13788507 .. Key not programmed -- passed on to FS

13788663 KEYUP: VK=18, Waiting=0

Interessting is that when i start the Enginge with the toggle(combination behing shift+a) i am not able to press for example ö on my keyboard after put the toggle. I must first push the shift on my keyboard. The ö opensfor the atc window . The same is with the light. (L button) when i push l it doesn´t work. I must fist push shift on the keyboard release it and the it works. Here is the log therefor. And so i think that the shift will not be released.

14122833 System time = 10/05/2011 17:54:58, FS2004 time = 16:40:11 (15:40Z)

14126015 Button changed: bRef=0, Joy=1, Btn=23, Pressed

14126015 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

14126015 SendKeyToFS(00000048=[H], KEYUP) ctr=0

14126015 Sending WM_KEYUP, Key=72 (Scan code 35), Ctr=1

14126015 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

14126015 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K72,8

14126015 KEYUP: VK=72, Waiting=0

14126062 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

14126062 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

14126062 .. Key not programmed -- passed on to FS

14126124 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

14126124 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

14126124 .. Key not programmed -- passed on to FS

14134595 KEYDOWN: VK=192, Waiting=0, Repeat=N, Shifts=1

14134595 .. Key not programmed -- passed on to FS

14134907 KEYUP: VK=192, Waiting=0

14139525 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=5

14139525 .. Key not programmed -- passed on to FS

14139696 KEYUP: VK=18, Waiting=0

14152286 KEYDOWN: VK=16, Waiting=0, Repeat=Y, Shifts=1

14152286 .. Key not programmed -- passed on to FS

14152379 KEYUP: VK=16, Waiting=0

Thanks Christian

[Pete Dowson]

Interessting is that when i start the Enginge with the toggle(combination behing shift+a) i am not able to press for example ö on my keyboard after put the toggle. I must first push the shift on my keyboard. The ö opensfor the atc window . The same is with the light. (L button) when i push l it doesn´t work. I must fist push shift on the keyboard release it and the it works. Here is the log therefor. And so i think that the shift will not be released.

There#s still something wrong. The KEYUPs for the press programming are not being sent. It is acting exactrly as if the keys are being held down.

Please post your FSUIPC.INI file -- just the buttons and keys sections. Something isn't making any sense at all!

Pete

[masterk]

OK,

here is it:

[buttons]

ButtonRepeat=20,10

1=P5,12,K70,8

2=U5,12,K70,8

3=P5,16,K75,8

4=U5,16,K89,10

5=P5,17,K82,10

6=U5,17,K89,10

7=H3,8,K68,8

8=H1,29,K113,8

9=H1,28,K113,8

10=P1,14,K68,8

11=U1,28,K112,8

12=U1,29,K112,8

[Axes]

0=0X,256,F,66387,0,0,0

1=0Y,256,F,66388,0,0,0

2=0R,256,F,65764,0,0,0

3=2X,256,D,22,0,0,0

4=2Z,256,F,66420,0,0,0

5=3R,256,D,36,0,0,0

6=4X,256,D,1,0,0,0

7=4Y,256,D,2,0,0,0

8=4Z,256,F,66423,0,0,0

9=4R,256,D,23,0,0,0

[buttons.iFly 737-800 AirBerlin D-ABBE (Normal screen)]

0=H2,4,K65,9

1=H4,14,K116,10

2=H4,19,K190,10

3=H5,14,K117,9

4=H5,15,K118,9

5=H4,15,K120,9

6=H2,5,K119,9

7=H2,3,K122,9

8=H5,28,K88,8

9=H5,29,K66,9

10=H5,18,K85,10

11=H5,19,K71,10

12=P5,12,K85,8

13=U5,12,K85,8

14=P5,13,K123,10

15=U5,13,K123,10

16=H2,0,K191,9

[sounds]

Path=H:\Flight Simulator 9\Sound\

Device1=Primärer Soundtreiber

Device2=Lautsprecher (VIA High Definition Audio)

Device3=Kopfhörer (2- Microsoft LifeChat LX-3000 )

Device4=Digital Output Device (HDMI TX0) (VIA High Definition Audio)

Device5=SPDIF Interface (TX1) (VIA High Definition Audio)

[buttons.iFly 737-800 Air Berlin (Normal screen)]

0=H2,4,K65,9

1=H4,14,K116,10

2=H4,19,K190,10

3=H5,14,K117,9

4=H5,15,K118,9

6=H2,5,K119,9

7=H2,3,K122,9

8=H5,28,K88,8

9=H5,29,K66,9

10=H5,18,K85,10

11=H5,19,K71,10

12=H5,12,K85,8

13=U5,12,K85,8

14=H5,13,K123,10

15=U5,13,K123,10

16=H2,0,K191,9

17=H3,12,K13,9

18=H3,13,K8,9

19=H4,1,K70,8

20=H4,15,K120,9

25=P1,27,C65752,0

26=U1,27,C65752,0

27=H1,14,K68,8

31=P1,24,K67,9

33=P1,23,K65,9

37=U1,23,K72,8

38=U1,24,K74,8

39=H3,0,K46,8

40=P4,7,C65564,0

41=P3,3,C65564,0

42=P1,1,C66113,0

43=P1,10,C66112,0

44=H1,25,K69,9

49=H1,7,K67,8

[Axes.iFly 737-800 Air Berlin (Normal screen)]

0=0X,256,F,66387,0,0,0

1=0Y,256,F,66388,0,0,0

2=0R,256,F,65764,0,0,0

3=1Z,256,D,10,0,0,0

4=1R,256,D,9,0,0,0

5=2X,256,D,22,0,0,0

6=3R,256,D,36,0,0,0

7=4X,256,D,1,0,0,0

8=4Y,256,D,2,0,0,0

9=4R,256,D,23,0,0,0

Best regards

Christian

[masterk]

Did you see an error here?

Best regards

Christian

[Pete Dowson]

Did you see an error here?

Sorry, I haven't had time to look at it today. It's on my list to look at tomorrow. It isn't going to be that easy. I shall have to get my FS9 installation up and running again to check.

If you don't see a reply from me by Friday evening, get back and shout at me.

Regards

Pete

[masterk]

Hi,

no problem. i have time. :) Thank you for the great support.

Christian

[Pete Dowson]

no problem. i have time. :) Thank you for the great support.

I 've done some testing and comparisons with key-press programming in FSUIPC3 in FS9, comparing the results to FSUIPC4 in FSX.

Something odd is going on. The code in FSUIPC for these parts is pretty much identical in the two cases, yet in FSX the KEYUPs are consistently sent within 100 mSecs of the last KEYDOWN.which they cancel. On FS9 the time varies considerably, from 200 or so mSecs up to several seconds! The longest i've recorded so far was in excess of 8 seconds!

So far I've not managed to get any result where the KEYUPs never got sent, though. I am wondering if the loading on your system, or other events, are somehow making the time extraordinarily long or even losing them due to other things (as we saw when you had the '@ key press intervening).

Something seems to have changed a bit on your system since you submitted the earlier logs (see your entry, message #7 in the thread). The log showed it getting KEYUPs, at least when there's no interference:

3981271 Button changed: bRef=0, Joy=1, Btn=23, Pressed

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 33=P1,23,K65,9

3981271 SendKeyToFS(00040041=[shft+A], KEYDOWN) ctr=0

3981271 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=2

3981271 [buttons.iFly 737-800 Air Berlin (Normal screen)] 37=U1,23,K65,9

3981271 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

3981271 .. Key not programmed -- passed on to FS

3981318 Sending WM_KEYDOWN, Key=65 (Scan code 30), Ctr=1

3981318 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=1

3981318 .. Key not programmed -- passed on to FS

3.588 seconds gap here

3984906 SendKeyToFS(00040041=[shft+A], KEYUP) ctr=0

3984906 Sending WM_KEYUP, Key=65 (Scan code 30), Ctr=1

3984906 KEYUP: VK=65, Waiting=0

3984952 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=1

3984952 KEYUP: VK=16, Waiting=0

I'm looking to see where the long times in FSUIPC3 are coming from. If i can reduce those to similar levels to those in FSX I suspect your problem will disappear.

[LATER]

I found one place where there is a delay made deliberately (so watching programs don't miss the keypress) but it looks like it sohuld have been of the order of 100-200 mSecs, like FSX, but the value has also been used for something else.

I've separated the two and made the KEYUP delay separate entirely.

Please try version 3.993 from this link and let me know:

FSUIPC 3.993

Regards

Pete

Regards

Pete

[masterk]

Hi,

thank you very much. I will test it after i am home from work.

I have made a test with the combination "ctrl+A" behind the Joystick toggle and there is the same problem. It is not only the problem with the shift key.

Best regars

Christian