h4rp00n33r, thank you so much for this workaround! I will try it very soon when I am back. Do you know if calibration works with this workaround? At the moment MFS ignores any calibration done through Windows Control Panel, like in the screenshots above. The calibration is recognised in other games, but I drift right in MFS, needing too big of a deadzone. Maybe there’s a way for this in vJoy or UCR?
Yes, UCR has to be open while playing MSFS. But you can minimize it.
No, unfortunately the issue regarding the calibration and the giant dead zones (mine are at 15% with the sticks) can not be solved with UCR. Maybe ReWASD (www.rewasd.com) can help here. I have not tried yet…
With Lorby’s AxisAndOhs (Products - Lorby-SI) it’s possible to use an external calibration, because it replaces the complete controller logic in MSFS. I think I’m going to try it this evening. 
The screenshot looks promising:
@h4rp00n33r UPDATE: SUCCESS! Rudder AND Calibration!
I had the same problems as @WeamDreaver; controller not showing up in game, and axis being corrupted. It turns out, if you install vJoy, or make changes to “Configure vJoy” app, this bugs out the Xbox controller driver. The solution is to uninstall the xbox controller through Device manager (leave vJoy alone), and replug your controller 2-3 times till it shows up again in Devices and Printers.
Anytime you make any changes through vJoy, it will be necessary to reinstall the Xbox controller driver. Only after all this, proceed with UCR.
As for the calibration issue, I unmapped/cleared the aileron and elevator in MFS for the Xbox controller, and instead added another two axis through UCR for aileron and elevator. I then also calibrated the vJoy controller through Control Panel, and to my surprise MFS registered the calibration! No more drift that needs 15%, I can get away with 6% now! It turns out MFS ignores any calibration specific to the Xbox controller, but accepts them for other devices?
Remember, when trying to map the axis for vJoy in MFS, it won’t let you choose the axis when auto detecting the axis. It warns you that you can’t use an axis from another controller. Just don’t use the auto detection, and choose your axis from the drop down list for vJoy in MFS. It will be easier if you remove a bunch of unused vJoy axis from it’s own software, but remember you will bug out the Xbox controller drivers again, so reinstall them again through Device Manager.
@h4rp00n33r I can’t thank you enough for this, I’ve discovered something new with vJoy and UCR that I can apply to my other games too now! As for Lorby’s AxisAndOhs, this is another big wow! I haven’t tried it yet, but currently you can’t calibrate the right thumbstick through Control Panel, only left. The way I do it now is, I display the raw data during calibration through CP. I look at the minimum and maximum X and Y values, then find the middle value I need to recenter to. Then you have to simultaneously rest both the X and Y axis to the values you need to act as the center before pressing “next”, which is ridiculously hard as the ranges are from 0-64,000 for the Xbox controller. The slightest movement can throw you off by 500. So this Lorby’s software might come in handy for this, and also to calibrate the right thumbstick.
Thanks again!
1 Like
that;s why i can never get a smooth take of or a landing.Due to non analog rudder control.it’s like the jet(mostly) is drifting
Same issue here with Logitech Wireless Gamepad F710. Worked fine until some time ago, since then hardly usable for yaw axis. Please fix!
This is still an issue. Xbox accessories app shows that the triggers do indeed work like an axis but MS2020 doesn’t identify them as one. This is a must fix for the game to be usable with Xbox which appears to be right around the corner
Works great! Thankyou for this.
still not fixed, where can I vote for this to get fixed?