I have all my controls' bindings set up nicely. There's just one problem, despite my best efforts to name them all differently, ie, 737/777, H-Jet, it seems the sensitivities can't be saved per plane. If I set up the sensitivities for the 737/777 for the reversers to work ok it messes up the settings for the H-Jet despite it being named H-Jet. Am I doing something wrong or is this a limitation to the program?

Thanks, Jack

Assuming this isn't a bug...but it does have the appearance of a potential conflict.

If I'm understanding your particular setup, It's helpful to understand that the per-aircraft settings cascade downwards. So ideally you don't want to set anything that will vary downwards...

And that generally means that everyone will have a different way of categorizing their addon hierarchies that aren't necessarily "wrong" or "right" (and to be clear, i'm still cleaning/refining my own 👍).

In your case, I would suggest a hierarchy something like:

General Controls: Airliners - Jet (this is for broadly standard assignments like throttle, landing gear, flaps or other things specific to a CLASS of aircraft (IMHO))

Airplane Controls: PMDG (this might be where your reversers sensitivities go - ONLY IF they are the same across both your PMDG 737 and 777)

Specific PMDG 737. Make one for each PMDG 'liner that has a DIFFERENT control assignments from the others. e.g., you might end up with PMDG Twins here, and PMDG quads (when the 74x's finally arrive!).

 

and then another like:

General: Biz Jets (e.g., generally twin jet, etc)

Airplane: Standard Controls (another could be "With Reversers" or some combo like "Spoilers and Reversers" or whatevs)

Specific HA420: whatever the HondaJet needs that is DIFFERENT from anything above.

 

Another e.g. to contrast, I have one that is:

General: Helicopters

Airplane: Turbine

Specific: Taogs OH6

 

Hope that helps - the new 2024 setup is better than 2020, but does require either forethought (or in my case, lots of re-do's) 😉. And don't forget that you can duplicate and rename profiles at each level - has been VERY helpful as I build out hierarchies.

 

Edited February 23Feb 23 by UrgentSiesta

18 minutes ago, UrgentSiesta said:

Assuming this isn't a bug...but it does have the appearance of a potential conflict.

If I'm understanding your particular setup, It's helpful to understand that the per-aircraft settings cascade downwards. So ideally you don't want to set anything that will vary downwards...

And that generally means that everyone will have a different way of categorizing their addon hierarchies that aren't necessarily "wrong" or "right" (and to be clear, i'm still cleaning/refining my own 👍).

In your case, I would suggest a hierarchy something like:

General Controls: Airliners - Jet (this is for broadly standard assignments like throttle, landing gear, flaps or other things specific to a CLASS of aircraft (IMHO))

Airplane Controls: PMDG (this might be where your reversers sensitivities go - ONLY IF they are the same across both your PMDG 737 and 777)

Specific PMDG 737. Make one for each PMDG 'liner that has a DIFFERENT control assignments from the others. e.g., you might end up with PMDG Twins here, and PMDG quads (when the 74x's finally arrive!).

 

and then another like:

General: Biz Jets (e.g., generally twin jet, etc)

Airplane: Standard Controls (another could be "With Reversers" or some combo like "Spoilers and Reversers" or whatevs)

Specific HA420: whatever the HondaJet needs that is DIFFERENT from anything above.

 

Another e.g. to contrast, I have one that is:

General: Helicopters

Airplane: Turbine

Specific: Taogs OH6

 

