Issue with aircraft specific buttons

[schroewo]

Hi,

after loading a saved flight the aircraft specific buttons don't work. To get the buttons work I've to open FSUIPC and close it.

This is the log file with enabled trace of buttons commands:

********* FSUIPC4, Version 4.593 by Pete Dowson *********

Reading options from "D:\Games\fsx\Modules\FSUIPC4.ini"

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

User Name="Wolfgang Schroeder"

User Addr="webmaster@cpp-tutor.de"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

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

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

47 System time = 01/03/2010 21:57:12

47 FLT UNC path = "\\WOLFGANG-PC\Users\Wolfgang\Documents\Flight Simulator X-Dateien\"

47 FS UNC path = "D:\Games\fsx\"

468 LogOptions=40000000 00000001

468 SimConnect_Open succeeded: waiting to check version okay

1903 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

1903 Initialising SimConnect data requests now

1903 FSUIPC Menu entry added

1935 D:\Games\fsx\FLIGHTS\OTHER\FLTSIM.FLT

1935 D:\Games\fsx\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

9766 D:\Games\fsx\SimObjects\Airplanes\Aerosoft Twin Otter 300\DHC6.AIR

9766 D:\fsx_flightplans\EurSightseeing\Part1\EGEHEGPC.PLN

9766 Weather Mode now = Custom

9766 \\WOLFGANG-PC\Users\wolfgang\documents\flight simulator x-dateien\europe.FLT

49016 System time = 01/03/2010 21:58:01, Simulator time = 07:30:12 (05:30Z)

49016 Aircraft="de Havilland Canadian Twin Otter Loganair (flybe)"

49016 [buttons] now aircraft-specific:

49016 2=P0,6,K51,9

55755 Advanced Weather Interface Enabled

71729 Button changed: bRef=0, Joy=0, Btn=23, Pressed

71729 [buttons] 8=P0,23,C66860,0

71729 FS Control Sent: Ctrl=66860, Param=0

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

74865 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9

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

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

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

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

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

74896 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1

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

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

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

74990 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9

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

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

75037 KEYUP: VK=51, Waiting=0

75037 KEYUP: VK=16, Waiting=0

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

77127 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9

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

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

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

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

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

77174 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1

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

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

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

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

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

77299 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9

77299 KEYUP: VK=51, Waiting=0

77299 KEYUP: VK=16, Waiting=0

Any hints?

Regards

Wolfgang

[Pete Dowson]

This is the log file with enabled trace of buttons commands:

I'd need to see all the relevant parts of the INI file too, please.

Pete

[schroewo]

Hi Pete,

don't what the 'relevant parts' are but these are the button sections:

[buttons]

ButtonRepeat=20,10

1=P0,5,C65752,0

2=P0,8,C65759,0

3=P0,9,C65758,0

4=P0,10,K65,9

5=P0,11,K65,8

6=P0,12,K48,8

7=P0,13,K220,8

8=P0,23,C66860,0

9=P0,28,C66854,0

10=P0,19,C65789,0

11=P0,21,C65790,0

12=P0,15,C65655,0

13=P0,17,C65656,0

14=P0,6,K51,9

[buttons.de Havilland Canada Twin Otter Flightsimmer.de DE]

0=P0,11,K65,8

1=P0,10,K65,9

2=P0,29,K51,9

[buttons.de Havilland Canadian Twin Otter Loganair (flybe)]

0=R0,22,C65880,0

1=R0,20,C65879,0

2=P0,6,K51,9

Regards

Wolfgang

[Pete Dowson]

after loading a saved flight the aircraft specific buttons don't work.

Do you think that's illustrated in the Log someplace? Here's what I see:

49016 Aircraft="de Havilland Canadian Twin Otter Loganair (flybe)"

The aircraft is the one with only these specific assignments (the rest being the generally assigned ones):

0=R0,22,C65880,0

1=R0,20,C65879,0

2=P0,6,K51,9

You pressed button 23, which isn't specifically programmed for this aircraft, so the general assignment is used:

71729 Button changed: bRef=0, Joy=0, Btn=23, Pressed

71729 [buttons] 8=P0,23,C66860,0

71729 FS Control Sent: Ctrl=66860, Param=0

Then you pressed button 6 (which, though not relevant, coincidentally has the same specific assignment as in the general section in any case):

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

74865 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9

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

Then again:

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

77127 [buttons.de Havilland Canadian Twin Otter Loganair (flybe)] 2=P0,6,K51,9

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

Any hints?

