What's With The PC Controller Since EDO Update?

[LanceLord]

I haven't played ED on PC since I played EDO during its beta testing phase. Used my PC windows controller and didn't have any problems using it during the EDO testing phase.

All my recent gaming progress had been on XBX to date. So in preparation for the CMDR account migration to PC, I logged on today to setup my game controls for both keyboard/mouse and game controller. Changed menu settings to both of these in the options. But while the keyboard/mouse work, the controller remains non responsive. Tried existing to desktop and relogging back in to same result. Also changed controls to game pad only as well as the USB port connections to no avail. Only the keyboard/mouse controls work. Is there an .ini file I could modify to hard code/fix this issue? Or am I committing some obvious brianfart that's causing this malfunction?

 

[Fnord Velkor]

Is it a Xbox wireless controller? I had to buy a "Xbox Wireless Adaptor for Windows 10" to get mine to be recognised by the game. ¯\(ツ)/¯

 

[LanceLord]

As a matter of fact it is. But what's weird is I didn't need this before during the Beta?

So it seems FDev changed some game control mechanic at the fundamental level. Anyhow, will try that. Hopefully it works. Haven't tested whether my HOTAS works on the PC version either. So here's crossing fingers and all toes it does >,<

Thanks for the feedback! o7

 

[STRONTIUM DOG]

I heard you can trick it back into recognition working by using a wired one though the method of unplugging and changing the device id in the bindings file alluded me...……………..

 

[Ashnak]

I wouldn't put the blame for that at FD - beta was when, 2014? 2016? Even if you used the same PC hardware with Windows 10 back then, a lot of system updates went down since that time.

So, no, it's not an FD issue - inasmuch as FD uses the most common baseline controller connection through the OS (Windows 10, mostly, nowadays). And that connection depends on the Bluetooth hardware and driver(s) on your specific motherboard (or dongle). Which may or may not keep the connection to the controller continously active even when no controller input is present.
Other games will simply decode the signal when/if it eventually comes in and then switch to the correct controller scheme (you can see that in a lot of FPSes when you have the controller help overlay active - press a key on the keyboard, and the help overlay switches to keyboard until you move one of the sticks again). ED with its highly flexible approach has shelved this approach - the controller setup is fixed at startup, and if the defined controllers aren't all foound, it falls back to kb+m as the least denominator.

As a bottom line: if you want a reliable connection, you'll either have to use wired or a dongle that is handled correctly by the OS. In case of Win 10 and the XBox controller, that's the XBox controller dongle.

 

[LanceLord]

You misunderstood me. It was the EDO beta I was referring to. I've played it and Horizons with zero issues since 2016. Until post EDO release when I took a long vacation from the PR scat storm fallout on consoles. Some 98% of my total game progression is on the console side. Lol.

Ah well. Lesson learned. I'm a prejudicial PC gamer but make console exceptions for certain game franchises (GTAO, RDR2) to help me troubleshoot and play test mods for PC version. In ED case it was a HD space issue on my PC. Didn't have enough HD space on my PC when I first got the game. So started playing on console. Over time my console CMDR ended up becoming the main account as result.