[FSUIPC4+FSX] CTRL+SHIFT issue

[A320wolf]

Hi Pete!

I've just bought FSUIPC 4 from simmarket and installed with the latest version for FSX available on this forum.

I start FSX and load the Wilco ERJ170 aircraft. I have the FSUIPC4 correctly installed and registered. All menus are visible and active.

I decide to use my goflight P8 module (it has 8 buttons) with this plane and so I go in the FSUIPC Buttons+Switches menu.

I start to assign the keyboards shortcuts to each button. The same with my VMAX cloche buttons.

Then I close FSUIPC window and try the work. With my surprise I notice a strange problem: each assignment with a CTRL+SHIFT+any keys let FSX to lock any other keyboard input.

For example: I use the CTRL+SHIFT+1 assignment to turn on the NAV LIGHTS.

If I use this combination directly on the keyboard FSX does it well without any problems. But if I push my button, FSUIPC send this key assignment to FSX, my NAV LIGHT turns ON but it's like the CTRL+SHIFT keys remains locked on the keyboard. I have to push CTRL+SHIFT again on the keyboard to unlock.

The strange thing is that on FSUIPC menu I remove these flags:

- Key press not to be held (nothing change even if I put the flag on this option)

- Key press to repeat while held

This issue occurs with any hardware I use (GoFlight or the simple VMAX cloche or any another cloche/throttle and so on).

Any other keys combination CTRL+any keys or SHIFT+any keys works perfectly.

And for your information I use FSUIPC 3.85 in FS9 in the same manner without problems.

I have this "bug" with any aircraft in FSX.

I hope you can understand the problem.... my English is not so good :oops:

I use FSX SP2 under Windows Vista 64bit Business Edition.

Thanks!

Bye, Max

[Pete Dowson]

And for your information I use FSUIPC 3.85 in FS9 in the same manner without problems.

I have this "bug" with any aircraft in FSX.

Strangely, this bug was reported in FSUIPC 3.853, and was fixed in 3.856. I don't believe it occurs in version 4.409. the current interim FSUIPC release. Have you tried it?

Regards

Pete

[A320wolf]

Hi Pete.

Yes... I'm using 4.409.

Thanks,

bye, Max

[Pete Dowson]

Yes... I'm using 4.409.

I cannot reproduce any such problem with 4.409. Could you enable Button and Key logging (in the FSUIPC4 logging tab) please, then use one of the programmed buttons. Show me the resulting FSUIPC4.LOG file (it will be in the FSX Modules folder).

This is quite urgent -- I will be away from Thursday night until December 29th.

Regards

Pete

[A320wolf]

Hi Pete.

I start FSX with my Embraer 170 add-on, activate the fsuipc log and I move up and down two GoFlight Switches:

- turn the nav lights ON and OFF ---- CTRL+SHIFT+1

- turn the beacon lights ON and OFF ---- CTRL+SHIFT+2

Here is the log:

********* FSUIPC4, Version 4.409 by Pete Dowson *********

User Name="Massimo Solimbergo"

User Addr="massimo.solimbergo@dreamsky.it"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

118217 System time = 18:08:01, FSX time = 12:51:08 (11:51Z)

118217 LogOptions changed, now 40000000 00000001

120635 Button changed: bRef=0, Joy=109, Btn=0, Pressed

120635 [buttons.Embraer 170 Cirrus new] 29=P109,0,K49,11

120635 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

120635 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

120635 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

120635 [buttons.Embraer 170 Cirrus new] 41=U109,0,K49,11

120635 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000081}

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

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

120635 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

120666 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

120666 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

120698 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=3

120698 KEYUP: VK=49, Waiting=0

120744 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

120744 KEYUP: VK=17, Waiting=0

120744 KEYUP: VK=16, Waiting=0

123318 Button changed: bRef=0, Joy=109, Btn=0, Released

123318 [buttons.Embraer 170 Cirrus new] 29=P109,0,K49,11

123318 [buttons.Embraer 170 Cirrus new] 41=U109,0,K49,11

123318 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

123318 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

123318 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

123318 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080}

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

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

123318 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

123350 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

127187 Button changed: bRef=0, Joy=109, Btn=1, Pressed

127187 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

127187 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

127187 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1

127187 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=2

127187 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

127187 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000082}

127187 KEYUP: VK=49, Waiting=0

127218 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=5

127218 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=5

127218 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=5

127218 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=5

127218 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=1

