The Control Options screen doesn’t save sets of selected device profiles (afaik, unless I missed it). Each device just has a “Current selected preset”, that’s it. Each device also has a list of presets that have been added for that device, including any MSFS ones and the default profile, managed through the preset manager interface. The preset manager interface could use a rework too, you should be able to switch presets within it but you can’t.
You can hot unplug/replug devices, but the deviceId won’t be reassisgned unless you do a restart, so hot plugging isn’t recommended either. Sounds obvious, but someone is always going to do it and expect it to work!
I’d counter this by saying, if it was that simple it would have been done already.
Then there’s the dedicated resources needed to deal with the inevitiable issues.
Q: I haven’t actually checked, is this on the feedback snapshot list at all?
From my direct experience peeling back the layers to see the different ways it could be done it isn’t that simple once you dig into it. There’s lot of different use cases with devices and saving confgurations for recall/reset, not to mention it needs to be performant. Changng the active device in the control options is not instantaneous, there’s some work under the hood going on to do this that also needs to be factored in when you want to bank switch all (or even some) devices at once. Ditto for device presets, though less intensive.
Some people have upwards of 400+ aircraft as well, and there’s also a wide range of planes & potential preset configurations people may want - in addition to generic presets. Obviously you can’t cater to all them, it has to be a general solution, but it also has to be flexible - to a degree.
So, from my perspective, it’s a tricky little problem to solve for at least a good % of use cases.
I know most people don’t care about any of the above technical implementation issues, they just want to “make it so” & use it - which is fair enough - but the reality of implementing functionality is always more complex than it appears on the surface. That applies to MSFS across the board too.
all that is missing is a way to assign a profile to a list of specific airrcraft.
Sounds like an interesting approach though, an inversion of the aircraft first approach.
Could you elaborate a bit more on how you would see it working, from setting control profile setups to aircraft, then all the way through to hitting the fly button so an aircraft has all its selected presets activated? How do you see it working within the context of the current Aircraft Selection and Control options UI? What would it look like, and how would it flow in terms of user actions to get it done?
It might be worth exploring.