Aircraft Specific (Buttons) Bug? - FSUIPC 3.53

[jordanal]

Hi Pete,

Thanks again for supporting FSim all these years.

I just started setting up "Aircraft Specific" settings (w/shortaircraftnameOK enabled) in the ini file using FSUIPC 3.53 registered. As you can see ,I did one section for the PMDG 747 and 737 each using the joystickcalibration and buttons sections. The problem is, when I come back into the FSUIPC GUI, the joysticks tab properly indicates "aircraft specific" as being checked but the Buttons tab does not. Now, if I then check the "aircraft specific" box on the Buttons tab, the shortname does appear on the FSUIPC GUI title bar and buttons seem to be assigned, but for some reason "aircraft specific" settings are not on by default even though the section in the ini file seems to be properly recongnized. I hope I've explained this well enough, but if I haven't, let me know and I'll try to rephrase.

Oh, one other thing; it would also be easier if the buttons assignments in the ini file started with one instead of zero. It took me a few minutes to realize that in order to identify my actual, physical buttons on the devices it was necessary to add 1 to the button assignemnts as listed in the ini. No joystick I've ever used has a button zero, :wink: Is it possible to change this sometime in the future?

BTW, I can't wait 'till you have the aircraft specific axis assignemnts facitlity in FSUIPC, that'll be absolutly fabulous :)

Pertinent ini sections as follows:

ShortAircraftNameOk=Yes

[JoystickCalibration.B737-]

ExclThrottleSet=No

SepRevsJetsOnly=No

FlapsSetControl=0

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=0

RudderTrimControl=0

CowlFlaps1Control=0

CowlFlaps2Control=0

CowlFlaps3Control=0

CowlFlaps4Control=0

Aileron=-16193,-582,444,16065

SlopeAileron=5

Elevator=-16193,-453,444,16065

SlopeElevator=5

Rudder=-16066,0,0,16192

SlopeRudder=5

LeftBrake=-16066,16192

SlopeLeftBrake=5

RightBrake=-16066,16192

SlopeRightBrake=5

Throttle1=-16256,-14321,-13418,16256

Throttle2=-16193,-14774,-14000,16192

Spoilers=-16193,16192

Flaps=-16129,16129

[buttons.B737-]

1=P4,1,K65,12 ;TAB+A, Yoke, B 2

2=P4,4,C66079,0 ;GEAR_UP, Yoke, B 5

3=P4,5,C66080,0 ;GEAR_DOWN, Yoke, B 6

4=P4,12,K82,9 ;Shft+R, Yoke, B 13

5=P4,15,C65789,0 ;SIM_RATE_INC, Yoke, B 16

6=P4,16,C65790,0 ;SIM_RATE_DECR, Yoke, B 17

7=P4,19,C65656,0 ;ZOOM_OUT, Yoke, B 20

8=P4,20,C65655,0 ;ZOOM_IN, Yoke, B 21

9=R1,0,K80,11 ;Ctrl+Shft+P, THQ, B 1

10=R1,1,K80,14 ;Ctrl+TAB+P, THQ, B 2

11=R1,2,K83,11 ;Ctrl+Shft+S, THQ, B 3

12=R1,3,K83,14 ;Ctrl+TAB+S, THQ, B 4

13=R1,4,K65,11 ;Ctrl+Shft+A, THQ, B 5

14=R1,5,K65,14 ;Ctrl+TAB+A, THQ, B 6

15=R1,6,K66,11 ;Ctrl+Shft+B, THQ, B 7

16=R1,7,K66,14 ;Ctrl+TAB+B, THQ, B 8

17=P1,8,K72,10 ;Ctrl+H, THQ, B 9

18=P1,9,K78,10 ;Ctrl+N, THQ, B 10

19=P1,10,C65751,0 ;LANDING_LIGHTS_TOGGLE, THQ, B 11

