Controller --FIXED

[Stiles]

Alright so I got everything set up for the controller (motionjoy) and it is being detected in-game, but when I go to assign the controls it identifies what button im pushing but it won't let me apply it.. was very happy to hear that the recent update fixes steering, would just love for this to work.

[CatBox]

Also, patchnotes say that Xbone controllers are now properly recognized, but it still shows up as two devices.

I can't map controls without something conflicting.

[Nadeox1]

I'm not too sure about motionjoy + BeamNG.Drive.

As for Xbone controllers, we didn't get any issue with that. In your Devices Manager, your controlleri is seen as one? Can you take a screenshot of the 'CONTROLS > Hardware' screen so we can see how the game names the controller?

[CatBox]

http://i.imgur.com/QFjdjs4.png

I have not had any issues with other games. Uninstalling the devices and reinstalling the driver from Microsoft results in the same issue. OS is Win 10 x64 with wired Xbone controller.

[Flying_Mushroom]

Cant bind any keys/axis on my Logitech Rumblepad 2 either. Worked fine before this update. Even tried to emulate it with x360ce but it didnt help.

The gamepad is properly recognized in both Windows 7 and the game itself (all axes and buttons)

[Stiles]

It see's it as a playstation 3 controller. I believe it was working in the prevoius update.

[Stiles]

Checking the command Lua or whatever, says "DirectInputDevice : : acquire | joystickO input device NOT acquired: Unknown error -2147220983"
dont know if that helps.

[Stiles]

FIXED--

[sag13]

how did you fixed it?

[Stiles]

Originally posted by sag13:

how did you fixed it?

https://www.youtube.com/watch?v=TpSaOJJIun8

[Nadeox1]

Originally posted by Horalka:

Cant bind any keys/axis on my Logitech Rumblepad 2 either. Worked fine before this update. Even tried to emulate it with x360ce but it didnt help.

The gamepad is properly recognized in both Windows 7 and the game itself (all axes and buttons)

We are looking into some issues that emerged with the new update. Your issue might be releted to those. We will soon release an hotfix as soon we got these covered.

[stenyak]

@catbox can you please copy your documents/beamng.drive/beamng.log file contents into http://pastebin.com and give us the resulting URL? Thanks!

[CatBox]

http://pastebin.com/maK9y13i

[stenyak]

@catbox, to be completely honest, I have no idea why that is happening, I am unable to reproduce the issue, I have found no one else experiencing the same issue as you, I see nothing strange in the logs, and I cannot even begin to think of a reason why a single controller would be detected as two separate controllers, even after reading and re-reading all the code that handles device detection :-(
If it is possible, could you please try with a different XBox gamepad? Can you also please make sure you have no strange software that may create conflicts (such as joystick emulator software, etc)? Or even better, try installing BeamNG in a different computer, and check if it also happens there?