Control conflict on FS2004

[stankar]

I installed FS9 on a new computer running Windows 7 and am experiencing the following conflict.

1. I use FSUIPC for most of my control allocations except the throttle quadrant and hat switch, for convenience. I am using the CH yoke and pedals.

2. When I activate one of the toggle switches, no matter to what I control a assign it, it toggles the landing gear, which is of course most inconvenient when flying a plane with retractable landing gear.

3. Thinking it might be a FSUIPC conflict, I searched for all instances of FSUIPC and corrected that.

4. Renaming FSUIPC extension to disable it made no difference.

5. Removing all yoke and pedal assignments in normal and slew mode, made no difference.

6. The problem only disappears when I disable the yoke, after which I can allocate the controls with FSUIPC.

7. I'm thinking of disabling the yoke and assigning all my controls to FSUIPC, but before I do this I'm hoping that somebody might be able to suggest where the problem is. After all, I'll simply be removing the symptom and not the cause. I suspect its either in the MS controls.dll or some other dll lurking around. I am reluctant to reinstall FS9 as this is quite a mission, with all the addons I have. If the problem is in the controls.dll, is it maybe possible to simply replace this dll and reassign the controls? This would be the easiest solution.

Thanks

Stan

[Andydigital]

Try assigning the button you are having a problem with to something else within FS9 itself, then once you have confirmed it is actioning this new command go back into the controls interface in FS9 and delete the assignment. This is what I do when a button starts to behave unusually, the same procedure works in FSX too.

[Pete Dowson]

You most certainly have the assignment to the Gear in FS. You probably have not used the FS assignments dropdown to check all instances of control devices and all button assignments there.

If you can't actually find it, then Andy's method should do the trick.

Pete

[stankar]

Hi

That's exactly what I did do. It actions the other command but simultaneously toggles the gear! I've tried this with many combinations.

Stan

[stankar]

Sorry if I didn't make it clear - but if I delete ALL the FS assignments which have been allocated to yoke, pedals and slew mode, and activate the troublesome yoke switch(5-up, 6-down), it toggles the gear. If I allocate it to some other function via FSUIPC (for instance a View function), it activates that function correctly, AS WELL AS THE GEAR. I haven't deleted the KEY assignments in FS. Only when I deactivate the yoke in FS does it NOT activate the gear, and that's why I am considering doing this and allocating ALL my controls via FSUIPC. However, this will only remove the symptom, not the cause, and I'm curious to find out why it does this. As I said in my earlier post, I suspect it could be something corrupted in the FS2004 Controls.dll file, and therefore I could easily rename this file and replace it with the default FS2004 file and see what happens. I'm just not sure how to extract this particular file from the FS2004 disks without doing a complete reinstal, which I'm reluctant to do. Alternately, I could use this toggle switch ONLY for aircraft without a retractable gear, but this seems a poor solution.

Stan

[Pete Dowson]

Sorry if I didn't make it clear - but if I delete ALL the FS assignments which have been allocated to yoke, pedals and slew mode, and activate the troublesome yoke switch(5-up, 6-down), it toggles the gear.

Yes, it was most clear. And the answer is clear too. If the switch toggles the gear it is most certainly assigned to do so, whether in its own driver (CH control manager maybe?), or in FS or in FSUIPC. You appear to have eliminated FSUIPC (by trying without), so it is elsewhere.

Enable Event logging in FSUIPC and check the log.

Only when I deactivate the yoke in FS does it NOT activate the gear

In that case the control is obviously assigned in FS to that switch on the yoke. There's no other answer, really.

and that's why I am considering doing this and allocating ALL my controls via FSUIPC. However, this will only remove the symptom, not the cause, and I'm curious to find out why it does this. As I said in my earlier post, I suspect it could be something corrupted in the FS2004 Controls.dll file, and therefore I could easily rename this file and replace it with the default FS2004 file and see what happens.

The controls.dll does not contain any key or button assignments. It's main function is to translate control numbers into calls to specific routines in SIM1, PANELS and so forth. It also contains the table from which FSUIPC gets the names for the FS controls.

