Custom bindings created last night are not recognized this morning. Nothing changed!
- Thread starter lasvideo
- Start date
I would start by unplugging every other peripheral that uses a USB port on your PC (except a mouse). Launch the game with only the necessary controllers plugged in and see if the game recognizes them.
Also, check in your windows power settings to make sure that usb sleep or suspension is NOT allowed.
I also run VKB controllers and had issues on my old PC when I had too many USB ports active at the same time. If a single port stops working and one of the controllers was using that port, Elite will not even show the custom bindings file that uses that controller.
Also, check in your windows power settings to make sure that usb sleep or suspension is NOT allowed.
I also run VKB controllers and had issues on my old PC when I had too many USB ports active at the same time. If a single port stops working and one of the controllers was using that port, Elite will not even show the custom bindings file that uses that controller.
This can be really annoying.
If the game can't detect every piece of hardware used in a control config, it won't load it and it won't tell you it hasn't loaded it - you have to try to start using it. It won't even show you the option to select the config, even though the .binds file is still there. On my control setup, this can be particularly irritating as sometimes I don't find out until I try to launch the ship and my joystick isn't working.
There is a bindingloadingerrors.log file in the same directory as the binds file which will show you the USB ID of the device that wasn't initialised. This can help with troubleshooting, especially in combination with USBDeview, which will show you the USB ID of the device next to a human readable device name.
If the game can't detect every piece of hardware used in a control config, it won't load it and it won't tell you it hasn't loaded it - you have to try to start using it. It won't even show you the option to select the config, even though the .binds file is still there. On my control setup, this can be particularly irritating as sometimes I don't find out until I try to launch the ship and my joystick isn't working.
There is a bindingloadingerrors.log file in the same directory as the binds file which will show you the USB ID of the device that wasn't initialised. This can help with troubleshooting, especially in combination with USBDeview, which will show you the USB ID of the device next to a human readable device name.