I get what you mean about radio panels. My understanding is that the older Saitek ones can be a little tricky to get working.
But everything else is just a collection of axes, buttons/switches and encoders most (if not all) of which is surely supported by the standard windows API’s?
Any complex trickery would be better handled by manufacturer created software and all Asobo need to do is provide the ability to then map those inputs to functions in the sim.
Whether a hardware trim wheel is an axis or a rotary encoder doesn’t really matter as if you have the ability to map either an axis or a switch input
I just can’t understand what they need to test here and what they are doing/keep doing that would break it.
This can’t simply be about Asobo creating pre-defined “default profiles” because surely those would be easy enough NOT to break with each update?
And there isn’t any support for force feedback or VR controllers that I know of.
Are Asobo making this harder than it needs to be for themselves?
As do my Virpil joystick, rudder pedals and throttles. - because they are simply windows compatible games controllers at the end of the day. All this “supported hardware” thing is utter utter nonsense.