Thrustmaster T.Flight not being recognized by PC?

I just reinstalled Elite Dangerous (trying to resolve an issue since the update) and for some reason my Thrustmaster T.Flight 4 isn't being recognized by the game anymore. It's not showing up in the Controller options (just Keyboard only, Empty, Keyboard and Mouse, Generic Joystick). Dunno what "empty" is supposed to be. But before the reinstall there was a thrustmaster profile as well. And I had a custom one too (which I copied and saved to put back in after the reinstall).

I tried to reinstall the Thrustmaster drivers too, but no change.

Any ideas?
 
Last edited:
I just reinstalled Elite Dangerous (trying to resolve an issue since the update) and for some reason my Thrustmaster T.Flight 4 isn't being recognized by the game anymore. It's not showing up in the Controller options (just Keyboard only, Empty, Keyboard and Mouse, Generic Joystick). Dunno what "empty" is supposed to be. But before the reinstall there was a thrustmaster profile as well. And I had a custom one too (which I copied and saved to put back in after the reinstall).

I tried to reinstall the Thrustmaster drivers too, but no change.

Any ideas?

Works fine by me. Doublecheck the ps/pc switch?
 
I am having this problem too. I had to remap everything. And some buttons still weren't recognised (the game saw the "seesaw switch" as the same as the twist yaw...

It all worked fine in beta...
 
Having a similar problem with a Thrustmaster Warthog Joystick I just bought since 3.0.

Not being recognised.

It works fine and I can programme axis from it but it's just a generic stick and no presets.
 
Last edited:
Definitely not the problem. The computer recognizes it just fine. ED does not.

PC recognizes, but E: D does not? Hm. We have the exact same HOTAS, and I've never had any issues with keybindings or disconnects. Very odd. And you've tried standard re-connecting and re-booting, right?
 
Having a similar problem with a Thrustmaster Warthog Joystick I just bought since 3.0.

Not being recognised.

It works fine and I can programme axis from it but it's just a generic stick and no presets.

I have a copy of my keybinds saved separately and have an idea. Going to do a minor tweak to the generic joystick to try and create a CustomBinds2.0 file, then replace it with the one I have saved. See if that works. can't do it till tomorrow though (currently reinstalling on Steam and the regular launcher, just in case)

PC recognizes, but E: D does not? Hm. We have the exact same HOTAS, and I've never had any issues with keybindings or disconnects. Very odd. And you've tried standard re-connecting and re-booting, right?

Of course. Even reinstalling--both the game (on and off Steam) and the drivers. Also tried different ports, uninstalling USB ports and rebooting, etc...
 
Are you able to check if your HOTAS works as intended in other games?
got no other games that require it, but the drivers have a testing program and all buttons and axis are working fine. windows 10 recognizes it in its system settings too.

BTW I have the newer 4, not the X model
 
Hey Guys,

Not sure if this may be a similar issue some CMDRs found with my script/bindings after the 3.0 update. It is sounding like the same symptoms (profile bindings are there in folder but not showing in ED). In my case, it was because I have MFG Crosswind rudder pedals mapped in my bindings but some CMDRs who dont have one connected found the bindings were crashing. It was looking for a GUID not present on their system & instead of ignoring like it used to it crashes loading the bindings.

There was a solution I reposted here: https://forums.frontier.co.uk/showt...rthog-Script?p=6452674&viewfull=1#post6452674

Short version, check bindingloadingerrors.log, if error showing along the lines of "Failed to find GUID for device" take note of the GUID # and then load your bindings file in a notepad and replace all of those GUID "{NoDevice}". Restart the game and your bindings should appear. You might need to remap some things you cleared afterwards.

Might not be the same in your case, but thought I would share in case it helps.

Cheers, AD
 
Last edited:
I still have the Custom.2.0.binds file saved elsewhere, but placing it back where I found it does nothing to restore my old settings. Does it need to recognize the Thrustmaster first? Is there any way to manually make it recognize the T.Flight?

I really can't play the game without my HOTAS and don't want to spend an hour resetting all the binds just to have someone say "Oh, you could have done this instead" to fix it.
 
Short version, check bindingloadingerrors.log, if error showing along the lines of "Failed to find GUID for device" take note of the GUID # and then load your bindings file in a notepad and replace all of those GUID "{NoDevice}". Restart the game and your bindings should appear. You might need to remap some things you cleared afterwards.

Might not be the same in your case, but thought I would share in case it helps.

Cheers, AD

Couldn't even find a bindingloadingerrors.log anywhere in my C drive.
 
I just reinstalled Elite Dangerous (trying to resolve an issue since the update) and for some reason my Thrustmaster T.Flight 4 isn't being recognized by the game anymore. It's not showing up in the Controller options (just Keyboard only, Empty, Keyboard and Mouse, Generic Joystick). Dunno what "empty" is supposed to be. But before the reinstall there was a thrustmaster profile as well. And I had a custom one too (which I copied and saved to put back in after the reinstall).

I tried to reinstall the Thrustmaster drivers too, but no change.

Any ideas?

I did a bunch of stuff a few months back. I had the same symptoms.
It turned out I pluged my hub into itself. I thought everything was pluged in, which it was.
But the Hub was never plugged into my laptop.

Duh
 
Do you use a gamepad with the hotas, too? Mapped to SRV controls perhaps? Is it battery powered? Be sure it's powered on before you start the game. New "feature" in 3.0. :)
 
Back
Top Bottom