FSUIPC 4.928 strange behaviour, most likely a conflict

Seme · February 7, 2014

Hello Pete & Fellow simmers

Last night I updated my FSUIPC to the latest one. Before this, I had setup my goflight modules for PMDG 777 & 737NGX and they still work brilliantly. Now, after the update, I wanted to assing the goflight modules (T8 & RP48) for PMDG 747 and for the MD-11. What I did, was that I assigned ctrl+a key command to each light switch via the PMDG Keyboard command menu. These are the same key commands that I use with the 777&NGX.

Then under FSUIPC button&switches tab, I tick the profile specific and created a new template for the MD-11 and for the 747. Then I assigned the keys the same way I did for the 777&NGX. For example ctrl+c toggles the beacon light switch. Now it looks like it works like charm, the switch moves as it should, on and off.

Now whats the problem? The problem is, that after I have moved any of the assigned switches either with the 747 or the MD-11, basically my keyboard does not work anymore. Everything else works more or less as should. If I try to type something, for example a website address to the browser, any of the keypress makes the PC do something else. For example I tried to type google to the the browser and it ended up adding the blank site to my favorites:)

Im completely puzzled, I know it has to be some conflict but do not now what. For referecene, the old 777 and NGX assignments works still fine and does not mess up my keyboard. The problem dissipated when I cleared the assignments for the 747 and the MD-11. So, now im back in the beginning...

I have not assigned anything via the goflight own mapping software, so Im using only the FSUIPC assignments. I have taken out almost all keyboard settings from the FSX as well, so these should not mess with the system.

Im using FSX, Win7 64bit, I have latest nvidia drivers (updated last night as well).

Any idea where to start to look the problem?

Many thanks!

Cheers

Thomas S.

Pete Dowson · February 7, 2014

Then under FSUIPC button&switches tab, I tick the profile specific and created a new template for the MD-11 and for the 747. Then I assigned the keys the same way I did for the 777&NGX. For example ctrl+c toggles the beacon light switch. Now it looks like it works like charm, the switch moves as it should, on and off.

Now whats the problem? The problem is, that after I have moved any of the assigned switches either with the 747 or the MD-11, basically my keyboard does not work anymore. Everything else works more or less as should. If I try to type something, for example a website address to the browser, any of the keypress makes the PC do something else. For example I tried to type google to the the browser and it ended up adding the blank site to my favorites:)

Im completely puzzled, I know it has to be some conflict but do not now what. For referecene, the old 777 and NGX assignments works still fine and does not mess up my keyboard. The problem dissipated when I cleared the assignments for the 747 and the MD-11. So, now im back in the beginning...

It sounds like you are getting a shift key (shift, ctrl or alt) stuck 'on', so modifying other keypresses. Are you assigning the switches to "press and release"? If so then FSUIPC will certainly be sending the KEYUP messages a little while after the KEYDOWN ones. Maybe the 747 or MD11 coding somehow inteerferes with this.

If you are, by mistake, assigning instead to just "press" then the keys will certainly be left pressed. If that's your mistake then it is easily rectified. Just assign to press and release instead.

Use the Key/Button logging facilities to see what is going on. (Logging tab, one of the checkboxes on the left). If you (temporarily) run FS in Windowed mode and enable the console log (same tab) you can see what FSUIPC sees in real time, whilst you operate the switches.

If you can't work it out, show me the log of you operating the switches, and then later trying to use the keyboard for other thngs (in FS), and also show me your settings (the INI file). You can paste the contents of these things into a message here.

Regards

Pete

Seme · February 7, 2014

Hi Pete,

Thanks for the fast and detailed reply. Thats enough information for me at the moment to work with (when I have the chance) and I will report back.

Thank god of this forum.... :)

Cheers

Thomas

Seme · February 7, 2014

Hi Pete,

"key press not to be held" and "key press to repeat while held" check boxes are not checked.. I just have set the key assignment (ctrl+c for example) into the upper "... press this button" and to the lower ".... release this button".

Cheers

Thomas

Pete Dowson · February 7, 2014

"key press not to be held" and "key press to repeat while held" check boxes are not checked.. I just have set the key assignment (ctrl+c for example) into the upper "... press this button" and to the lower ".... release this button".

That'll send the same keypress each time you operate the switch. If it is a momentary press button then best not to assign anything to 'release; or it'll be sent twice.

[LATER]

I just realised you said you did NOT have the "key press not to be held" option set, so you are holding the keypress. Why?

I need the log as I said if you still need help.

Pete

Seme · February 9, 2014

Hi Pete,

Still having the same problem, what ever I assign, it freezes the keyboard and ezca is not working anymore. Somehow I think it will trigger the ctrl to be held... Heres the log when I tried to assing ctrl+c for beacon light, using goflight T8 switch.

********* FSUIPC4, Version 4.928 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=66B60000

User Name="Thomas Schmiedeke"

User Addr="seme_@hotmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

