Xbox controller is not detected

The log says:

1.55686|D|DirectInputManager::EnumDevicesProc|Direct Input device not registering, since its an XInput compatible device: 'Controller (XBOX 360 For Windows)', 'Controller (XBOX 360 For Windows)'​

In the game, only mouse and keyboard is detected.

In the inputmaps folder, I have four files with different guids:
5EEA8560.diff
028E045E.diff
0719045e.diff
keyboard.diff

The guid files have the correct guids entered inside, I've taken the guid from Euro truck simulator 2's config file.

Now here's the small detail that might change this scenario compared to others. I use custom xbox 360 drivers from a Japanese guy that allows rebinding of the controller. In most other games, the controller is detected without any problems and can be used.
I use these custom drivers in ETS2/ATS in order to use the both triggers on separate axis. The default xbox drivers won't allow for separate trigger axis in most games where it is supported, they just share a centered axis most of the time.

I would try and reinstall the original driver and try it, but I don't want to do it if I don't have to.

I have searched for an answer to this problem for several hours, and the wikipedia page where you can remap your controller doesn't have the content it used to. It now states to magically add the controller in game and everything should work.

 

so you cant map any functions in the settings?
thats unusual, normally you should be able to manually map buttons even for controllers that are not supported by default.
if the game is not registering inputs at all im afraid you would have to install the default driver to make it work.

 

I reverted the drivers and the game registers the xinput device and there are default controllers bound to it.
Problem is, in ETS2, the triggers are on the same axis but in BeamNG they aren't. You can see on the picture attached that in ETS2, both the brake and accelerate button is bound to the Z-axis, which is the triggers' same axis.

In the inputmap for the controller, it states:
"action" : "brake", "control" : "zaxis"
"action" : "accelerate", "control" : "rzaxis"
which showes that even BeamNG have to tackle this issue, but the developer realized that there was a rzaxis that could be used instead of sharing the axis.

I'm going to dig deeper on this issue so that I can use the controller with split axis.

I'm also looking into making shift states for the buttons. I use select and start as shift buttons which gives me access to more than double the amount of buttons the controller normally would allow.

 

since beamng seems to be able to use both axis seperately there must be a way to set it up in ets as well.
i dont own that game so i dont know anything specific but maybe someone on the ets forums knows how to do this.

a little off topic but if you play a lot of games like this i would recommend you to spend a little on a force feedback wheel.
you can get a used logitech g27 for under 200 bucks and you will get a fully working h-shifter, clutch pedal and 900 degrees of steering rotation.
i have been using the previous version of that wheel for about 10 years and it still works great so these things last a long time.

 

I got it to work. I had to force Windows to use the custom drivers and then unplug, replug, restart the computer until the green light came on. The problem was that the green light wasn't on which means Windows doesn't register the device properly. When I had a wireless control earlier, it always had the green light on because it was connected to a receiver. After the fuse in the receiver blew, I woved to not use the wireless controller again.
This is how it looks ingame now:

Game with separated axis and custom drivers.

Moderator may close the thread.

Solution is to install the custom drivers properly until the green light turns on, on the controller.