HOTAS used to work perfectly, Elite now refuses to see it

Craven287

C
One day, the game works fine. Next day, launcher opens, click play, launcher crashes, no game. Uninstall game, reinstall game, launches properly but HOTAS (Thrustmaster 16000M FCS) no longer recognized, controls automatically set to KB+M.

Tried different USB ports, both on the hub and directly on the board, doesn't matter. Uninstall game, remove everything Elite related under AppData and other hidden folders, reinstall game, HOTAS still not recognized, either through the USB hub or directly on the board even though it's a fresh install again.
Even installed the HOTAS drivers which I never needed before but that didn't help.

Other games that support a stick still recognize the stick, both through the hub or directly. Elite still recognizes my controller either through the hub or directly.

"BindingLoadingErrors.log" > "There where errors when loading preset file: T16000MHOTAS.binds
Missing devices: T16000MTHROTTLE, T16000M"
Device manager does see both devices connected.

I have no idea what's going on or how to fix it and I'd greatly appreciate any advice possible. I really want to fly again...
 

STRONTIUM DOG

STRONTIUM DOG
read this first afterwhich we may need to dicuss a device id change which is coverd in part in the same few page thread

lost your binds? want hasstle free backed up binds look no further

keybindings can reset if you visit the control section without one of your usual devices used to play the game ie hotas , xbox pad etc not plugged in or at that present moment is undetected by windows as it thinks your just using keyboard and mouse it simply rewrites your binds for you...
forums.frontier.co.uk forums.frontier.co.uk


hopefully youll find a slighly older bindfile that has not been overwritten plug in restart an bobs your unc otherwlse you may need to change the device id in the old bindfile
 
Last edited:

Craven287

C
Found a binds file in a backup. Threw it in the Bindings folder but no success so far. Where do I change the device ID in that file? Did a search for "ID" in the binds file but that got me 116 results all labeled as humanoid controls.
 

STRONTIUM DOG

STRONTIUM DOG
first lets see if we can get the device recognised
grab the binding folder and cut and paste it to your desktop
restarting the game with the folder missing it should create a new one and in doing so get your already pluggen in devices re recognized
so try setting some new binds up with that new"folder"
youcan swap back folders later
you can use notepad++ find and replace feature to swap a device id back to an old bindfile
 
Last edited:

STRONTIUM DOG

STRONTIUM DOG
that is strange the new folder should pick up any new device id upon game restart
have you tried selecting the ingame custom preset and maunually changing a hotas binding
has the device got a console/pc switch near the base
 
Last edited:

Craven287

C
Ship Controls set to custom, tried to change a binding, it registers the mouse, the keyboard, the controller but not the hotas.
No switches on the device.
 

Craven287

C
Done, game now has a "generic joystick" in the presets. My stick still isn't recognized.
Earlier, you mentioned something about changing device ID's. Is that something to try?
 

STRONTIUM DOG

STRONTIUM DOG
yes but we need to establish the new device id which maybe in the generic joystick bindfile which we can find and replace in the old bindfile later so can you rebind the hotas atm using the generic preset ie is the device responding at all
 

Craven287

C
Nothing's happening, HOTAS works on other games, Elite keeps refusing to see it.
I can probably get the device ID from device manager but I'm not seeing anything in the binds where to replace it.
 

Craven287

C
Some sort of progress has been made, getting a different error message now.
"Missing devices" has become "Failed to find GUID for device".
Going to get some sleep, I'll see about figuring this out tomorrow.

Thank you for all the help.
 

STRONTIUM DOG

STRONTIUM DOG
The "Failed to find GUID for device" error in Frontier (Elite Dangerous) typically occurs when the game can't recognize a connected input device (like a joystick or HOTAS) due to a change in the device's ID or if the device is not properly connected. This often happens after updates, hardware changes, or when using different USB ports. The error message usually appears in the bindingloadingerrors.log file and can cause the game to revert to default bindings.

Here's a breakdown of the issue and potential solutions:
Understanding the Problem:
  • GUIDs (Globally Unique Identifiers):
    Each device connected to your computer has a unique GUID, a long string of numbers and letters that identifies it.

  • Binding Files:
    Elite Dangerous uses these GUIDs to map your custom controls to specific devices. If the GUID changes, the game can't find the device and thus can't apply your custom bindings.

  • Common Causes:
    • Changing USB ports: Different ports may assign different GUIDs to the same device.

    • Hardware changes: Adding or removing devices can shift the order and thus change GUIDs.

    • Game updates: Updates can sometimes alter how the game reads device IDs.

    • Flaky USB connections: Loose or low-power connections can cause the game to miss the device.
Troubleshooting Steps:
  1. 1. Check USB Connections:
    Ensure all input devices are securely plugged into the same USB ports they were previously using.

  2. 2. Rename or Edit Binding Files:
    • The game creates a backup of your bindings file with ".binds" extension when it encounters a GUID issue.

    • Locate this file (usually in the game's AppData folder) and either rename it to something like Custom.4.0.binds.old or open it in a text editor.

    • If you know the specific GUID that's causing the problem, you can search for it within the file and replace it with a valid GUID from a working binding file or a newly created one.
  3. 3. Create a New Binding File:
    • Start the game and create a new, temporary binding profile using the affected device.

    • Save this profile. This will generate a new .binds file with the correct GUID.

    • Open both the old and new .binds files in a text editor (like Notepad++) and compare the device information. Replace the old device information (including the GUID) with the new information.

    • Save the old .binds file and restart the game.
 

Doctor Dread

Doctor Dread
Craven287 said:
One day, the game works fine. Next day, launcher opens, click play, launcher crashes, no game. Uninstall game, reinstall game, launches properly but HOTAS (Thrustmaster 16000M FCS) no longer recognized, controls automatically set to KB+M.

Tried different USB ports, both on the hub and directly on the board, doesn't matter. Uninstall game, remove everything Elite related under AppData and other hidden folders, reinstall game, HOTAS still not recognized, either through the USB hub or directly on the board even though it's a fresh install again.
Even installed the HOTAS drivers which I never needed before but that didn't help.

Other games that support a stick still recognize the stick, both through the hub or directly. Elite still recognizes my controller either through the hub or directly.

"BindingLoadingErrors.log" > "There where errors when loading preset file: T16000MHOTAS.binds
Missing devices: T16000MTHROTTLE, T16000M"
Device manager does see both devices connected.

I have no idea what's going on or how to fix it and I'd greatly appreciate any advice possible. I really want to fly again...
Click to expand...

@Craven287
What Win version are you using, 10 or 11?
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom