So I tried to assign two throttles, one for normal flight, and one collective for helicopters. But they seem to interfere with each other.. I cannot have both assigned to “throttle” without them interfering with each other.. This should in theory not be an issue, as long as I am not touching the other throttle.. Doing this all the time in Xplane and DCS, but MSFS can’t handle it…
Is there any other way to have several throttles assigned at once, without having to unassign them all the time depending on the aircraft I am flying??
If you use the sim‘s assignment menu you need to create controller profiles for every different setup and switch them everytime you want to use either of them.
In opposite to P3D or XP where commands only are sent once the moment you activate them (like flipping a multi position switch, moving an axis) this sim actively reads these positions and forces them to true/on/moving all the time.
I personally have deleted all bindings in the sim and use Axis and Ohs, a wonderful and externally running app that lets me do what I want with different profiles for different planes that get automatically selected once set up. Similar to FSUIPC/XPUIPC.
1 Like
Thanks for your reply, and for explaining me how the sim itself read my controllers. This would explain this behaviour! About that Axis and Ohs, this is only for axis, right? So in essence I keep my button assigned in the sim, but let the external app control the axis? Does it bypass MSFS controllers entirely?
I use Axis and Ohs and have a bit of a mixture. A&Os does axies and buttons and scripting and a lot more besides. It is very powerful, but I find easier to do simple things with than the similar FSUIPC. FSUIPC also has (had?) issues with the CRJ, which was one reason I changed.
I retain the in sim default button mappings for the camera - simply because that was easy to do - but have removed all other “in sim” button and axes mappings and use A&Os for them. It works very well.
There is a great thread here where you can ask any questions of the community:
There is also a great web resource here for scripts and button mappings for many of the available more complex aircraft:
3 Likes
Thank you so much! I will definately try this software!
But an immediate question comes to mind. I don’t want to manually assign all axis to all aircraft. Can I easily copy/paste one scheme over to other aircraft aswell? Say I make one for the Cessna, can I copy it over to all other aircraft, and then change them individually afterwards?
AAO also has a demo version (closes after 20 minutes) and a freely available manual which should be read. I love this tool.
You should assign them to Throttle 1, Throttle 2 etc. not “Throttle”. “Throttle” moves all throttles and is useful if you have just one and fly a multiengine airplane.
3 Likes
The more I read about how Asobo have approached input controls in FS2020 the more confused I get.
Or rather… “What the hell were they thinking?”
2 Likes
This will not solve the problem though. Helicopters and GA use the same Throttle, so it will interrfere no matter what I map
I might have misunderstood. Just create a profile and switch it depending on what you fly. That’s what they are for.
1 Like
And to make matters worse, to keep the Xbox folk happy they ditched the light indication in the controls panel, when you bind a button to a key, that keypress would light up so you know it is done correctly, now we have nothing!
And to pile on more $hi& in this area, I cannot tell if a button is on or off anymore unless you set it up in Nintendo mode!
I don’t quite understand the gripe, the sim’s control panel lets us create as many profiles as we want and assign every button and lever available how we prefer. I have Bravo Throttle Quadrant and Thrustmaster Airbus set, I just use the sim’s profiles to differentiate. In my view it is only logical not to have same assignments to different controllers used simultaneously. Why would that be a user case that is necessary to be implemented, let alone make someone think “they don’t know what they are doing”?
@TidalPopcorn618 Asobo’s controller scheme is horrible. If you’ve ever tried X-Plane 11, that’s how it’s supposed to be. Controllers made for each aircraft without the need of axisandohs software and the likes.
I don’t have any need for Axis and Ohs. The sim’s controller scheme works just fine for me. Would you care to elaborate what exactly you cannot do what you want with it? Assigning two different control throttles for one in-game throttle makes little sense to me.
@TidalPopcorn618 We all have different setups, not everyone has it the way you have it, and some of us don’t even have monitors and relies on VR. Bringing up flightplans and loading controller schemes from within VR messes up the VR runtime and it makes me have to take of my HMD, walk out of my simulator, go to my PC monitor, select the controller scheme, walk on back to my simulator and crawl my way in and put my HMD back on again..
In X-Plane 11 it chose my controllers automatically based on what aircraft I loaded. It had the controllers stored individually FOR the aircraft. So I didn’t have to manually choose a controller scheme seperately from selecting an aircraft.
Yes, I agree, that would be a nice to have feature, and I am sure could be added at one point. But again, this is just something that can be overcome by thinking ahead before flying and making sure the controller set is the one required. It can be seen as a nuisance, but hardly warrants trashing the whole scheme.
I also fly VR btw, even more lately as I have re-calibrated and found a sweet spot to really enjoy, and can access the controller setup within VR, no issues. Except for the fact that every time when I resume simming, the flaps have mysteriously been set to full. Does not happen only in VR though.
The more I think about that feature, more I think you have raised a valid point and should open it in the Wishlist section, so we can all vote on it. I will for sure give my vote for it. It would be a great improvement to be able to map the controller settings to specific aircraft.
@TidalPopcorn618 Yeah but I don’t think Asobo will even notice it, they have a workload so far up their neck I think it’s just a waste trying to get their attention. We can only hope for it 
They were normal game developers without any clue about a flightsim and aviation when they created the UI, not to mention the sim physics. They are great at visuals etc. In a normal videogame you need to keep controls sticky as long as you hold W S A D down. This sim‘s controls have been exactly what I would expect in a typical game. A flightsim however requires the controls to give an impulse and release immediately after. A two position switch needs to be able to get overridden with a mouse click on that cockpit switch and mustn‘t be forced to a position just because the hardware says so. Different controllers for different types of aircraft must not disturb eachother while you normally only use one controller for a game. They‘ll have to learn and accept the difference but I guess it will be a long way for us to teach them.
1 Like
And one of the biggest annoyances (and departures from the usual “common sense” configurations is that you can only see what is mapped to the controller you are mapping at the time.
Want to bind Landing Gear to a button on a throttle?
Sure, you can do that. But you cannot simultaneously see if that function is also mapped to a second throttle, your keyboard or a vJoy device because rather than present a global list of functions that can be mapped (and what may or may not already be bound to those functions) FS2020 compartmentalizes every separate device that’s connected.
It’s a really clunky way of managing the functions and input devices.
The workflow should be
- Find function to be mapped (landing gear)
- Map to any of your devices as you chose. - because any device can be mapped at any time.
(and be able to see any other devices mapped to that function at the same time)
The workflow IS
- Select device you wish to bind.
- Find function to be mapped.
- Select each other device in turn to see if that same function is mapped to those also.