It would be great and in fact a very important thing to make it possible to
bind a control profile to a specific aircraft. So that when the plane is
loaded, a specific control profile is selected. This will save you from
manually switching the profile every time you change the plane (and the chance
that the user will forget to do it himself). Agree, it is impossible to use a
single profile for different types of aircraft. P.S. It is also worth
considering that it is better to contain only changed assignments in a custom
profile, and not everything in a row. If the command is not changed, then take
assignments from the default profile.
++++ true feature…
I use spad.next, which allows profile change based on aircraft title. This also allows you to setup common controls in the sim control profile. It also allows more complex commands than just key/control assignments, and recognises a swathe of game controllers.
I agree with you on the ask but even having Spad.Next(which is a wonderful add-on for MSFS)…keeping up with changes to the variables in each update requires time to update and can be frustrating chasing down the right event, variable that works properly. Also, using DevMode (using CTRL+G) is helpful. I agree with a “default profile” or baseline assignment per aircraft but people have different setups is the problem. This is my perspective on this topic.