Hey guys, my xbox one controller doesn’t seem to be working when I "play"in the editor… Works fine if I launch in 4.7 but not in 4.15.
Its plugged in so I’m not using wireless.
Tried updating drivers to x64 with x360ce, placed the xinput1_3.dll in the Epic Games/Launcher/Engine/Binaries/Win64
Controller works fine playing unreal and Shadow complex but not in the 4.15 editor when I hit “play” as it does in 4.7
Any ideas? Much appreciated.
CoOps
I was having this same problem using 4.14. I tried updating and reinstalling all my drivers as well as various xinput settings but nothing worked. Eventually when I tried installing 4.15 the Xbox One controller began working. However, I have just tried it again in 4.15 and it is no longer working. Nothing on my system has changed, which makes me think that this is most likely a bug with the 4.14/4.15 editor. On running the console command show debug input I can see that no input is received from the gamepad.
If you have any luck with finding a solution please let me know, likewise I will do the same.
Hey maxochel,
I just installed 4.16 and the xbox one controller works like a charm. You can even use the controller to navigate in the viewport which is ace!
Thanks for your reply, go 4.16 if possible 
Using 4.18, had the same problem as above.
Closed and reopened the Editor and everything was fine.
Basically: connect the controller BEFORE opening the editor
Still experiencing this issue in 4.22. 
I have a wired xbox 360 controller, and it works with navigating in the editor viewport, but I get no response whatsoever from it when playing in editor or standalone.
Hey Acriax, just be sure to have your controller plugged in before you launch your ue4 file.
Ysgrathe: Basically: connect the controller BEFORE opening the editor
I really wish it would be that simple. Still the same issue in a fresh first person template project on a fresh install of 4.23. Works inside the editor to fly around the viewport, but when pressing play, none of the axises or actions works. Otherwise, the gamepad works fine in windows and in games. It’s just UE4 that has problems when pressing play in the editor (both in PIE and Standalone modes).
Did it just start working for you or?
Hey Acriax,
The controller is working in the editor but ignored when playing, sounds like you need to
map controller settings in the Project.
Project settings>Input>Mapping
Here a great video regarding doing this by Mathew Wadstein.
Hope this helps, I’d subscribe to Mathew’s “youtube channel” he’s brilliant.
Hope this helps!
I was just going to reply the same thing. 
My first attempt to debug this would be to check an axis setting
Project Settings>>Engine>>Input…
Then under Axis mappings (not Action mappings), make sure you have something mapped like ‘MoveForward: Gamepad Left Thumbstick Y-Axis’
Then check to see if anything happens in the MoveForward Event and go from there
Thanks, but this happens even on fresh first person template projects, which already have gamepad input setup properly. However, I found out the reason… kinda. For some reason, the gamepad input is completely ignored by the first player, but if I play with 2 players, the second player moves with the gamepad. And I know there are options to enable this in the settings, but none of those are checked, and I’ve tried checking and unchecking them to no avail. UE4 just flat out refuses to give player 1 any gamepad input.
In Project Settings>>Maps and Modes,
What is the state of the ‘Skip assigning Gamepad to Player 1’ checkbox?
Unchecked, tried all combinations of those two. 
And if I check Dedicated server, no player gets gamepad input either. Very strange indeed…
I just created a new 1st person template in 4.23
literally did nothing else. Ran it, controller working fine out of the gate.
Could it be a windows setting somehow?
Or have you changed something in an INI file that would affect all games for that engine version?
Yep, that’s how I would expect it to work. Nope, nothing like that. Only thing I can think of is some Windows Update causing it at some point, but it is a very weird issue in that case, if it specifically targets player 1 of UE4 games.