T16000m FCS Hotas TWCS Throttle Erratic performance

I have just bought the T16000m FCS setup as the reviews for the X56 are very poor.

Yesterday i installed and set up the configuration for the joystick and the throttle. The hardware was recognised by Windows and checked the calibration etc. In FS2020 i bound the keys i wanted and adjusted sensitivity as required etc. On checking the slider response for the throttle, the white line moved as expected and was not jumping around or flickering (no apparent dead spots etc). I unbound the throttle on the flight stick.

When it came to my first flights in any of the planes, the throttle would be jumping around (erratic) from 0 to full and everywhere in between.

I unbound the throttle on the TWCS and bound it to the slider on the flight stick. This worked perfectly as one would expect.

Can someone please tell me where i am going wrong. or is the TWCS faulty…?

I did read one review from a year ago on VATSIM that the TWCS did have an issue with FS2020…but no one on here seems to have discussed this…??? so i guess not an issue.

I am running an Alienware PC that the hardware is connected to.

I have previously been using FS2020 for just over a year with my old AV8-R playstation joystick…which has now died a death…potentiometer issues! 20 years out of it…not bad.

Thank you for any assistance.

Julian

make sure you bind the correct throttle axis (I believe it’s the -100% to 100% one).

The TWCS worked right out of the box with the standard profile for me.

The strange thing is that the white line in the control settings shows a full range of movement and holds the throttle setting full, medium or low and everywhere in between. Its only in game play that the throttle jumps around…i cant get my head around it…i have also ensured there are no other keys bound to throttle to ensure there is no conflict.

If you both have the joystick and the throttle, the throttle on the joystick is fighting the separate throttle. Unbound the joystick throttle.

Also, by default the left wheel of the throttle is bound to trim. You do want to unbind that also.

I had unbound the slider on the flight stick to prevent any conflict. It was made redundant. The wheel on the throttle was set for my trim and so should not have been an issue. The trim worked perfectly.

turns out the mouse had a preset throttle axis i did not know about…this interfered with the controls…apologies for wasting anyones time!!!

Hi Julian

I think I can solve this issue for you. I have had the same problem with my Thrustmaster HOTAS Warthog throttle. The good news is that this is a very easy fix to apply once you know what is causing it. I have just posted a note on the forum for other users but will paste in my fix for you here and, fingers crossed, this does the trick and solves you issue.

All the best

Ed

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.

This is a Microsoft / Asobo issue and is not an issue with the Thrustmaster Throttle. Having said that, I suspect that other MSFS users using different throttles, could also experience similar issues.

The issue is caused by a setting, deep inside Microsoft Flight Simulator 2020, that provides ‘Take-off Assistance’. 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. This forces the flight simulator to take 2 sets of input signals for the throttle.

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.

The fix is really easy.

Within MSFS, navigate to OPTIONS / ASSISTANCE OPTIONS / PILOTING

Turn off ‘Assisted Takeoff’

Click ‘Apply and Save’ or F11 to save your new settings

And that is it. Everything works perfectly once this change is made.

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.

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.

Ed

2 Likes