All of your FS assignments are either defaulted, by definitions in the "devices" CFG files, or, more usually, assigned in the FS9.CFG file. If you genuinely cannot find where you have the assignment I suggest you remove the FS9.CFG file and let FS generate a new one.

Regards

Pete

[stankar]

Thanks Pete. Yes, I have to agree that it seems obvious that the control has been allocated in FS. I'll play around tomorrow and let you know as soon as I find something. In the meantime, its Saturday night here, and I'm taking the wife to a movie, so, no flightsimming for now.

Take care and have a good weekend.

Stan

[stankar]

Hi Pete

Re-creating FS9.cfg doesn't solve the problem. I also did another comprehensve search for stray fsuipc.dll's and found none.

I logged toggling the rogue key up and then down, and this is what I got. Perhaps you can interpret it for me?

Thanks

Stan

********* FSUIPC, Version 3.82 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\FS2004\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Stan Shear"

User Addr="stanshear@gmail.com"

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

1029 System time = 08:40:44

1029 C:\FS2004\

1029 System time = 08:40:44, FS2004 time = 12:00:00 (00:00Z)

4804 FLIGHTS\OTHER\FLTSIM.flt

4836 AIRCRAFT\c172\Cessna172SP.air

4992 Aircraft="Cessna Skyhawk 172SP"

35895 AIRCRAFT\DreamFleet Baron 58 Lite\BaronB58_2k4v1.8.air

36067 Aircraft="DreamFleet Beech Baron 58 Lite"

36223 [buttons] now aircraft-specific:

36223 9=P0,0,K120,8

36223 10=P0,1,K75,8

36223 6=P0,8,K71,8

38672 Advanced Weather Interface Enabled

39655 C:\Users\Stan\Documents\Flight Simulator Files\UI generated flight.flt

40435 Clear All Weather requested: external weather discarded

77750 Traffic File #63 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_boats"

77906 Traffic File #14 = "scenery\world\scenery\traffic030528"

77953 Traffic File #69 = "c:\fs2004\addon scenery\canada\nanaimo\scenery\traffic_cycd"

78234 Traffic File #60 = "c:\fs2004\addon scenery\canada\british columbia - victoria - landscape\scenery\traffic_ogden_point"

78328 Traffic File #66 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_ga"

78437 Traffic File #68 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_seaplane"

78593 Traffic File #67 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_heli"

78655 Traffic File #62 = "c:\fs2004\addon scenery\canada\british columbia - victoria - landscape\scenery\traffic_victoria_boats"

78702 Traffic File #64 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_cruiseships"

78796 Traffic File #28 = "scenery\world\scenery\traffic_000_woa_westjet_su08"

78905 Traffic File #49 = "scenery\world\scenery\traffic_90_woa_westjet_su06"

79108 Traffic File #65 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_cypk_ga"

79357 Traffic File #58 = "scenery\world\scenery\trafficjzasu05"

79498 Traffic File #43 = "scenery\world\scenery\traffic_254_woa_ultimate ga cessna 402_su06"

80059 Traffic File #15 = "scenery\world\scenery\traffic_000_woa_air canada jazz_wi08"

80106 Traffic File #16 = "scenery\world\scenery\traffic_000_woa_air canada_su08_fs9"

80262 Traffic File #32 = "scenery\world\scenery\traffic_10_woa_ups_su05"

80262 Traffic File #39 = "scenery\world\scenery\traffic_213_woa_ultimate ga learjet 45_su06"

80309 Traffic File #44 = "scenery\world\scenery\traffic_26_woa_american airlines_su06"

80371 Traffic File #46 = "scenery\world\scenery\traffic_60_woa_fedex_su05"

80371 Traffic File #48 = "scenery\world\scenery\traffic_80_woa_delta air lines_su06"

80465 Traffic File #52 = "scenery\world\scenery\traffic_kelowna"

80527 Traffic File #55 = "scenery\world\scenery\traffic_pacificcoastalairlines"

80730 Traffic File #57 = "scenery\world\scenery\trafficacasu05"

111384 WeatherOptions set, now 40003605 (timer=0)

114535 Button changed: bRef=0, Joy=0, Btn=4, Pressed

