The bindings for Garmin G1000 are provided for the Cessna 172 G1000 variant and the Diamond DA 64. With these bindings it’s possible to map other hardware to the sim without having to make changes only using the mouse. It seems it would be easy to add this set of bindings to other aircraft that are equipped with the G1000, like the Beech Bonanza.
There are aircraft specific bindings for the G1000. Whatever next. These are not needed it would be much simpler to have a generic G1000 binding. The G1000 can be controlled the same for any aircraft. I and many others do exactly that right now using sim connect.
If anything drives me away from Xbox back onto PC, it will be the hit and miss implementation of default keybinds onto commonly used aircraft instrument controls, functions etc. Mapping controls onto the various buttons of my MIAP Pro, yoke and keyboard is one of the favourite parts of this hobby for me.
Some developers are better than others. A2A for example have embraced the fact that not everybody wants to use (or can use) LVars. For example they have introduced bespoke in-game mappings for the 2 buttons of the engine monitor. And in the Comanche, the fairly unique AP roll knob can be mapped (including a very convenient centre key bind). Infinitely more pleasing to use than grabbing for the mouse. Many other buttons, dials, knobs are similarly mappable. Commendable. Love BlackSquare aircraft, own all available modules on Xbox, but if I had a BlackSquare gripe it would be that he does not offer enough equipment control outside of third party apps and LVars.
And the Asobo 172 is great in this regard too. It’s been a while since I’ve used the 172, but in addition to all of the GPS buttons being mappable to keyboard commands, you can map all of the internal light dimmers etc. Although the Garmin GNS zoom controls stopped working pre-SU4 so I stopped using that module.
I absolutely loathe using the mouse for controlling the AP, radios, GPS etc. I can’t think of a bigger “immersion wrecker”. I personally would support all user-interactable controls to be compulsory mappable to keyboard controls without the need for third party SW before being allowed onto the MP.
Building up a functional cockpit like you described is probably beyond the intended scope of an Xbox or PlayStation. By its nature it’s really a PC centric thing because of all the tinkering and configuration required. You want full flexibility then unfortunately that means you need to be on PC.
I don’t want full flexibility and I certainly don’t want a full cockpit. I am content with my yoke, keyboard and fairly basic MIAP Pro button box.
What I’d like is for all modules to be forced to implement basic button maps to AP controls, lights, GPS buttons etc before being allowed onto MP. It’s asking for nothing, today some developers offer this, some don’t. A2A seem to be in tune with my expectations. I have other aircraft which are amazing, but force me to use the mouse to dial in AP target altitude, for example. Forcing people onto PC and third party apps for that is not sensible.
When I said full flexibility I was meaning to be able to control everything for all aircraft. That sounds like exactly what you want. I’m sorry you don’t like the answer but what you are wanting is for every dev to implement at the same level and we can’t even get that for other things. Devs by their nature want to do things in the best way they see fit. So as we have seen with the sim over the years that means multiple different ways to achieve the same thing rather than a standard way.
I’ve tried to make this very point a few times before but the response is normally ‘but forcing standardisation’ doesn’t allow innovation. I don’t agree with that response because you can still innovate around a standard. That’s kind of why it is like it is and if history is to be believed very likely to not change.
OK. You are right, even though I’ve explained twice I do not want “full flexibility”.