I’ve been trying to use X360ce to enable a couple non-Xbox controllers for the editor. My problem doesn’t seem to have been documented before.
When I run x360ce_x64.exe inside of …/Engine/Binaries/Win64, it opens but the controller tabs remain blank and it never generates the .INI file it normally does.
What’s strange is that if I create a new folder inside of /Win64 (or outside of it) and run X360ce there, it works as expected. If I create a new folder inside of /Binaries, copy just UE4Editor.exe and x360ce_x64.exe and run it, it works as expected. But as soon as I add the rest of the contents of /Win64 to my new folder, it stops functioning. It’s as if there’s something included in /Win64 that’s stopping X360ce from creating an .INI or something.
I have enabled all permissions for both /Win64 and x360ce_x64.exe.
Thank you so much, @MC1RScorpion and @herb64 !!! I couldn’t figure out why the x360ce file was not generating the xinput1_3.dll and x360ce.ini files as before. Perhaps it’s because there are so many .exe files in Unreal’s Win64 folder it confuses the application.
The solution, as herb64 described, is to put the x360.exe file into a new empty folder anywhere on your drive, double click x360.exe to launch, then when prompted, create the xinput1_3.dll and let it search for settings for your controller. Customize if desired and finally press Save. Then close the application and paste the contents of that new folder (x360.exe, xinput1_3.dll, and x360ce.ini) inside the C:\Program Files\Epic Games\UE_(YourVersion)\Engine\Binaries\Win64 folder. Now simply launch Unreal Engine and you are good to go!!