Hello from Iceland!

I am currently stuck @ BIKF after pushback on my ThinkPad P70 mobile sim rig, where I use a Turtle Beach Stealth Ultra controller. Had to remap my rudder/NWS to the right stick instead of using the triggers, which I saw was an issue to be addressed in the upcoming update, but I absolutely and positively cannot move the throttles. No matter what I do. I see some input on the engine display when I press the Increase Throttle button, but it instantly snaps back to idle when I release it. Anyone got an idea what the issue is?

Cheers!
Atli Jarl.

UPDATE

Reinstalled and deleted the preferences folder, nothing. Every other addon works with this controller in FS20.
Works perfectly in FS24 besides that pesky rudder problem, but totally workable there.

Very strange.

Atli Jarl.

11 hours ago, AtliJarl said:

UPDATE

Reinstalled and deleted the preferences folder, nothing. Every other addon works with this controller in FS20.
Works perfectly in FS24 besides that pesky rudder problem, but totally workable there.

Very strange.

Atli Jarl.

I think this addon not works for FS2020. They release for FS2020, but not complete works. FS2024 you can use and i saw many videos and all youtubers used FS2024 and it worked very well and nobody used for FS2020. Very strange ... I tried calibration many times and nothing happened. I was a problem only with this A346.

Having this same problem also with WinCtrl throttles in MSFS2020. Have been away for a week or so, so haven't tried since then, but I was going nowhere when trying to get flying with the -600. I suspect a duplicate binding somewhere but am struggling to find it.

To avoid or detect duplicate bindings if suspected, unplug every controls but the throttle, reate an empty profile for it and only assign the required axes to thir function.
Have a look to the attached tutorials for the TCA and the Bravo as configuration guidelines.

Bravo-A340.pdf TCA-A340.pdf

UPDATE.

Fired it up on my main rig before and after update, I have the Airbus TCA stick + quad throttles + speedbrake / flaps addon. Disconnected everything else but the throttles don't budge. Speedbrakes, flaps, engine starters, rudder trim, auto brakes and parking brake works like it should. I see in the EFB page for calibration that the values for each axis are registered but the throttles absolutely and positively do not move. Not with the mouse, not with F2/F3. Nothing. Same joystick profile works on any other airplane. There is some weird logic behind this.

Cheers!
Atli Jarl.

If you unplug all the controls, will the throttle move with the mouse ?
--> The goal is to rule out any hardware issue.

On 3/29/2026 at 1:16 PM, SimWare said:

If you unplug all the controls, will the throttle move with the mouse ?
--> The goal is to rule out any hardware issue.

Nope ... still stuck when using the mouse...

... should add that moving the HW throttles (Winctrl in my case) causes the readings in the EFB throttle settings page to change in a logical fashion. If the engines are on, the commanded thrust green circles move on the engine instruments, but as soon as the the HW throttle stops moving they jump back to idle. The throttle levers in the sim don´t move at all.

Ok, so bottom line is that it isn't hardware related as even with no control (throttle, stick, rudder, yoke, etc.) the levers in the plane won't move, right ?

40 minutes ago, SimWare said:

Ok, so bottom line is that it isn't hardware related as even with no control (throttle, stick, rudder, yoke, etc.) the levers in the plane won't move, right ?

Yes correct … the little clenched hand appears but moving it doesn’t move the throttles in the cockpit. Not even a small amount … they seem completely locked at idle.

Should also have mentioned in my earlier post that as well as seeing the engine instruments move when using the hw throttle, there’s lots of clicking which sounds like the throttles clicking into quadrants. With the brakes off, the plane will even start to move slightly as a small amount of thrust kicks in before the throttles drop back to idle.

I know this feels likes some type of hardware issue, but I don’t think it is in this case … could it be a Mobiflight/FSUIPC type issue or something else that auto starts (or maybe should but doesn’t) with either windows (like the FBW background program) or with the sim itself (I have pop out manager and FSLabs CC)?

Also just to confirm, we are talking MSFS2020 here … I will try in 2024 (which I haven’t migrated to, but is installed) to see if that makes a difference.

• Just to confirm, did you activate the plane ?