I can't see anything wrong with that. Can you explain? What is actually going wrong? I can't make anything odd happen here which necessitates going into FS options (which you didn't do during the course of the log).

Please, if there's a problem, I need to know how to reproduce it and I need to know pretty qiuickly as I've just about wrapped up the next major update release ready for Wednesday.

Regards

Pete

[schroewo]

Hi Pete,

to elimate any aircraft specific behaviour I switched over to the default Cessna 172. Then I programmed button 6 to send the command SHIFT+3 to popup the GPS.

And here is what I did:

1, Starting FSX with the Cessna.

2. Waiting a few seconds

3. Pressed the button 6 3 times -> no GPS shown

4. Wating a few seconds

5. Opened FSUIPS via the menu

6. Pressed the cancel button to close FSUIPC

7. Pressed the button 6 4 times -> GPS is shown

********* FSUIPC4, Version 4.593 by Pete Dowson *********

Reading options from "D:\Games\fsx\Modules\FSUIPC4.ini"

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

User Name="Wolfgang Schroeder"

User Addr="webmaster@cpp-tutor.de"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

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

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

47 System time = 02/03/2010 10:04:10

47 FLT UNC path = "\\WOLFGANG-PC\Users\Wolfgang\Documents\Flight Simulator X-Dateien\"

47 FS UNC path = "D:\Games\fsx\"

453 LogOptions=40000000 00000001

453 SimConnect_Open succeeded: waiting to check version okay

1872 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

1872 Initialising SimConnect data requests now

1872 FSUIPC Menu entry added

1903 D:\Games\fsx\FLIGHTS\OTHER\FLTSIM.FLT

1903 D:\Games\fsx\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

9423 D:\Games\fsx\SimObjects\Airplanes\C172\Cessna172SP.AIR

9423 Weather Mode now = Theme

9423 \\WOLFGANG-PC\Users\wolfgang\documents\flight simulator x-dateien\test.FLT

36348 System time = 02/03/2010 10:04:47, Simulator time = 21:12:17 (02:12Z)

36348 Aircraft="Cessna Skyhawk 172SP Paint1"

36348 [buttons] now aircraft-specific:

36348 0=P0,6,K51,9

39297 Advanced Weather Interface Enabled

61901 Sim stopped: average frame rate for last 24 secs = 23.6 fps

65879 Button changed: bRef=0, Joy=0, Btn=23, Pressed

65879 [buttons] 8=P0,23,C66860,0

65879 FS Control Sent: Ctrl=66860, Param=0

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

68797 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

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

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

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

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

68843 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1

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

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

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

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

68968 KEYUP: VK=51, Waiting=0

68968 KEYUP: VK=16, Waiting=0

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

69015 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

69842 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

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

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

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

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

69889 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1

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

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

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

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

70013 KEYUP: VK=51, Waiting=0

70013 KEYUP: VK=16, Waiting=0

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

70060 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

70856 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

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

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

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

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

70887 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1

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

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

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

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

71027 KEYUP: VK=51, Waiting=0

71027 KEYUP: VK=16, Waiting=0

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

71059 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

73024 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

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

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

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

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

73071 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=1

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

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

73118 [buttons.Cessna Skyhawk 172SP Paint1] 0=P0,6,K51,9

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

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

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

73196 KEYUP: VK=51, Waiting=0

73196 KEYUP: VK=16, Waiting=0

Regards

Wolfgang

[Pete Dowson]

to elimate any aircraft specific behaviour I switched over to the default Cessna 172. Then I programmed button 6 to send the command SHIFT+3 to popup the GPS.

But you already do have that button programmed to send Shift+3. It is part of your default assignments for all aircraft. There is nothing "aircraft specific" about it. Are you saying that with a button already assigned to do something, having it ALSO defined as aircraft specific cancels BOTH actions, until you go into FSUIPC options?

I'm really not clear why you'd pick specifically on a button which you have programmed as Shift+3 for all aircraft. Do you get the same problem with genuinely aircraft-specific assignments?

If it is only with such dual assignments then that might be why I cannot reproduce it. I'll try that.

[LATER]

No, I cannot make it go wrong at all, even with a duplicated assignment like yours. sorry. It's a bit weird. The routine FSUIPC uses to load up the settings when you go into the Options is exactly the same as that used when it detects (and logs) the aircraft name.

I'll see if I can make it happen with something closely resembling your original button assignments, as you posted earlier.

[LATER STILL]

No. With identical assignments to yours, but different aircraft names as I don't have those, it all works as expected.

Sorry, I am at a loss with this. I would love to fix it before finishing the major Release I've got almost ready, but I'd need to reproduce it. I've pored over the code too and as I say it is identical both ways. All I can suggest for now is that you try 4.60 when it is avialable, before the end of the week (hopefully tomorrow in fact), and if you still get a problem I will have to start adding more logging to special test copies for you to run. As it only happens on your system that's the only way I can think to do it., but I cannot afford to hold up this release at this stage.

Regards

Pete

[schroewo]

So this what I've done in the meantime:

I completely removed FSUIPC and installed a fresh 4.57 version so no duplicated button assigments exists. Then I assigned only the button 6 to send the "SHIFT+3" command for the standard Cessna 172. At this point there were no problems with the key assignment, all things work as expected.

Then I renamed the version 4.57 and copy the newer version 4.588 to the module folder and the problem recurs. After that I renamed the 4.588 version and restored the older 4.57 version and the problem went away. Strange.

If you want I can upload the test flight (with the standard Cessna) and the complete module folder (except the key :wink: ) to my website and send you the download link.

Regards

Wolfgang

[Pete Dowson]

If you want I can upload the test flight (with the standard Cessna) and the complete module folder (except the key :wink: ) to my website and send you the download link.

No, I really won't be able to do anything this week. Wait for 4.60, test with that. Let me know if it is still a problem and we'll go from there.

I have simply got to get this finished today and tomorrow, then I am away till Monday.

Regards

Pete

[schroewo]

I've installed version 4.6 and the problem still exists. The problem also exists if assign the button global. Maybe we can do further testings when you've time next week. In the meantime I will switch back to 4.57 where everything works.

Kind regards

Wolfgang

[Pete Dowson]

I've installed version 4.6 and the problem still exists. The problem also exists if assign the button global. Maybe we can do further testings when you've time next week. In the meantime I will switch back to 4.57 where everything works.

The problem really is that no matter what i do, even if I have the same button assignments as you, there is no problem. I cannot fix it without seeing what is wrong. The code path for the chasnge of aircraft title follows the same in the options entry/exit as far as button assignments are concerned.

[LATER]

Just some more ideas. Some things I shall throw out. Please contradict me if any are false.

1. In all of what you've reported, the change to the aircraft and the consequent change in the button assignments has been correctly logged. So this means that the correct assignment tables have been constructed.

2. In all of what you've shown there's no sign of ANY button use at all before you get it working, you say by going into the Options and back out. There's no indication that ANY buttons work before that, none at all.

3. This suggests that the joystick is not actually being detected until then -- i.e. until the joysticks have been "initialised" again by entry to the options.

If this is the case then I have probably been looking in the wrong places. One of the most recent changes in FSUIPC4 was to have the Buttons testing use the results of the axis scanning -- i.e. use DirectInput instead of the old joy API.

I noticed that your "joystick" has a lot of buttons -- I noticed numbers up to 29. But does it have any axes at all? If so, are you using any, are any assigned in FSUIPC?

Could you reply to this as soon as possible, please, because if I am going down the right road here I should be able to fix this quite quickly. At least I will know where to look. It may simply be that when there are no axes assigned, FSUIPC doesn't initialise the DirectInput devices until it actually MUST do, i.e. in the options.

If this is the case I don't understand why you'd only report it as "after loading a saved flight the aircraft specific buttons don't work". If what I am saying is anything like the truth then I would expect it never to see any buttons, aircraft-specific or not, till you enter the Options.

In the case that I am wrong, could you please do some simple basic tests for me? As follows:

1) Make a safe copy of your FSUIPC4 INI file, then delete all of the button assignments, both global and aircraft specific.

