Since the last SU MSFS no longer recognises that my throttle is in Beta range when reversing thrust on landing.

I have a Thrustmaster Warthog Throttle with a reverse thrust lift control. Everything I've tried just gets me in a worse muddle. I tried adding a binding for reverse thrust and it just deletes my normal range throttle, then it doesn't work at all.

I know many have much worse problems than this but bit of a shame really. Great if someone here already knows how to correct this - or it's a trip down to the Asobo swear box again for me. :-##

Any ideas anyone?

Thanks in advance.

 

Ray

I'm really struggling with reverse thrust since the last MSFS update.

No matter what I try to do (in MSFS config or FSUIPC) my X52 Pro throttle gets treated as if it were in two halves - and not truly linear. So ... after crossing the 50% threshold, auto reverse disengages - and it generally goes bananas. I have a throttle button mapped the reverser HOLD.

Some of my props/turboprops work OK, but the only airliner that works properly is the FBW A320neo - which has its own calibration routine.

I use FSUIPC7 with it configured for reverse thrust for my Warthog - works perfectly with no issues and last checked last night.

Martin

2 minutes ago, sauviat said:

I use FSUIPC7 with it configured for reverse thrust for my Warthog - works perfectly with no issues and last checked last night.

Interesting ... how do you activate your reverse thrust? Just by sliding back - or with a "hold" button (or toggle)?

51 minutes ago, sauviat said:

I use FSUIPC7 with it configured for reverse thrust for my Warthog - works perfectly with no issues and last checked last night.

Martin

Thanks all

@Martin - please could you tell me exactly how you did this in FSUIPC 7? I have purchased the upgrade now. I also have the Warthog controllers

That would be much appreciated.

 

Ray

 

There's a thread on here where a moderator explained it to me. I'll look for it.

Martin

EDIT:

 

Edited June 3, 20215 yr by sauviat
Additional content

The last update completely messed up all of my saved controller settings so you might have to redo them.  I finally bought FSUIPC and set up my profiles there because this is becoming a recurring issue for me after updates..

Still works fine w/ a rocker switch on my Saitek Yoke & TQ

So, nothing I've done so far as resolved this for me. 

I followed the instructions for setting up FSUIPC (I think) but that made no difference - I want to have this working on all my planes (particularly TBM and Longitude) not profile specific for one plane.  Of course I may have misunderstood the settings. I sort of had the hang of FFSUIPC more or less in P3D but this seems a bit different.

Tried reassigning button '29' to toggle or hold reverse thrust, and both settings just stopped the controller working altogether.

So for now I'm stumped. Can't understand why after working perfectly since last August it's suddenly stopped dead. I have checked the TM drivers and Windows calibration and throttle seems to be working fine. Reverse is button 29 and that lights up when I hold it down.

I'll put a message to MSFS helpdesk (not holding any breaths).

Thanks for your help anyway...

@rayharris108 Just curious, but when you purchased it did you physically invert the "bar"? You have to do this!

Martin

 

Not sure what you mean - on the controller (Warthog)?

To go in to beta range there is a detent where you lift the throttle and pull it backwards. If so yes. It worked first time I bought MSFS without any set up from me until now.

Yes, you are lifting it over the bar - you actually feel it go over the bar. That first time were you getting the reverse thrust? For a single engine you may not have had to do very much - you know when it engages, like in the TBM, you here and feel it.

I wanted it for three and four engine planes in FSX, so everything was just transferred from FSUIPC4 to FSUIPC7.

Martin

First time I did that, yes it worked perfectly. Now it doesn't.

Maybe conflict somewhere. Do you have any other controls? What is happening with the MFSF controls - perhaps a default bind!

Martin