• If you have FSUIPC installed, please uninstall it temporary (or move its entire folder somewhare else.

  It sometimes happens that FSUIPC, even if not actively interfaced with controls causes strange behavior
  in the simulator.

• Please check that the Assistance settings are set to TRUE TO LIFE
  https://forum.aerosoft.com/index.php?/topic/174442-assistance-parameter-in-msfs%C2%A0-often-the-culprit-in-unwantedstrange-aircraft-behaviors/

Thank you - I will check these this evening and report back.

• Just to confirm, did you activate the plane ?

Yes, but I was one of the people who got a replacement serial number due to the server issues you had on the launch day so it got activated twice. I did do a reinstall recently before reviving this thread and it didn’t ask for a new activation… happy to try deactivating and reactivating if you show you me how and think that may be helpful.

• If you have FSUIPC installed, please uninstall it temporary (or move its entire folder somewhare else.

  It sometimes happens that FSUIPC, even if not actively interfaced with controls causes strange behavior
  in the simulator.

This didn’t help … I did restart the pc after uninstalling

• Please check that the Assistance settings are set to TRUE TO LIFE

They weren’t - they were set “harder” - I have set to true to life following your instructions, sadly this didn’t work either.

Many thanks for helping sort this!

Just to add … I installed in FS2024 and the throttles work fine … so it seems to be something deep inside FS2020 …

Did you already attempted a reinstall of the aircraft ?

43 minutes ago, SimWare said:

Did you already attempted a reinstall of the aircraft ?

As noted in my earlier post: "Yes, but I was one of the people who got a replacement serial number due to the server issues you had on the launch day so it got activated twice. I did do a reinstall recently before reviving this thread and it didn’t ask for a new activation… happy to try deactivating and reactivating if you show you me how and think that may be helpful."

I did do one additional reinstall after removing FSUIPC as well.

Hi,

This is an odd issue that we've now seen occur a few times. For the users this occurring for, it only seems to affect MSFS 2020, and doesn't appear to be flight sim hardware specific. Because of how few users have the issue, it's proving for me to be quite hard to reproduce, but my working theory is this is caused by an underlying setting or conflict (such as another addon) within the sim.

20 hours ago, Paul Hand said:

I did do a reinstall recently before reviving this thread and it didn’t ask for a new activation

Reinstalling the aircraft via Aerosoft One will not clear the WASM work folder, which is where your activation and other addon related information is stored. Could you please give the steps here a try and then see if this yields any improvement?

If clearing the work folder doesn't work, could you try temporarily moving all other addons out of your community folder, leaving just the A340, and then seeing if this causes the throttle to start working?

Thanks Tom ... recompiling the WASM folder didn't help, unfortunately.

I can't seem to empty my community folder (getting what seems to be a famous "Your Organization Doesn’t Let You Place Files Here" error).

MY community folder is a mess anyway, so I might delete the whole thing and slowly build it back up ... but that' a project for the weekend. Thanks for your continued support. I will advise when I have had the opportunity to test further.

@Tom @SimWare deleting EVERYTHING except the -600 from my community folder did solve the problem, so there must have been a rogue interaction somewhere.

Now to add things back!

Thanks for your help with this.

Cheers

20 hours ago, Paul Hand said:

@Tom @SimWare deleting EVERYTHING except the -600 from my community folder did solve the problem, so there must have been a rogue interaction somewhere.

Now to add things back!

Great! I'm glad to hear you got it figured out.

It definitely seems like there's some kind of conflict going on, but with very few users having the issue It's hard to pinpoint the exact addon. Hopefully this is something we can figure out further down the line so we can more easily let people know of the conflict.

4 hours ago, Tom said:

Great! I'm glad to hear you got it figured out.

It definitely seems like there's some kind of conflict going on, but with very few users having the issue It's hard to pinpoint the exact addon. Hopefully this is something we can figure out further down the line so we can more easily let people know of the conflict.

Thanks Tom ... I'll let you know what, if anything, breaks it again!

Do you also have the A330 installed ?

3 hours ago, SimWare said:

Do you also have the A330 installed ?

No, I don’t own it. There were some old Axis and Ohs things hanging around in my community folder that I suspect may have been the culprit … I don’t seem to need them for my current usage, so haven’t tried adding them back.

On 4/20/2026 at 4:21 PM, Paul Hand said:

No, I don’t own it. There were some old Axis and Ohs things hanging around in my community folder that I suspect may have been the culprit … I don’t seem to need them for my current usage, so haven’t tried adding them back.

Just updated the A340 to the latest release, no change. Throttles still stuck, but you have pointed out a possible solution, so now I'm going to remove some things from the community folder one by one to see which one is causing this. I also have tried removing all FSUIPC / SayIntentions things, resetting the A340, reinstalling on every update, but so far, no good. Works perfectly in FS24.

I am removing the Lorby files now, but I do use Lorby as I have a Stream Deck and A&O is required to run the script for the A340 profile, which works just fine in FS24.

I just can't imagine what in my community folder could be interfering with my controls configuration, as every other plane works.

Cheers,

Atli Jarl.

Aha!! I have found the culprit! Removed these three folders and my quad throttles are working perfectly after calibrating them through the EFB.

Alas, I need AAO for my Stream Deck, so I am going to do some research on this.

*EDIT - Narrowed it down to the aao interactions folder, an addon for AAO (It will create LVars for all buttons and levers that use the default Asobo logic.) AAO scripts working perfectly with the A340-600 now. 🥳

You can mark this one as solved!

PS. These folders are present in FS24 and do not affect the controls there.

All the best from Iceland!

Atli Jarl.