So - love Flightsim 2020 but really think there are some important items missing. Especially when it comes to the crazy people like me who like to have extended setups at home.
The issue is that there seems to be first of all a lack of support for anything more advanced than the Thrustmaster Flightstick and Quadrant. Now not all devices in the world can be supported, but if I am to use something like the VRinsight Airbus FCU panel - then I need to be able to assign key combinations to the individual keys on the unit.
BUT here is where the issue arises. I can only find one key binding for something like Auto pilot.
There is no AP1 and AP2 setup in the overview in the control section.
This issue is the same for many items - no way to bind a key for each individual take off light.
I cannot find a way to define a key binding for how to change the EFIS between LS/VOR/NAV/ARC/PLAN modes - or the range setting.
So - the way to solve this in my opinion would be (beside starting to support the hardware for home builders) to publish a complete key list so that we are able to define each key individually.
Hope you will do this…
You might want to look into SimConnect. Having only key-binds is not going to cut it.
Also: You can go into the control section and assign any key combination to any available input yourself. Not all available actions have keys assigned by default.
I know I can assign keys but what if the thing I am looking for is not there.
That is what I was trying to describe. There is no AP1 & AP2 only turn on/off Autopilot - and it only does it to AP1. The same with the other examples I gave. Sorry if that was not clear.
So just to stress - I need to know how I can add keys to input that currently only seems to be able to work via mouse input.
Indeed not all variables are bindable by default.
However, you might want to look into Spad.NEXT which is able to capture nearly all events and bind actions to it.
Have you looked at FSUIPC?
Thanks for the suggestions - First SPAD - Not sure what it is and why it would help me.
I don’t have a Saitek unit and no other units are listed under the supported models.
I have tried looking into FSUIPC but so far I cannot get it to work - seems like you have to purchase it before it will work. Also currently it only works with a limited version of Linda and I am a bit uncertain if it is at all possible to save your own keys to a specific plane layout. Believe this is due to the limit in the beta version. So I would have to pay, but not really be able to customize and on top, again as I understand it, I would need to recode the plane interface after each update - Yikes…
So if anyone using VRinsight Airbus FCU can add in then please do.
So far I can get it to “work” by starting Linda, then VRinsight VRisim, then FS2020, get in cockpit, then jump to VRisim and then pressing the start button. I get parts working but loads of items lacking.
So a complete A320 list if items that can be assigned would be a gift from god right now - and I am still referring to all the items that is not in the list currently being displayed inside FS2020
If you’re building hardware yourself look up mobiflight. There is MSFS2020 support with mobiflight. if you’re just using the saitek components then you’ll need spad.next to bind many of the options. It’s not exactly just plug and play, you’ll need to do some research but Spad.next will solve your saitek problems.
Try opening a ticket with Zendesk support.
I’ve had one open with a request for documentation for input setup and their response was “ask the community” but perhaps if enough of us ask then somebody, somewhere might actually provide that documentation…at which point it’s easier to work out what is actually missing and/or is actually there already but buried under some obscure phrasing.
wait… the actual response to a legitimate question / support request regarding input peripherals was go ask the community how to do it?
That’s real concerning if they are relying on the community to provide support for things they’ve built.
Yup. That was the zendesk support for Microsoft flight simulator 2020 official response to a question regarding documentation for input control set up. - specifically what the various binding options for throttle axes do. (There are functional differences.)
In a separate ticket where I asked what the actual success criteria for achievements was (and what might inhibit successful completion of an achievement flight…because surely somebody in support must have written down the conditions somewhere right? Right?) the answer was…
wait for it…
Ask the community.
Seems like an easy job working on the zendesk support desk.
I don’t know why i’m surprised by this. Essentially that’s the level of support we had with FSX after they disbanded support all together for it.
I’m starting to think we’re getting played hardcore here on their true intentions especially at the rate things keep breaking and concern for pumping out more enhancements before bugs are even sorted out (compounding on each other to make things worse each update).
Well the only way to fix it is if enough people vote to have this… Complaining doesn’t work.
Apparently votes does. Only need about 1100 to make it to the top…
Surely there must be that many home builders that is missing this information.
you have to make it votable first. 