For the 172 they are specific controls, so they’d need to be custom made for every aircraft. Honestly, the G1000 (and other base avionics imo) should be bindable by default under the Aircraft category and not only for the specific aircraft controls category.
So I’m not sure this is really a “bug” and more of a wishlist item as it seems like it was intentionally not implemented here.
But it is the same Garmin G1000, One set of binds should work for every plane that carries it. It isn’t the plane we’re binding, it’s the Garmin. Why couldn’t the modeling be applied to every plane that has a G1000?
This is why so many pc users use external apps for their control. The in sim bindings are but a fraction of those used. When you get to 3rd party custom aircraft the issue gets even worse. It’s not worth fighting it if on a PC. Just get an external apps and be able to control everything. For information yes the same controls used in one aircraft are the same ones used in another. If you are saying the C172 specific bindings do not also work in the C400 then Asobo are obviously doing something peculiar for that.
They’re using a new 2024-specific feature called “specific controls” which allows a developer to create totally unique controls for their aircraft which are bindable in the sim. Basically, the thing you’ve pointed out that complex 3rd party aircraft have, except this is a tool MS has given developers to do that natively in the sim instead.
I simply don’t understand why anyone would consider doing that for a standard bit of kit such as the GNS, G1000 etc. There are already well established events for the control of these developed by WT. This is just adding a completely unnecessary additional layer. Microsobo just don’t seem to get control bindings. They have continually made a mess of it which is why I suggested giving it up as a bad job and using the more complete and capable external apps available.
The Cessna C400 Corvalis is a default plane, it is not about bindings not working, for the C400 the bindings don’t exist. It is not the only plane with no Garmin bindings. Seems like laziness to me.
Check the images in the opening post. Searching MFD for the C400 gets no results compared to the full page for the 172.
I did find controls in the center console, which I can’t bind to a dial on my HOTAS because there are no MFD binds. IRL it would be a simple move to reach over feel the knob and zoom the MFD. In the game, I must look down, my hand must leave the stick, grab the mouse and grab the dial with the cursor. Actually, I have to click the PFD/MFD selector buttons on the left first.
What irratates me is that they already had all this modeled for the G1000, they just got . . . bored?
I understand all that. What I’m saying is there shouldn’t be specific bindings for each and every aircraft using the g1000. What happens when an add-on aircraft uses the G1000. There will be no bindings. All that’s needed is a single set of bindings that can be used in any aircraft using the g1000. That’s how it is when using an external app outside of the crazy world of default bindings. For instance I can control the G1000 in the c400 just fine. Do yourself a favour and just use an external app if you can, it’s so much easier and less hassle.
I’m not a developer so I can’t give a more technical explanation, but I think the way the buttons are mapped is actually set by the aircraft developer, not something stock to the avionics. We’ve had several examples where the same buttons either don’t work on one plane and do on another, or their function is inverted on one, and not another.
That may be why these controls are technically considered “specific” because it comes down to how it’s implemented in the aircraft - which is not universal by design.
For the WT stuff I use exactly the same control scheme for every aircraft using the same avionics. Nothing different, nothing inverted just exactly the same in all instances.
For other things such as cockpit switches and the like that may be the case but that’s because they are more aircraft specific. The controls on a G1000 or a GNS for example operate the same in whatever aircraft they are fitted.
There were, until recent updates, aircraft where the zoom in/out buttons on GNS530s were inverted compared to others - and those are WT avionics. Same with some aircraft where the VS/FLC Nose Up/Down buttons were inverted on some, but not all, implementations of the G1000. There is some element of aircraft configuration that has an impact.
I think you are referring to the virtual cockpit controls. If the dev assigns the wrong event to the cockpit click spot then yes. But if you are sending that command from an external source and use the same command on every aircraft the GNS display will respond the same. We are talking control from outside the virtual cockpit here don’t forget.
Yeah, in terms of direct manipulation of variables/events, that’s right. For the record, I fully agree these should be standardized and mappable in controls settings and not per aircraft.
I’m sorry to have to say it again but yes they do. Forget what’s happening with the virtual cockpit or what’s in the in sim bindings lists. You can control every G1000 with the same set of controls on every aircraft. Myself and many others do this whenever we use those avionics.
As far as an app that will depend on how you intend on providing that external control. Personally I use Air Manager and touch screens to display and control a cockpit outside of the sim but if the intention is to use existing game controller hardware perhaps something like Axis & Ohs or SPAD would be more appropriate. Building your own button box then perhaps Mobiflight.
Didn’t have a G1000 setup photo to hand but you get the idea.
Nice setup. I just want to bind controls to my HOTAS . . . are you being specific about cockpit builds, or if I get in a 172, use its controls/MFD binding page and bind to my HOTAS, the binds will work in the C400? Or do I need button boxes and additional apps?
You’ll notice I mentioned existing hardware. By this I include joysticks, yokes, throttles or any other game controller hardware that is a standard plug n play hid device.
The first thing to try as it sounds like you haven’t done so already is use the C172 G1000 bindings to try and control the c400. If that works then you are done.
Failing that then you will need one of the external apps such as the ones I mentioned. Note that there are others as well. A search on apps that use sim connect to control MSFS should reveal more.