127218 KEYUP: VK=17, Waiting=0

127218 KEYUP: VK=16, Waiting=0

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

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

127218 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

127250 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=4

127281 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

127281 KEYUP: VK=50, Waiting=0

127312 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

127312 KEYUP: VK=17, Waiting=0

127312 KEYUP: VK=16, Waiting=0

128123 Button changed: bRef=0, Joy=109, Btn=1, Released

128123 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

128123 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

128123 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0

128123 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

128123 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

128123 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080}

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

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

128123 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

128154 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1

128154 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0

128186 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

128186 KEYUP: VK=50, Waiting=0

128217 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

128217 KEYUP: VK=17, Waiting=0

128217 KEYUP: VK=16, Waiting=0

134036 LogOptions changed, now 00000000 00000001

143302 System time = 18:08:26, FSX time = 12:51:23 (11:51Z)

143302 *** FSUIPC log file being closed

Average frame rate for running time of 36 secs = 26.4 fps

Memory managed: 19 Allocs, 19 Freed

********* FSUIPC Log file closed ***********

Thanks for your help!

Regards,

Max

[Pete Dowson]

I move up and down two GoFlight switches

I thought you said you were using a P8, push buttons, not a T8 with toggle switches?

120635 Button changed: bRef=0, Joy=109, Btn=0, Pressed

120635 [buttons.Embraer 170 Cirrus new] 29=P109,0,K49,11

120635 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

120635 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

120635 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

120635 [buttons.Embraer 170 Cirrus new] 41=U109,0,K49,11

You have the same key combination sent when the button is pressed AND when it released. Why is that? It is most unusual to do that with a button and keypresses. It would make sense with a toggle switch.

The sequence sent when it was pressed is this:

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

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

120635 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

120666 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

120666 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

120698 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=3

120698 KEYUP: VK=49, Waiting=0

120744 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

120744 KEYUP: VK=17, Waiting=0

120744 KEYUP: VK=16, Waiting=0

Everything there is fine, except that the KEYDOWN for key 49, though it was sent, was not received by FSUIPC. I assume it's been detected earlier in the chain by the add-on you intended it for.

On the release:

123318 Button changed: bRef=0, Joy=109, Btn=0, Released

123318 [buttons.Embraer 170 Cirrus new] 29=P109,0,K49,11

123318 [buttons.Embraer 170 Cirrus new] 41=U109,0,K49,11

123318 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

123318 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

123318 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

123318 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080}

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

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

123318 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

123350 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

which is fine, as far as it goesbut there appears to be a delay then before the button releases are sent. In fact, just after the next button is pressed:

127187 Button changed: bRef=0, Joy=109, Btn=1, Pressed

127187 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

127187 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

127187 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1

127187 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=2

127187 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

127187 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000082}

127187 KEYUP: VK=49, Waiting=0

127218 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=5

127218 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=5

127218 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=5

127218 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=5

127218 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=1

127218 KEYUP: VK=17, Waiting=0

127218 KEYUP: VK=16, Waiting=0

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

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

127218 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

127250 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=4

The emboldened entries are those for the key releases from the previous press.

Then we get the releases from the second pressed button:

127281 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

127281 KEYUP: VK=50, Waiting=0

127312 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

127312 KEYUP: VK=17, Waiting=0

127312 KEYUP: VK=16, Waiting=0

which are fine, then the release action on the same button:

128123 Button changed: bRef=0, Joy=109, Btn=1, Released

128123 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

128123 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

128123 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0

128123 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

128123 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

128123 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080}

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

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

128123 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

128154 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1

128154 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0

128186 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

128186 KEYUP: VK=50, Waiting=0

128217 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

128217 KEYUP: VK=17, Waiting=0

128217 KEYUP: VK=16, Waiting=0

and that looks perfect.

So, in this example at least, there appear to be no "stuck keys" except in the few seconds between releasing the first button and pressing the second, when it rectified itself.

I'm really not sure how that delay arises. Would the key releases have occurred if you had not pressed another GoFlight button? I'm afraid your log, whilst showing that there might be a problem, doesn't seem to show THE problem. It is really a shame you pressed the second button.

Now I have a better idea of what you are doing I will try to reproduce this here. Meanwhile, could you try actually reproducing the stuck keys case with them actually stuck, not apparently cleared by another button press. And could you clarify whether you are using buttons (as on a P8) or toggles (as on a T8)?

Regards

Pete

[Pete Dowson]

