I find it really frustrating to have to manually change the profile every time I switch aircraft.
Why can’t we save a specific profile for each plane—for example, the Inibuilds A350-900—so that the correct profile loads automatically when spawning in that aircraft?
Currently, you can only set a single default profile, which applies to all planes. That’s not very practical.
And in the SU3 beta, you can’t even set a default profile anymore, which used to work for me—at least partially.
Please improve this system. It would make things much more user-friendly!
You should be able to use the “Create” option to create a set of controls for a specific aircraft - Just call it something like “Controls for Aircraft X” and only use it for that aircraft.
For the default I think you would use “Apply to all airplanes”. You would then go in and use the “Create” option to create a set of controls for a specific aircraft if you did not want it to use the “default”
I must admit I find the controls interface somewhat confusing, so my comments above may be totally incorrect.
My controls have to be reselected almost every time when I change planes. This is even though I have saved to all airplanes. I recycle through presets even though it has the correct one and then eventually return to the original preset again and it usually sticks.
In SU1 and SU2 beta this was actually working (albeit very weirdly). The configs in the ‘Airplanes controls’ category can be bound to an aircraft by ‘set as default’. If I have an ‘inibuilds’ preset, I can set default to the ‘A350’.
However THIS is now broken in SU2. I can only apply items that are under the ‘specific’ settings to an aircraft. Yet there are no specific controls in the A350. And I can’t bind a specific action curve to the elevator for example to an aircraft since that’s under the ‘Airplanes’ category.
Basically this is a very bad modelling of general user needs.
If a binding is under the ‘specific’ category and is specific to an aircraft, there’s no point applying an config preset that only works for one aircraft to other aircraft since they don’t even have that setting to bind.
If a binding is under the ‘airplanes’ category and is general to all ‘airplanes’ category aircraft, there’s actually need to bind specific action curves or keys to each aircraft (either PMDG, iniBuilds, Fenix). Yet we’ve lost this ability.