114535 [buttons.DreamFleet Beech Baron 58 Lite] 3=P0,4,K51,9

114535 SendKeyToFS(00040033=[shft+3], KEYDOWN) ctr=0

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

114535 KEYDOWN: VK=16, Waiting=0, Shifts=1

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

114582 Sending WM_KEYDOWN, Key=51 (Scan code 4), Ctr=1

114582 SendKeyToFS(00040033=[shft+3], KEYUP) ctr=0

114582 KEYDOWN: VK=51, Waiting=0, Shifts=1

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

114691 Sending WM_KEYUP, Key=51 (Scan code 4), Ctr=2

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

114738 Button changed: bRef=0, Joy=0, Btn=4, Released

114738 [buttons.DreamFleet Beech Baron 58 Lite] 3=P0,4,K51,9

117312 Button changed: bRef=0, Joy=0, Btn=5, Pressed

117312 [buttons.DreamFleet Beech Baron 58 Lite] 4=P0,5,K71,8

117312 SendKeyToFS(00000047=[G], KEYDOWN) ctr=0

117312 Sending WM_KEYDOWN, Key=71 (Scan code 34), Ctr=1

117312 KEYDOWN: VK=71, Waiting=0, Shifts=0

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

117359 SendKeyToFS(00000047=[G], KEYUP) ctr=0

117359 Sending WM_KEYUP, Key=71 (Scan code 34), Ctr=1

117468 Button changed: bRef=0, Joy=0, Btn=5, Released

117468 [buttons.DreamFleet Beech Baron 58 Lite] 4=P0,5,K71,8

[Pete Dowson]

I logged toggling the rogue key up and then down, and this is what I got. Perhaps you can interpret it for me?

...

********* FSUIPC, Version 3.82 by Pete Dowson *********

First, version 3.82 is very very much out of date. I cannot support old versions. Current is 3.96, and there's a 3.962 in the Updates Announcement above. Please read the Announcements some time -- there's one which lists supported versions. Always make sure you are up to date before asking for support.

This line:

36223 6=P0,8,K71,8

shows button 8 on Joystick 0 is assigned to the "G" key. Is that your so-called rogue key?

You need to enable Event logging to see the controls being sent.

Please make sure yto update to a supported version before coming back.

Pete

[stankar]

Thanks Pete - didn't realize I was outdated. I'll correct that and check it out and get back to you. Have a good day.

Stan

[Pete Dowson]

Thanks Pete - didn't realize I was outdated. I'll correct that and check it out and get back to you.

What I don't understand is that you claim to have tested without FSUIPC and still had this "ghost" GEAR operation. Yet clearly you have at least two FSUIPC assignments of buttons to send a "G" keypress, the one I already pointed out:

6=P0,8,K71,8 (keycode 71 is 'G').

and the one operated here at the end of the Log extract you posted

117312 Button changed: bRef=0, Joy=0, Btn=5, Pressed

117312 [buttons.DreamFleet Beech Baron 58 Lite] 4=P0,5,K71,8

117312 SendKeyToFS(00000047=[G], KEYDOWN) ctr=0

117312 Sending WM_KEYDOWN, Key=71 (Scan code 34), Ctr=1

117312 KEYDOWN: VK=71, Waiting=0, Shifts=0

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

117359 SendKeyToFS(00000047=[G], KEYUP) ctr=0

117359 Sending WM_KEYUP, Key=71 (Scan code 34), Ctr=1

117468 Button changed: bRef=0, Joy=0, Btn=5, Released

117468 [buttons.DreamFleet Beech Baron 58 Lite] 4=P0,5,K71,8

You have evidently made these aircraft-specific assignments and then forgotten them? If your FSUIPC assignments are all in a mess and you cannot work out what you've done, I recommend you delete the whole INI file and start again.

Regards

Pete

[stankar]

Hi Pete

I downloaded FSUIPC 3.96, deleted all the FS assignments except the hat switch and throttle controls, and reassigned the other yoke switches and buttons in FSUIPC. Still got the same problem. What can I say? Here's the latest log:

Stan

********* FSUIPC, Version 3.96 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\FS2004\MODULES\FSUIPC.DLL" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Stan Shear"