47 System time = 09/02/2014 11:01:27

47 FLT path = "C:\Users\Seme\Documents\Flight Simulator X Files\"

390 Trying to connect to SimConnect Acc/SP2 Oct07 ...

437 FS path = "D:\FSX\"

1279 Run: "D:\FSX\Modules\linda.exe"

1482 LogOptions=00000000 00000001

1482 SIM1 Frictions access gained

1482 Wind smoothing may be by ASN, not FSUIPC, if it is running

1482 Will switch smoothing action when ASN starts/stops

1482 G3D.DLL fix attempt installed ok

1482 SimConnect_Open succeeded: waiting to check version okay

1482 Trying to use SimConnect Acc/SP2 Oct07

1545 VRI port 1 "com3" opened

5039 VRI FMER ("MCP Combi") detected on port com3

5663 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

5663 Initialising SimConnect data requests now

5663 FSUIPC Menu entry added

5710 D:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

5710 D:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

108967 D:\FSX\SimObjects\Airplanes\PMDG747-400\B747-400.AIR

129980 System time = 09/02/2014 11:03:37, Simulator time = 11:03:33 (21:03Z)

130464 Aircraft="PMDG747-400 KLM ASIA"

197903 Starting everything now ...

198059 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.2.2.0

198059 GoFlight GFT8 detected: 1 device

198059 GoFlight GFRP48 detected: 1 device

198090 LUA.0: beginning "D:\FSX\Modules\ipcReady.lua"

198090 LUA.0: ended "D:\FSX\Modules\ipcReady.lua"

198121 AES Link established

198137 LUA.1:

198153 LUA.1: [iNIT]LINDA:: Loading...

198231 LUA.1: LINDA:: Aircraft: PMDG747-400 KLM ASIA

198246 LUA.1: LINDA:: Aircraft module detected: PMDG 744-400

198293 LUA.0: LINDA:: AivlaSoft library loaded...

198309 LUA.0: LINDA:: FSX standard library loaded...

198324 LUA.0: LINDA:: IAO library loaded...

198324 LUA.0: LINDA:: RealityXP library loaded...

198340 LUA.0: LINDA:: A2A MAP library loaded...

200383 LUA.0: LINDA:: Module: PMDG 744-400 Started...

200399 LUA.0: LINDA:: Ready to go, Captain!

200399 LUA.0: LINDA::

200461 LUA.0: LINDA:: Offsets watching list cleared!

201741 Advanced Weather Interface Enabled

237309 Sim stopped: average frame rate for last 42 secs = 25.7 fps

265264 LogOptions changed, now 40000000 00000001

273922 *** Entered Buttons option page ***

280724 Aircraft="PMDG747-400 KLM ASIA"

294904 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

294904 FirstButtonChange res=00006D00 (0.109, 0)

333343 *** Exiting Buttons option page ***

339599 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

340940 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

343483 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

344341 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

346198 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0

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

346369 KEYUP: VK=50, Waiting=0

346900 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=0

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

347071 KEYUP: VK=49, Waiting=0

350144 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

351470 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

354278 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=0

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

354450 KEYUP: VK=56, Waiting=0

354824 KEYDOWN: VK=55, Waiting=0, Repeat=N, Shifts=0

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

355027 KEYUP: VK=55, Waiting=0

355526 KEYDOWN: VK=54, Waiting=0, Repeat=N, Shifts=0

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

355698 KEYUP: VK=54, Waiting=0

356213 KEYDOWN: VK=53, Waiting=0, Repeat=N, Shifts=0

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

356384 KEYUP: VK=53, Waiting=0

356759 KEYDOWN: VK=52, Waiting=0, Repeat=N, Shifts=0

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

356930 KEYUP: VK=52, Waiting=0

357383 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=0

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

357554 KEYUP: VK=51, Waiting=0

358163 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0

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

358288 KEYUP: VK=50, Waiting=0

359660 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=0

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

359848 KEYUP: VK=49, Waiting=0

361954 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0

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

362078 KEYUP: VK=50, Waiting=0

365323 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

368194 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

373357 Sim stopped: average frame rate for last 40 secs = 26.7 fps

374715 *** Entered Buttons option page ***

377289 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

377289 FirstButtonChange res=00006D07 (0.109, 7)

378256 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

379597 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

379613 FirstButtonChange res=00006D07 (0.109, 7)

393825 *** Exiting Buttons option page ***

396976 Button changed: bRef=0, Joy=109, Btn=7, Released

396976 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

396976 SendKeyToFS(00020043=[ctl+C], KEYUP) ctr=0

396976 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

396991 Sending WM_KEYUP, Key=67 (Scan code 46), Ctr=1

397023 KEYUP: VK=67, Waiting=0

398442 Button changed: bRef=0, Joy=109, Btn=7, Pressed

398442 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

398442 SendKeyToFS(00020043=[ctl+C], KEYDOWN) ctr=0

398442 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

