Thrustmaster T.Flight Hotas One MSF Edition (White) not working with MSFS 2024

T.Flight HOTAS One (MSFS Edition/White) in MSFS 2024 – things to check

BudE86 — yeah, you’re not the only one running into this. The “white” MSFS-branded HOTAS One can behave differently than the older T.Flight variants depending on how it’s being detected (and whether MSFS 2024 is actually loading a usable control profile for it).

Here’s the order I’d tackle it.

1) Confirm Windows is seeing it correctly (before MSFS)
Before touching anything in-sim, make sure the device is clean in Windows.

1. Unplug the HOTAS.
2. Reboot the PC (sounds basic, but it clears a surprising number of stuck HID/device states).
3. Plug the HOTAS directly into a rear motherboard USB port (avoid hubs/front panel for now).
4. In Windows, open “Game Controllers” and confirm you see it as a joystick/controller and that axes/buttons respond during the test.

If Windows doesn’t show proper axis movement here, MSFS won’t be able to either.

2) Remove “duplicate controller” confusion
MSFS can get weird if multiple similar devices are present (or if an old device is half-working and stealing assignments).

1. Disconnect the “very, very old” Thrustmaster stick while you troubleshoot the white HOTAS.
2. Also disconnect any other gamepads/controllers temporarily (Xbox controller, etc.).
3. Start MSFS 2024 with ONLY keyboard/mouse + the HOTAS connected.

3) In MSFS 2024, verify it’s detected and not stuck on an empty profile
Once in MSFS:

1. Go to the Controls/Options area and look for the HOTAS device in the device list.
2. If it shows up, check what “profile” it loaded. Sometimes it loads a blank/partial template or a broken default.
3. Try creating a brand-new custom profile for that device (don’t edit the default; clone it or start fresh).

Then assign just the basics first (to confirm the sim can “see” inputs):

• Pitch axis
• Roll axis
• Yaw axis (or rudder)
• Throttle axis
• Brake (optional)

If those work, you can fill in the rest.

4) Watch for axis conflicts (especially throttle)
A very common issue is the sim “sees” the axis but it’s fighting another assignment (or reversed / set as a button).

1. When you bind an axis, use the “search by input” feature (move the throttle/stick and see what MSFS detects).
2. Make sure throttle is assigned as an AXIS (not “Increase/Decrease Throttle” button commands).
3. Clear any duplicate bindings on other devices (even keyboard bindings can sometimes cause confusion, but usually it’s another controller).

5) Don’t assume the MSFS Edition profile exists in 2024
MSFS 2020 had a lot of baked-in controller templates over time. MSFS 2024’s templates/support have been a moving target for some hardware, so the fact that it’s “MSFS Edition” doesn’t guarantee it has a working 2024 mapping out of the box. In those cases, manual binding is the workaround (once the sim is actually reading the inputs).

About “Is there a Flight Simulator game where this newer stick works?”
If Windows recognizes it properly as a standard game controller, it should work in sims in general (the limitation is usually default profiles, not basic compatibility). The fact your ancient stick “sort of” works makes me suspect your issue is either:

• the white HOTAS not being detected properly at the Windows level, or
• MSFS 2024 loading a dead/empty profile for it, or
• device conflict/duplicate bindings.

A few targeted questions so we don’t guess

1. Are you on PC, Xbox, or both? (HOTAS behavior/support differs a lot depending on platform.)
2. Does the HOTAS show proper axis/button movement in Windows “Game Controllers” testing?
3. In MSFS 2024 Controls, does the device appear by name, and does “search by input” detect anything when you move the stick/throttle?
4. Any other controllers connected when you tested (including the old Thrustmaster, Xbox pad, yoke/pedals, etc.)?

Answer those and I can narrow it down fast (and if it’s a profile problem, I’ll tell you exactly what to bind first to get you flying).