User Addr="stanshear@gmail.com"

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

936 System time = 17/01/2010 13:56:15

936 C:\FS2004\

936 System time = 17/01/2010 13:56:15, FS2004 time = 12:00:00 (00:00Z)

4711 FLIGHTS\OTHER\FLTSIM.flt

4727 AIRCRAFT\c172\Cessna172SP.air

4742 Aircraft="Cessna Skyhawk 172SP"

10904 \\STAN-PC\Users\Stan\Documents\Flight Simulator Files\Vanvouver Piper 26L Ready for takeoff.flt

10967 AIRCRAFT\Flight One PA-28\PA-28-181.air

10982 Aircraft="PIPER PA-28-181 Archer DREAM FLEET - 3"

11216 Clear All Weather requested: external weather discarded

11981 Advanced Weather Interface Enabled

42432 Traffic File #63 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_boats"

42463 Traffic File #14 = "scenery\world\scenery\traffic030528"

42573 Traffic File #69 = "c:\fs2004\addon scenery\canada\nanaimo\scenery\traffic_cycd"

42713 Traffic File #29 = "scenery\world\scenery\traffic_00_woa_continental air lines_su06"

42713 Traffic File #60 = "c:\fs2004\addon scenery\canada\british columbia - victoria - landscape\scenery\traffic_ogden_point"

42853 Traffic File #65 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_cypk_ga"

43228 Traffic File #68 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_seaplane"

43337 Traffic File #62 = "c:\fs2004\addon scenery\canada\british columbia - victoria - landscape\scenery\traffic_victoria_boats"

43337 Traffic File #67 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_heli"

43477 Traffic File #64 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_cruiseships"

43602 Traffic File #16 = "scenery\world\scenery\traffic_000_woa_air canada_su08_fs9"

43680 Traffic File #49 = "scenery\world\scenery\traffic_90_woa_westjet_su06"

43727 Traffic File #66 = "fsaddon\vancouverplus_1\vancouverplus_1_scenery\scenery\traffic_vplus1_ga"

43883 Traffic File #57 = "scenery\world\scenery\trafficacasu05"

46270 Traffic File #58 = "scenery\world\scenery\trafficjzasu05"

46363 Traffic File #43 = "scenery\world\scenery\traffic_254_woa_ultimate ga cessna 402_su06"

46909 Traffic File #15 = "scenery\world\scenery\traffic_000_woa_air canada jazz_wi08"

47159 Traffic File #28 = "scenery\world\scenery\traffic_000_woa_westjet_su08"

47159 Traffic File #32 = "scenery\world\scenery\traffic_10_woa_ups_su05"

47206 Traffic File #44 = "scenery\world\scenery\traffic_26_woa_american airlines_su06"

47206 Traffic File #46 = "scenery\world\scenery\traffic_60_woa_fedex_su05"

47268 Traffic File #52 = "scenery\world\scenery\traffic_kelowna"

47315 Traffic File #55 = "scenery\world\scenery\traffic_pacificcoastalairlines"

58547 AIRCRAFT\DreamFleet Baron 58 Lite\BaronB58_2k4v1.8.air

58547 Aircraft="DreamFleet Beech Baron 58 Lite"

107516 WeatherOptions set, now 40003605 (timer=0)

110339 Button changed: bRef=0, Joy=0, Btn=4, Pressed

110339 [buttons.DreamFleet Beech Baron 58 Lite] 1=P0,4,K51,9

110339 SendKeyToFS(00000033=[3], KEYDOWN) ctr=0

110339 Sending WM_KEYDOWN, Key=51 (Scan code 4), Ctr=1

110339 KEYDOWN: VK=51, Waiting=0, Repeat=Y, Shifts=1

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

110605 Button changed: bRef=0, Joy=0, Btn=4, Released

110605 [buttons.DreamFleet Beech Baron 58 Lite] 1=P0,4,K51,9

112102 Button changed: bRef=0, Joy=0, Btn=5, Pressed

112102 [buttons.DreamFleet Beech Baron 58 Lite] 0=P0,5,K50,9

112102 SendKeyToFS(00040033=[shft+3], KEYUP) ctr=0