One other thing to try, please. Assuming you've not tested this yet with the official user release at present (4.40), do you think you could try that and let me know? I need to know if this problem might be due to recent changes (4.401-4.409) or whether they existed before.

In order to get the 4.40 installer to install 4.40 you'll need to remove the FSUIPC4.DLL from the FSX modules folder, as it refuses to replace a later version.

After that, could you also try 4.411 (now in the FSX Downloads Announcement above), as there are some other changes in that.

Thanks.

If I cannot resolve this tomorrow (Thursday) it is going to have to await my return on the 29th.

Regards

Pete

[A320wolf]

Hi Pete.

First of all thanks for your great and quick help!

Now I try with version 4.111.

Ok in the example above I use GoFlight T8 (switches). I assign keys before when I turn the switch up, I have to turn my nav lights on. Then when I turn down the switch I have to turn the nav lights off. Probably it's not the correct way... let me know.

In any case the same thing happen also if I assign the ctrl+shift+any keys to a button.

I assign the same keys to my VMAX CLOCHE button and the I log the result.

Another thing: the ctrl+shift "issue" happens with any add-ons/aircraft.

Give me 10 minutes to download and try the FSUIPC 4.111

Bye, Max

[Pete Dowson]

I assign keys before when I turn the switch up, I have to turn my nav lights on. Then when I turn down the switch I have to turn the nav lights off. Probably it's not the correct way... let me know.

Doesn't the aircraft you are using obey the FS NAV light switch? I'm not sure why you have this strangekey combination. Why not assign the button to the NAV light control provided for this? ("TOGGLE NAV LIGHTS").

It is also possible, using FSUIPC Offset controls, to have a separate operation for turning them On and Off, so always ensuring the switch is synchronised.

I'm afraid i've accidentally deleted your post about 4.411. I just need the Log file itself, please. Can you send it to me (Zipped) at petedowson@btconnect.com? Thanks.

Can you then try 4.40 please?

Pete

[A320wolf]

Simply because many of the complex add-ons for FS9 and FSX don't use the default controls.

Someone give you the chance to assign keys combinations. I can say PMDG, LEVEL-D, WILCO-FEELTHERE, DIGITAL AVIATION FOKKER and so on ....

In my case I'm using the Wilco ERJ170 www.wilcopub.com who comes with a key assignment control panel.

I assign the CTRL+SHIFT+keys to different controls. Anyway I repeat that in FS9 the same situation works without problems.

I suppose there's something wrong in FSX + FSUIPC.

I'd like to know if someone else has the same issue.

Thanks!

Bye, Max

[A320wolf]

Hi Pete.

Email sent.

Thanks!

Bye, Max

[Pete Dowson]

Email sent.

Thanks.

The log you sent shows everything worked perfectly. Every press had a coplementary release, and all in correct short times. Look, here is the log split into key presses and releases:

PRESS BUTTON 6 [CTRL+SHIFT+1]

154831 Button changed: bRef=0, Joy=0, Btn=6, Pressed

154831 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

154831 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

154831 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

154831 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

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

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

154831 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

154862 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

154893 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

154893 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1

154893 KEYUP: VK=49, Waiting=0

154925 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

154925 KEYUP: VK=17, Waiting=0

154925 KEYUP: VK=16, Waiting=0

154956 Button changed: bRef=0, Joy=0, Btn=6, Released RELEASE BUTTON 6 (not programmed)

154956 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

PRESS BUTTON 6 AGAIN (CTRL+SHIFT+1]

156516 Button changed: bRef=0, Joy=0, Btn=6, Pressed

156516 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

156516 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

156516 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

156516 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

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

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

156516 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

156563 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

156625 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

156625 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1

156625 KEYUP: VK=49, Waiting=0

156656 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

156656 Button changed: bRef=0, Joy=0, Btn=6, Released RELEASE BUTTON 6 (not programmed)

156656 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

156656 KEYUP: VK=17, Waiting=0

156656 KEYUP: VK=16, Waiting=0

PRESS BUTTON 6 AGAIN (CTRL+SHIFT+1]

158107 Button changed: bRef=0, Joy=0, Btn=6, Pressed

158107 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

158107 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

158107 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

158107 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

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

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

158107 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

158138 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

158169 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

158169 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1

158169 KEYUP: VK=49, Waiting=0

158216 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

158216 KEYUP: VK=17, Waiting=0

158216 KEYUP: VK=16, Waiting=0