2) Assign one button only, as global.

3) Close down FSX and restart it.

4) Test that one button. Does it work initially? OR does it only work after visiting the Options?

5) Now load a different aircraft, then in Buttons options, select 'aircraft specific' and assign another button, a different one.

6) Close down FSX and restart it.

7) Test that new button. Does it work initially? It shouldn't because the aircraft will be wrong.

8 ) Load the correct aircraft, and test that button. Does it work then? OR does it only work after visiting the Options?

9) Assign the SAME button as was global in step 2, but now as aircraft-specific.

10) Close FSX and restart it.

11) Test that button with the default aircraft. Does it work? (Don't go into Options)

12) Load the other aircraft and test that button. Does it work then? OR does it only work after visiting the Options?

I think we should transfer this to email from now on as I am going to have to start sending you files, or at least private links to files. I have a little more time tomorrow than I expected -- seems my wife has changed our trip to Friday now. Please email me as soon as you can on petedowson@btconnect.com . I'll be up for perhaps another 30 minutes but i'll be at it here in the morning , only a few hours from now.

Thanks,

Pete

[Pete Dowson]

Just in case I'm right in my surmises that this is nothing to do with "aircraft specific" or "loading a flight", but only to do with having only buttons on the joysticks and no axes at all, could you download this little updated 4.60 version and test it as soon as you can, please?

http://fsuipc.simflight.com/beta/FSUIPC460a.zip

[LATER]

It's Thursday now and I don't have much time, so I've assumed what I surmised is actually true and have replaced 4.60 with 4.60a in all the download ZIPs, both from here and from the Schiratti site. If this still does not fix your specific problem then I'll need the results of that series of tests I listed and I'll have to look again next week.

Thanks,

Pete

[schroewo]

Hey great! With version 4.60a it works as expected. Thanks for your patient and outstanding support!

Kind regards

Wolfgang

[Pete Dowson]

Hey great! With version 4.60a it works as expected. Thanks for your patient and outstanding support!

Good!

I'd have fixed it much fast (within an hour) if it hadn't been for the misleading business about aircraft-specific and flight loading. That was all irrelevant it seems. It was instead an initialisation problem for setups with no axis assignments, and would have affected all button assignments up until you entered the FSUIPC options.

Regards

Pete