20=P1,11,C66240,0 ;TOGGLE_TAXI_LIGHTS, THQ, B 12

21=R1,12,K90,11 ;Ctrl+Shft+Z, THQ, B 13

22=R1,13,K90,14 ;Ctrl+TAB+Z, THQ, B 14

23=R1,14,K72,11 ;Ctrl+Shft+H, THQ, B 15

24=R1,15,K72,14 ;Ctrl+TAB+H, THQ, B 16

25=R1,16,K86,11 ;Ctrl+Shft+V, THQ, B 17

26=R1,17,K86,14 ;Ctrl+TAB+V, THQ, B 18

27=P1,18,K65,10 ;Ctrl+A, THQ, B 18

28=P1,19,K80,10 ;Ctrl+P, THQ, B 20

29=P1,20,K86,9 ;Shft+V, THQ, B 21

30=P1,21,K86,10 ;Ctrl+V, THQ, B 22

31=P1,22,C65560,0 ;STROBES_TOGGLE, THQ, B 23

[JoystickCalibration.747-400]

ExclThrottleSet=No

SepRevsJetsOnly=No

FlapsSetControl=0

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=0

RudderTrimControl=0

CowlFlaps1Control=0

CowlFlaps2Control=0

CowlFlaps3Control=0

CowlFlaps4Control=0

Aileron=-16193,-582,444,16065

SlopeAileron=5

Elevator=-16193,-453,444,16065

SlopeElevator=5

Rudder=-16066,0,0,16192

SlopeRudder=5

LeftBrake=-16066,16192

SlopeLeftBrake=5

RightBrake=-16066,16192

SlopeRightBrake=5

Throttle1=-16256,-14321,-13418,16256

Throttle2=-16193,-14774,-14000,16192

Throttle3=-16193,-14645,-13871,16192

Throttle4=-16256,-14708,-13934,16256

Spoilers=-16193,16192

Flaps=-16129,16129

[buttons.747-400]

1=P4,1,K65,12 ;TAB+A, Yoke, B 2

2=P4,4,C66079,0 ;GEAR_UP, Yoke, B 5

3=P4,5,C66080,0 ;GEAR_DOWN, Yoke, B 6

4=P4,12,K82,9 ;Shft+R, Yoke, B 13

5=P4,15,C65789,0 ;SIM_RATE_INC, Yoke, B 16

6=P4,16,C65790,0 ;SIM_RATE_DECR, Yoke, B 17

7=P4,19,C65656,0 ;ZOOM_OUT, Yoke, B 20

8=P4,20,C65655,0 ;ZOOM_IN, Yoke, B 21

9=R1,0,K80,11 ;Ctrl+Shft+P, THQ, B 1

10=R1,1,K80,14 ;Ctrl+TAB+P, THQ, B 2

11=R1,2,K83,11 ;Ctrl+Shft+S, THQ, B 3

12=R1,3,K83,14 ;Ctrl+TAB+S, THQ, B 4

13=R1,4,K65,11 ;Ctrl+Shft+A, THQ, B 5

14=R1,5,K65,14 ;Ctrl+TAB+A, THQ, B 6

15=R1,6,K66,11 ;Ctrl+Shft+B, THQ, B 7

16=R1,7,K66,14 ;Ctrl+TAB+B, THQ, B 8

17=P1,8,K72,10 ;Ctrl+H, THQ, B 9

18=P1,9,K78,10 ;Ctrl+N, THQ, B 10

19=P1,10,C65751,0 ;LANDING_LIGHTS_TOGGLE, THQ, B 11

20=P1,11,C66240,0 ;TOGGLE_TAXI_LIGHTS, THQ, B 12

21=R1,12,K90,11 ;Ctrl+Shft+Z, THQ, B 13

22=R1,13,K90,14 ;Ctrl+TAB+Z, THQ, B 14

23=R1,14,K72,11 ;Ctrl+Shft+H, THQ, B 15