158279 Button changed: bRef=0, Joy=0, Btn=6, Released RELEASE BUTTON 6 (not programmed)

158279 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

PRESS BUTTON 6 AGAIN (CTRL+SHIFT+1]

159589 Button changed: bRef=0, Joy=0, Btn=6, Pressed

159589 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

159589 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

159589 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

159589 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

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

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

159589 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

159620 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

159651 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0

159651 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1

159651 KEYUP: VK=49, Waiting=0

159683 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

159683 KEYUP: VK=17, Waiting=0

159683 KEYUP: VK=16, Waiting=0

159745 Button changed: bRef=0, Joy=0, Btn=6, Released RELEASE BUTTON 6 (not programmed)

159745 [buttons.Embraer 170 Cirrus new] 43=P0,6,K49,11

PRESS BUTTON 1 (CTRL+SHIFT+2]

163068 Button changed: bRef=0, Joy=109, Btn=1, Pressed

163068 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

163068 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0

163068 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

163068 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

163068 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

163068 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000082}

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

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

163068 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

163099 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1

163099 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0

163130 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

163130 KEYUP: VK=50, Waiting=0

163162 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

163162 KEYUP: VK=17, Waiting=0

163162 KEYUP: VK=16, Waiting=0

RELEASE BUTTON 1 (CTRL+SHIFT+2]

164378 Button changed: bRef=0, Joy=109, Btn=1, Released

164378 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

164378 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

164378 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0

164378 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

164378 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

164378 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080}

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

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

164378 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

164410 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1

164410 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0

164441 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

164441 KEYUP: VK=50, Waiting=0

164472 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

164472 KEYUP: VK=17, Waiting=0

164472 KEYUP: VK=16, Waiting=0

PRESS BUTTON 1 (CTRL+SHIFT+2]

165626 Button changed: bRef=0, Joy=109, Btn=1, Pressed

165626 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

165642 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0

165642 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

165642 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

165642 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

165642 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000082}

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

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

165642 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

165673 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1

165673 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0

165704 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

165704 KEYUP: VK=50, Waiting=0

165751 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

165751 KEYUP: VK=17, Waiting=0

165767 KEYUP: VK=16, Waiting=0

RELEASE BUTTON 1 (CTRL+SHIFT+2]

167124 Button changed: bRef=0, Joy=109, Btn=1, Released

167124 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11

167124 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11

167124 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0

167124 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

167124 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

167124 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080}

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

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

167124 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

167155 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1

167155 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0

167186 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3

167186 KEYUP: VK=50, Waiting=0

167218 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2

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

167218 KEYUP: VK=17, Waiting=0

167218 KEYUP: VK=16, Waiting=0

You'll see, every part is fully complete and self-contained. Surely you did not experience any Control or Shift sticking in this sequence?

Have you ANY log which shows the problem actually occurring? I saw in your previous example where there was a 2-3 second delay, but apart from that everything has worked. Delays could occur because FS is busy accessing disc and so on, and normally the wanted key release does no harm.

You said it also happens with 4.40, which means it probably would ALWAYS happen on your system, right back to day one. If I cannot reproduce it even once here we might be looking at some process of elimination, or checking the other add-ons on your system.

BTW, I remember you said "I use FSUIPC 3.85 in FS9 in the same manner without problems". The implementation in this area in identical in 4.40 and 3.85, so it is pointing either to some weird timing difference or some sort of interference with an add-on. The code is also some 10 years old and this is the first report, so I'm worried that it is going to be a tough one to crack. I do need to be able to reproduce it, and it would be very useful to see a log which actually demonstrated the problem.

Regards

Pete

[Andydigital]

Does the OP have "FS Flight Keeper" installed? as I had the same issue a few weeks ago when assigning a keyboard shortcut facility in FSFK to the ACARS gauge and then using FSUIPC to turn it into a joystick button press. I ended up just editing the panel.cfg instead and used a normal panel call button combo i.e. shift 3 etc.

I've tried replicating the OP's problem with the latest interim build of FSUIPC4 and cant make it happen.

[A320wolf]

Mmm... thanks Pete. Unfortunatley no, I don't use any other add-ons in the background such as Flight Keeper or similar.

In this case I'll try to reinstall all my system because I don't know what happen. I'm asking why if I press the same key combination directly on the keyboard this problem doesn't appear :roll:

I'll let you know.

Many thanks again for your help,

Bye, Max

[Andydigital]