Hope that helps - the new 2024 setup is better than 2020, but does require either forethought (or in my case, lots of re-do's) 😉. And don't forget that you can duplicate and rename profiles at each level - has been VERY helpful as I build out hierarchies.

 

Thanks. I’ve done exactly that. It works great. What I’m talking about is the Hardware Settings gear and different sensitivities for different planes. 
 

The bindings work perfectly in all other regards. 

It will save sensitives per aircraft.  Based on your screenshots I believe you need to NOT do this “in flight” … hit Esc (don’t select the menu gear icon from auto hide menu in flight), then settings, then  Controls, make changes and save, then return to flight.  I think it’s a bug.

10 minutes ago, SayAgain said:

It will save sensitives per aircraft.  Based on your screenshots I believe you need to NOT do this “in flight” … hit Esc (don’t select the menu gear icon from auto hide menu in flight), then settings, then  Controls, make changes and save, then return to flight.  I think it’s a bug.

I just tried exactly as you described. I hit Esc then set the sensitivity for the 737 and loaded the 737. But when I loaded the Hjet it had the same sensitivity settings as the 737.

I have a feeling that the sensitivities cannot be saved per aircraft unless I’m still not doing it right.

23 minutes ago, SayAgain said:

It will save sensitives per aircraft.  Based on your screenshots I believe you need to NOT do this “in flight” … hit Esc (don’t select the menu gear icon from auto hide menu in flight), then settings, then  Controls, make changes and save, then return to flight.  I think it’s a bug.

Dang. This is creepy. I just tried the exact same procedure again and now it works. I have aircraft specific sensitivity settings. Bizarre.

As I recall (in my case anyway), the entry method (in flight or outside of a flight) to the controller configuration/setup caused the aircraft specific saving issue for me.  Going by memory right now as I’m in the office … but the “control” configuration performed “in flight” doesn’t offer a “Save” option (just back).

Hardware settings (sensitivities and null zones, etc) cannot be set per aircraft.  It's just one set of settings for everything.

I hope they do make it per aircraft at some point.   I have fully linear for the Fenix but some other aircraft (particularly smaller GA) really need some tweaks.

[EDIT:  Just read SayAgain's comments. Hmm, checking this out now!]

Edited February 23Feb 23 by JYW

20 minutes ago, SayAgain said:

As I recall (in my case anyway), the entry method (in flight or outside of a flight) to the controller configuration/setup caused the aircraft specific saving issue for me.  Going by memory right now as I’m in the office … but the “control” configuration performed “in flight” doesn’t offer a “Save” option (just back).

I’ll have to back too and look as I don’t recall a save either but it’s probably these. At least I got it to work.

1 minute ago, JYW said:

Hardware settings (sensitivities and null zones, etc) cannot be set per aircraft.  It's just one set of settings for everything.

I hope they do make it per aircraft at some point.   I have fully linear for the Fenix but some other aircraft (particularly smaller GA) really need some tweaks.

[EDIT:  Just read SayAgain's comments. Hmm, checking this out now!]

It does work because I just spent a couple hours testing and troubleshooting. The thing for me is i haven’t seen any detailed documentation from MS/Asobo on this.

2 minutes ago, JYW said:

Hardware settings (sensitivities and null zones, etc) cannot be set per aircraft.

Pretty sure it’s possible, you have to select the configuration yourself manually when you change aircraft.  I have several different ones, A2A and PMDG and FSLabs etc. 

6 minutes ago, SayAgain said:

Pretty sure it’s possible, you have to select the configuration yourself manually when you change aircraft.  I have several different ones, A2A and PMDG and FSLabs etc. 

I look forward to checking it out.   I've never experimented with this as the fact that there are no profiles to be named etc always led me to believe that the hardware sensitivites settings were fixed, for all aircraft.   I'll be very happy to see that it works!

Edited February 23Feb 23 by JYW

5 minutes ago, JYW said:

I look forward to checking it out.   I've never experimented with this as the fact that there are no profiles to be named etc always led me to believe that the hardware sensitivites settings were fixed, for all aircraft.   I'll be very happy to see that it works!

I know it works. I just created two different ones for the 737 and the H-Jet and tested vigorously.

1 hour ago, JYW said:

led me to believe that the hardware sensitivites settings were fixed, for all aircraft

Well, I can certainly see the confusion, overall that Controller UI design is pretty bad (better than it was, but still pretty bad).  And then Asobo have the “locked” icon profiles and then have to cycle thru each and every profile rather just pick form a dropdown list … etc. etc.   They need a UI consultant (PC users are not the same as XBOX users).