112102 Sending WM_KEYUP, Key=51 (Scan code 4), Ctr=1

112102 SendKeyToFS(00040032=[shft+2], KEYDOWN) ctr=1

112102 KEYUP: VK=51, Waiting=0

112149 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=3

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

112149 KEYUP: VK=16, Waiting=0

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

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

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

112211 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=1

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

112305 Button changed: bRef=0, Joy=0, Btn=5, Released

112305 [buttons.DreamFleet Beech Baron 58 Lite] 0=P0,5,K50,9

112867 Traffic File #39 = "scenery\world\scenery\traffic_213_woa_ultimate ga learjet 45_su06"

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

116969 [buttons] 7=P0,6,K117,8

116969 SendKeyToFS(00040032=[shft+2], KEYUP) ctr=0

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

116969 SendKeyToFS(00000075=[F6], KEYDOWN) ctr=1

116969 KEYUP: VK=50, Waiting=0

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

117016 KEYUP: VK=16, Waiting=0

117079 Sending WM_KEYDOWN, Key=117 (Scan code 64), Ctr=1

117079 KEYDOWN: VK=117, Waiting=0, Repeat=N, Shifts=0

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

117219 Button changed: bRef=0, Joy=0, Btn=6, Released

117219 [buttons] 7=P0,6,K117,8

136704 KEYDOWN: VK=91, Waiting=0, Repeat=N, Shifts=32

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

138513 SendKeyToFS(00000075=[F6], KEYUP) ctr=0

138513 Sending WM_KEYUP, Key=117 (Scan code 64), Ctr=1

[stankar]

Pete I found the problem. So darn obvious and yet so difficult to pinpoint.

I just removed the individual references to gear up and gear down in FS9.cfg and left the gear toggle, as follows:

//BUTTON_DOWN_EVENT_04=GEAR_UP

//BUTTON_DOWN_EVENT_05=GEAR_DOWN

GEAR_TOGGLE=71,8

I don't know the technical explanation for this, but the problem is solved and I thank you for your patience.

FSUIPC still remains the most useful addon I've ever purchased or downloaded. I don't have to tell you that you are a remarkable programmer (Iused to lecture VB.Net and applications at the University of Cape Town in South Africa before I retired), and I humbly acknowledge your talent.

Take care and keep up the wonderful work for the FS community.

Regards

Stan

[Pete Dowson]

Hi Pete

I downloaded FSUIPC 3.96, deleted all the FS assignments except the hat switch and throttle controls, and reassigned the other yoke switches and buttons in FSUIPC. Still got the same problem. What can I say?

I didn't say updating FSUIPC would "fix" anything, because there's nothing to fix. I needed you to update because I don't support old versions.

As I pointed out, you had the keypress "G" assigned in FSUIPC to at least two of your Buttons. Until you delete those or re-program them they will continue to send "G" to FS whenever you press them. It seems you aren't reading my replies. I don't see any point in you showing me log files if you don't read my analysis of them.

Here's the latest log:

And what do you think that should show? You don't even say what the log is of. You still haven't bothered to enable Event logging as I suggested.

All I can see from this log is that you appear to have reprogrammed one of the affected button (0,5) to send "Shift+2" instead of "G":

112102 Button changed: bRef=0, Joy=0, Btn=5, Pressed

112102 [buttons.DreamFleet Beech Baron 58 Lite] 0=P0,5,K50,9

112102 SendKeyToFS(00040032=[shft+2], KEYDOWN) ctr=1

There's no "G" being sent in this log, whilst there was last time.

I'm not sure what you are asking of me now. I think I've helped all I can. If you still don't know what you are doing, why not simply start again, delete your FSUIPC INI file, as I suggested? If you want anything else from me please enable the logging options I suggest and tell me exactly what your logs are supposed to show you doing.

Regards

Pete

[stankar]

Hi Pete

We may have crossed lines in the last two posts - as you will see in the post just before your last reply, I found the problem. One learns every day, but it can be frustrating.

Thanks again.

Stan

[Pete Dowson]

Hi Pete

We may have crossed lines in the last two posts - as you will see in the post just before your last reply, I found the problem.

Ah, good. Well done!

Pete