I would first try moving the FSUIPC4.ini file to another location for now and let FSUIPC build another one the next time it is run. Reinstalling everything is a rather drastic step to take just yet.

[Pete Dowson]

In this case I'll try to reinstall all my system because I don't know what happen.

But first can you

(a) confirm that, in both the logs you supplied so far you did NOT experience any Ctrl or Shift key "sticking"? Because both logs clearly show all "KEYDOWNs" matched by subsequent "KEYUPs".

and

(b) try and obtain a log for me which DOES reflect a real occurrence of your problem. If you have to press and release several buttons please note which was the last one before the stickiness.

I'm asking why if I press the same key combination directly on the keyboard this problem doesn't appear

Because the keyboard IS the keyboard and not a long sequence of Windows messages pretending to be a keyboard! It's like the difference between a real aircraft and a simulated one. They aren't the same! ;-)

It sounds like somehow, somewhere, for some reason, some of those messages are going astray. That's what I have to track down!

Pete

[A320wolf]

Ok Pete.

I've recreated a new fsuipc.ini but without success.

Here is the log. I turn up the goflight t8 switch (ctrl+shif+1). The nav lights switch on the virtual cockpit turn up too.

Then I press the space bar on the keyboard to see if the control to move the mouse and look inside the virtual cockpit works. None! It's locked and I have to press ctrl+shift on the keyboard to unlock it.

Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

175096 System time = 22:43:05, FSX time = 12:20:33 (11:20Z)

175096 LogOptions changed, now 40000000 00000001

184113 Button changed: bRef=0, Joy=109, Btn=0, Pressed

184113 [buttons.Embraer 170 Cirrus new] 0=P109,0,K49,11

184113 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

184113 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

184113 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

184113 [buttons.Embraer 170 Cirrus new] 2=U109,0,K49,11

184113 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000081}

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

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

184113 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

184160 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

184690 KEYDOWN: VK=32, Waiting=0, Repeat=N, Shifts=3

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

185174 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185189 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185236 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185267 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185283 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185314 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185361 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185392 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3

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

185423 KEYUP: VK=32, Waiting=0

192131 LogOptions changed, now 00000000 00000001

200711 System time = 22:43:30, FSX time = 12:20:49 (11:20Z)

200711 *** FSUIPC log file being closed

Average frame rate for running time of 71 secs = 56.0 fps

Memory managed: 31 Allocs, 31 Freed

********* FSUIPC Log file closed ***********

The "bug" happen immediately.

Bye, Max

[Andydigital]

Just to get around the problem for now (as it may be difficult for Pete to track down this problem before he goes on his Christmas break) You can also use Shift and Tab instead to gain a load of new keys to use, this is what I did before changing my mind and editing the panel.cfg

Hope this helps for now.

[A320wolf]

Good idea but unfortunately the Wilco ERJ doesn't allow the SHIFT+TAB :shock:

Well.... I suppose to try a clean installation of my system even if I have installed only FSX. Now I have something to do during my holiday :?

Thank for your help!

Bye, Max

[Andydigital]

How about just Tab and the key you want?

[A320wolf]

:roll: no... I have to forget the TAB key with this add-on

Bye, Max

[Pete Dowson]

I've recreated a new fsuipc.ini but without success.

I didn't suggest that one.

Here is the log. I turn up the goflight t8 switch (ctrl+shif+1). The nav lights switch on the virtual cockpit turn up too.

Then I press the space bar on the keyboard to see if the control to move the mouse and look inside the virtual cockpit works. None! It's locked and I have to press ctrl+shift on the keyboard to unlock it.

Yes, the Log, this time (for the FIRST time since we exchanged messages!) shows no KEYUPs being sent or received:

184113 Button changed: bRef=0, Joy=109, Btn=0, Pressed

184113 [buttons.Embraer 170 Cirrus new] 0=P109,0,K49,11

184113 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0

184113 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3

184113 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3

184113 [buttons.Embraer 170 Cirrus new] 2=U109,0,K49,11

184113 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000081}

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

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

184113 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

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

184160 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1

... but You pressed the SPACE bar about half a second after pressing that button (or flicking the toggle, whatever). That's real quick! Look:

184690 KEYDOWN: VK=32, Waiting=0, Repeat=N, Shifts=3

The number on the left is milliseconds. 184690 - 184113 = 577 mSecs, or 0.577 seconds.

So, does it seem to you that is this the only way it happens -- when you press the real keyboard whilst the (long) key sequence from the button press is still playing?