24=R1,15,K72,14 ;Ctrl+TAB+H, THQ, B 16

25=R1,16,K86,11 ;Ctrl+Shft+V, THQ, B 17

26=R1,17,K86,14 ;Ctrl+TAB+V, THQ, B 18

27=P1,18,K65,10 ;Ctrl+A, THQ, B 18

28=P1,19,K80,10 ;Ctrl+P, THQ, B 20

29=P1,20,K86,9 ;Shft+V, THQ, B 21

30=P1,21,K86,10 ;Ctrl+V, THQ, B 22

31=P1,22,C65560,0 ;STROBES_TOGGLE, THQ, B 23

[Pete Dowson]

The problem is, when I come back into the FSUIPC GUI, the joysticks tab properly indicates "aircraft specific" as being checked but the Buttons tab does not. Now, if I then check the "aircraft specific" box on the Buttons tab, the shortname does appear on the FSUIPC GUI title bar and buttons seem to be assigned, but for some reason "aircraft specific" settings are not on by default even though the section in the ini file seems to be properly recongnized.

This is normal. Why do you think it is a problem? It all works doesn't it?

The way aircraft specific settings work is NOT the same between the two sections. With the Joystick Calibrations, the specific section is used INSTEAD of any generic section you may also have. It is one or the other. Hence the checkbox shows that.

In the case of Buttons it is much more complex. Only those buttons you have re-programmed to be aircraft-specific are aircraft-specific, but any others, defined for general use, will still have their programming action operational. Hance the Button programming is much more flexible (and as a result more complex, sorry). The Key Press programming is the same.

I did think about making the Joystick Calibration similar, but couldn't think of an easy way to disable calibrations and assignments which you didn't want interfering, so I made the system do a straight swap in this case. Besides which, it is a much more likely need to have a 'core' of button assignments which are applicable to all aircraft.

I did think this was documented somewhere, but maybe I didn't make it clear enough.

Oh, one other thing; it would also be easier if the buttons assignments in the ini file started with one instead of zero. It took me a few minutes to realize that in order to identify my actual, physical buttons on the devices it was necessary to add 1 to the button assignemnts as listed in the ini. No joystick I've ever used has a button zero

Well, I haven't seen any that have numbered buttons at all. The Windows API numbers the buttons from zero, so it is entirely logical for me to do so too. It is a standard practice going back many years now.

Is it possible to change this sometime in the future?

No, not at all. It would certainly cause confusion all round. Pretty much all the sophisticated gear used to build cockpits uses numbering starting from zero, and in any case suddenly renumbering everything in an update will mean everyone suddenly having unexpected problems needing re-programming in FSUIPC options!

BTW, I can't wait 'till you have the aircraft specific axis assignemnts facitlity in FSUIPC, that'll be absolutly fabulous :)

See the Announcements above. And be careful -- joysticks are numbered from 0, andfaxes are "numbered" with lettrers, X Y Z R U V, following the Windows API and general harware practice for the last 10 years or more. I doubt if any of your joysticks are numbered thus. ;-)

Regards,

Pete

[jordanal]

LOL, OK Pete, fair enough and thanks for a timely reply. As soon as you mentioned the "combining" of sections for buttons and keys I realized where I went wrong in my logic and that I did read that info in the Advanced users doc (yes, I actually read the manual, LOL) I understand about the starting with one being too big of change, it just seemed odd at first when my buttons weren't matching my ini file settings.

LOL, OK about axis-0, I'm gonna create labels for them starting with zero, LOL... :D

[Pete Dowson]

If you have just downloaded the FSUIPC 3.536 Zip, please do so again. I just found out the module I Zipped was corrupted and have uploaded it again. The cirrect one bears a timestamp of about 01:16 (AM).

Regards,

Pete

[jordanal]

Yup, sure enough, the module I pulled down was from 12:07am. Re-downloading the zip again now. Thanks for the heads-up...

v/r,

AL