398442 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2

398458 Sending WM_KEYDOWN, Key=67 (Scan code 46), Ctr=1

398473 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

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

398473 KEYDOWN: VK=67, Waiting=0, Repeat=N, Shifts=2

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

399628 Button changed: bRef=0, Joy=109, Btn=7, Released

399628 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

399628 SendKeyToFS(00020043=[ctl+C], KEYUP) ctr=0

399643 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

399643 Sending WM_KEYUP, Key=67 (Scan code 46), Ctr=2

399659 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1

399675 KEYUP: VK=67, Waiting=0

399675 KEYUP: VK=17, Waiting=0

400205 Button changed: bRef=0, Joy=109, Btn=7, Pressed

400205 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

400205 SendKeyToFS(00020043=[ctl+C], KEYDOWN) ctr=0

400205 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

400205 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2

400221 Sending WM_KEYDOWN, Key=67 (Scan code 46), Ctr=1

400236 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

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

400236 KEYDOWN: VK=67, Waiting=0, Repeat=N, Shifts=2

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

402264 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=2

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

402436 KEYUP: VK=50, Waiting=0

403263 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=2

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

403465 KEYUP: VK=49, Waiting=0

405665 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=2

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

405837 KEYUP: VK=49, Waiting=0

406164 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=2

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

406352 KEYUP: VK=50, Waiting=0

416991 Sim stopped: average frame rate for last 23 secs = 29.7 fps

473463 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=2

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

473635 KEYUP: VK=49, Waiting=0

473869 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=2

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

474040 KEYUP: VK=50, Waiting=0

599216 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=0

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

599450 KEYUP: VK=49, Waiting=0

599933 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0

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

600167 KEYUP: VK=50, Waiting=0

Does this help you to solve the issue?

Cheers and thanks!

Thomas

Pete Dowson · February 9, 2014

Does this help you to solve the issue?

FSUIPC is working correctly, doing what you ask. Look, this shows the switch operating correctly:

398442 Button changed: bRef=0, Joy=109, Btn=7, Pressed

398442 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

You "pressed" the button (or toggled the switch to 'on'

398442 SendKeyToFS(00020043=[ctl+C], KEYDOWN) ctr=0

398442 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

398442 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2

398458 Sending WM_KEYDOWN, Key=67 (Scan code 46), Ctr=1

398473 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

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

398473 KEYDOWN: VK=67, Waiting=0, Repeat=N, Shifts=2

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

and as programmed it pressed Ctrl+C.

(You do realise Ctrl+C is a VERY bad key combo to use, don't you. It is normally intercepted by Windows and means "terminate".)

Then your button was released or switch set to Off:

399628 Button changed: bRef=0, Joy=109, Btn=7, Released

399628 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

399628 SendKeyToFS(00020043=[ctl+C], KEYUP) ctr=0

399643 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 0000007f}

399643 Sending WM_KEYUP, Key=67 (Scan code 46), Ctr=2

399659 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=1

399675 KEYUP: VK=67, Waiting=0

399675 KEYUP: VK=17, Waiting=0

And both the C key and Ctrl were released -- in the correct order, too.

Then you pressed the button again 9or switched it to "on":

400205 Button changed: bRef=0, Joy=109, Btn=7, Pressed

400205 [buttons.PMDG747-400 KLM ASIA] 19=H109,7,K67,10

400205 SendKeyToFS(00020043=[ctl+C], KEYDOWN) ctr=0

So, again, Ctrl + C were pressed:

400205 JoystickValues PCnum=0, dwCount=1, data[2]={0000006d 000000ff}

400205 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=2

400221 Sending WM_KEYDOWN, Key=67 (Scan code 46), Ctr=1

400236 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

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

400236 KEYDOWN: VK=67, Waiting=0, Repeat=N, Shifts=2

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

but you never released the button or switched the switch to off!

This is why Ctrl C were kept pressed. It is doing EXACTLY what you programmed!

Why on Earth are you wanting to hold the keypresses down with a button or toggle switch? Obviously if you opt to hold the keypress whilst the button is pressed, the keys will stay pressed until you release the button (or switch the switch off). That's the whole point of having the Hold facility. But it is normally only used for momentary buttons, you seem to be using it on a toggle switch. Why? It might beokay if you don't want to use the keyboard for anything else. But it seems daft to me.

Pete

Seme · February 9, 2014

Hi Pete,

Thanks for straighting this up, I got mixed how the system works. I did the same as for the 777 and the NGX which works fine, so thats why I wonder why it did not work with 747 and the MD-11. I will change the setup for the 777 and the NGX as well.

This is what happens with a novice that does not understand the system correctly, thanks to you, I got this sorted

Cheers

Thomas

Sign In

FSUIPC 4.928 strange behaviour, most likely a conflict

Recommended Posts

Seme

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Seme

Link to comment

Share on other sites

Seme

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Seme

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Seme

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Browse

Activity

Important Information