Any idea why this happens? (Throttles advance but a320 thinks they should reverse) It won’t provide any thrust, because it just goes into reverse thrust.
Worked ok before, and works ok on a Cessna 152. Not sure if its a bug in FS, FBW32nx or Saitek. Or me? Can’t figure it out.
Detail steps to reproduce the issue encountered:
If you go to full thrust, will the plane move forward?
No. It remains in Reverse Thrust until i pull the throttles back to idle
Did you try selecting “reverse axis” on the controls to see if that would cure the issue?
Thanks for taking the time to reply. Yes I did try that, but it didn’t work. It was just the same but in reverse, i.e. at the normal physical position of idle, the reversers would be on full, and when I moved them physically forward, (as if full throttle) then engines went to idle.
If this is an issue that has been there since the start and affect most planes, you may want to check if there is a firmware update for your HOTAS, i got the new X52 (black one, Logitech) and i have no such problems.
I’ve been struggling with this also but… found a work around that works ( for me that is)
I have mapped joystickbutton 16 ( low right on the throttle) to toggle thurstreverser on and of.
Feels a bit counter intuïtief but after a while I got used to it.
That might be an issue because the X-52 pro of ErroneousPanic7 and myself is of the good old Saitek brand and it might look the same as the newer Logitec version but the firmware isn’t.
Fun thing and maybe related: I took the Longitude and decided to visit Paro (Bhutan) to land on that mountainous runway, i took of heading northwest, swinging around and touching down. When wheels were on the ground i pressed the thumb button (which i have assigned to toggle reverse thrust), it didn’t work. Reverse thrust just looked like it it was stuck and didn’t budge, as if rusted in place and you were trying to dislodge it.
I then went back to Arlanda (Sweden) and tried enabling reverse thrust, no problem there. Maybe this is location dependent somehow, i.e. at a certain height, or a certain XYZ position that screws up flight controls in some way.
What aircraft were you flying?
That’s strange. I can’t see the logic in the scenery affecting the throttles. I’ve just completed a flight from EGLL to EGCC yesterday and no problems. EGLL is the default one in FS2020 and EGCC is a new one from Maaco Simulations. I’ve had the issue a number of times before but I don’t remember which airports. The latest issue was at Gatwick (EGKK Ultra). Going to try it again but I’ll watch out for things to see if there are any other anomalies. I can only remember it affecting the A320neo. And it doesn’t happen all the time as I have just proved.
There were issues with the throttle not working at all in a number of aircraft in FS2020 - but i traced this down to the fact that I had been using FSX beforehand and had ‘invoked’ the X52 HOTAS profile program to make the X52 work with the Aerosoft Airbus in FSX. I had fogotten to ‘switch it off’ or ‘Clear’ the profile when I finished with FSX. When I started FS2020 afterwards - it obviously had a conflict. When I ‘cleared’ the Profile or ‘switched’ the profile off - the throttles, Joystick and buttons etc that I had setup in FS2020 then started working as I had programmed them to do - with the 320neo and the 152, CJ4, Icon A5, etc. So it maybe retlated - I’ll have to keep a close eye on exactly what I do.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