If so, i wonder if this is a problem of Windows, and possibly only of Windows. FSUIPC uses a single Windows call "SendInput" to ask it to do all this. It is effectively a "playback" facility -- as if the keystrokes were recorded and are now being played back. I'm thinking now that this facility can be interrupted, and effectively halted, by real keyboard action.

You are more likely to be able to interrupt a 6 key sequence (Ctrl + Shift + Key DOWN then UP in reverse order) than a 4 key one (Ctrl or Shift, not both). So maybe that's why? Are you often pressing keys on the keyboard very quickly after using a button? Wouldn't it be better to program everything on the buttons and avoid the keyboard?

Tomorrow I will see if I can reproduce it on WinXP first, then, if I have time, Vista 32. I may have to leave this till the week after Christmas though. I was worried initially that it was a new bug in the recent interim releases, but now i know if must have always been occurring and it hardly bothered anyone before, it becomes less urgent. Now that you know about it at least you can avoid it or recover from it until we find a fix -- if there is one. If it does turn out to be a Windows problem i don't know if it can be worked-around.

Regards

Pete

[A320wolf]

So, does it seem to you that is this the only way it happens -- when you press the real keyboard whilst the (long) key sequence from the button press is still playing?

Hi Pete.

I press the spacebar because it's the first thing to see if the ctrl+shift is locked.

Even if I don't press any keys after turn the switch or other button with the ctrl+shift+any key, this combination produces the "error"

Normally when I use my switches or buttons I don't use any other keys so quickly. This is the first time I have this annoying issue but I think it's better to "re-clean" my system, install FSX and FSUIPC with any other add-ons and try with default aircraft.

Then I'll let you know.

Tomorrow I will see if I can reproduce it on WinXP first, then, if I have time, Vista 32. I may have to leave this till the week after Christmas though. I was worried initially that it was a new bug in the recent interim releases, but now i know if must have always been occurring and it hardly bothered anyone before, it becomes less urgent. Now that you know about it at least you can avoid it or recover from it until we find a fix -- if there is one. If it does turn out to be a Windows problem i don't know if it can be worked-around.

Ok.... for your information I'm using Vista 64bit.

Anyway don't worry Pete. I appreciate your help and support.

I'll post some news in this topic as soon as my system will be reinstalled.

Thanks again and Merry Christmas!

Regards,

Max

[Pete Dowson]

I press the spacebar because it's the first thing to see if the ctrl+shift is locked.

Even if I don't press any keys after turn the switch or other button with the ctrl+shift+any key, this combination produces the "error"

But evidently not often? I say this because all the other examples you showed were fine. The only one you've shown with a problem was with an immediate (very fast, in fact) pressing of the space bar.

I would, if possible, still like to see a log of an "ordinary" case where this happens, where the space bar is not pressed for, say, at least 15 seconds -- just to be absolutely clear that it could not possibly have anything to do with real keyboard action interfering with Windows playback sequences.

I've taken a look at my code, and I must say it is starting to look more and more like a possible Windows bug. So far I cannot see any other way of emulating the keypress sequences than using this one, provided by Windows for that purpose.

Normally when I use my switches or buttons I don't use any other keys so quickly. This is the first time I have this annoying issue but I think it's better to "re-clean" my system, install FSX and FSUIPC with any other add-ons and try with default aircraft.

Then I'll let you know.

Okay. Thanks.

Ok.... for your information I'm using Vista 64bit.

Yes, but though I do have a Vista 64 installation, it only has FSX on it. It is my cockpit setup and I don't really want to "pollute" it with any software I'm not really using. If I cannot reproduce it with either XP or Vista32 I might try installing Vista64 on another machine, along with FS9, and see if I can reproduce it there.

... Merry Christmas!

Thanks! And you too!

Pete

[Pete Dowson]

I'll post some news in this topic as soon as my system will be reinstalled.

I hope I've caught you in time!

Please download and try 4.413 from the FSX Downloads Announcement.

I couldn't reproduce the issue on WinXP, but decided to look at ways of improving the code in any case. I have moved the key press sending code to a separate thread, away from the main FS thread. This should make it far less susceptible to the vagaries of FS's own actions, and, particularly, those of the add-on which is actually processing the keys being pressed.

The timings now of each keystroke DOWN and UP should be more precise and reliableI hope!

Please try it and let me know.

I could do the same in FSUIPC3, but since you don't get problems with that I'll leave well enough alone! ;-)

Regards

Pete