Different ports for control interfaces shouldn't be a problem - the client goes by device ID, so as long as it's attached and powered on when the game starts... it should work. If there is a missing device ID, the game will launch with a default binds set. Helpfully, there is a log file, found in your bindings folder, which tells you the device causing the error. If you plug your DS4 into another port, you may well need to install the device driver. I have to do this for every port I plug my gamepad into.
The log file is in:
You will need to set Windows to display hidden files and folders.
You can disable Steam's controllersupport interference in Steam > Settings > Controller > General Controller Settings. I use a wireless Xbox 360 Gamepad with no Steam issues, only the above-mentioned driver install, which is a Windows issue.
Launching the game through Steam passes your credentials to the launcher automatically. Launching directly from the launcher (within the Steamapps folder) will require you to log in manually the first time, which includes entering a code sent to the email address you provide when you create a Frontier account. I've never had any issues with launching the game this way, and I suspect it might also prevent Steam interfering with the attached controllers.
The log file is in:
Code:
C:\Users\<Your user>\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings
You can disable Steam's controller
Launching the game through Steam passes your credentials to the launcher automatically. Launching directly from the launcher (within the Steamapps folder) will require you to log in manually the first time, which includes entering a code sent to the email address you provide when you create a Frontier account. I've never had any issues with launching the game this way, and I suspect it might also prevent Steam interfering with the attached controllers.
Last edited: