![]() Even if your settings ar unset, I would be incluned to set the assited settings on, apply and save the new settings, exit FS2020 normally, then go back in and reset teh assisted settings to off, then apply and save again. The fix that worked for me was:ĭo make sure you check these settings as they were the cause of all my issues. This conflicted with the Thrustmaster Wathog Throttle and Joystick. I had applied a mandatory asobo update and this set the assisted settings to on. I finally tracked my problem down to the assisted settings. As I opened the Warthog throttle physically, the screen showed the throttle moving all over the place and ditto the joystick. I was getting really eratic behavior with the throttle. That sounds like exactly how my problem with the Thrustmaster Throttle started. The good news is the fix is still here for all to see and I’m really pleased that it helped you. ![]() I’m still hoping that Microsoft / Asobo will sort the issue out properly and issue a bug fix but so far that hasn’t happened. I watched 2 upgrades of FS2020 go through and the AI settings remained as they were so, on the basis that I thought this could affect others, I posted the fix on this forum. I went through the AI settings setting them back on one at a time until I found the setting that was causing the issue.Īfter that, I contacted Microsoft again and explained that I had identified the cause and how to overcome it and nothing happened. It took a few hours of resetting default settings until I switched all of the AI settings off and suddenly everything worked as it should. The problem persisted even with the change of hardware and that meant it had to be something with the FS2020 settings. I had tried everything and actually changed the throttle as I thought it was faulty. I had - had the issue with my throttle control for months on end. It’s great to hear that you have benefitted from the fix. Hopefully, this message will assist others who are having the same issues that I have experienced and, for goodness sake Microsoft, set this flag back to off on the next update and document it so that others can make a value judgement on whether or not this option is useful to them or, as in my case, a massive overhead.Ībsolutely no problem. Microsoft / Asobo either can’t or won’t acknowledge this as a serious issue but at least there is now a fully working solution to this awful controller issue. Everything works perfectly once this change is made. Within MSFS, navigate to OPTIONS / ASSISTANCE OPTIONS / PILOTINGĬlick ‘Apply and Save’ or F11 to save your new settingsĪnd that is it. The first signal comes from the physical throttle movement from the Thrustmaster HOTAS Warthog throttle and the second signal (the one that causes the erratic behaviour) comes from the simulator itself as it tries to override the users physical throttle settings. ![]() This forces the flight simulator to take 2 sets of input signals for the throttle. When this option is set (which it is by default since the update back in Mid 2021) the simulator tries to override the users throttle and some joystick movements on take-off. The issue is caused by a setting, deep inside Microsoft Flight Simulator 2020, that provides ‘Take-off Assistance’. Having said that, I suspect that other MSFS users using different throttles, could also experience similar issues. This is a Microsoft / Asobo issue and is not an issue with the Thrustmaster Throttle. Star Citizen on the other hand, is noted as a game that can correctly config devices where others fail.So, after spending four hours trying to get the ‘ghost throttle’ issue sorted out with my Thrustmaster HOTAS Warthog throttle and Microsoft Flight Simulator 2020, I have finally identified the issue and sorted it out. That can be both a boon and a bane and with a HOTAS setup of controllers from different manufacturers, it's why I won't bother with War Thunder at all. ![]() Star Citizen and War Thunder aren't good examples as both have highly proprietary input device code, which is why they can have different results with detecting controllers. So my recommendation is, If you have another USB gaming device try unplugging it. Do you have any other USB devices that could be possibly causing a conflict? As an example, I have a USB Tartarus gaming keypad, which won't prevent any of my other 4 USB devices from being detected in a game, but it does cause both my Thrustmaster T.16000m and Logitech F310 to not display correct button and axis layout under Win10 > Devices > properties. If it has such a switch, try switching it to the other setting. If so, that can sometimes explain why some games will detect it and others won't. I'm not that familiar with the T.Flight HOTAS, does it by chance have an XInput / DirectX switch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |