Wrong mapping of XBox 360 Controller

[vrguru]

Hi.

I have been using OIS 1.4 and recently upgraded to 1.5.1 Now it turns out that the mapping of an XBOX360 controller is absolutely remapped in a totally random way as I see it.

I built the console example and it shows the same thing.

Version 1.4:

OIS Version: 1.4.0
Release Name: 1.4.0
Manager: Win32InputManager
Total Keyboards: 1
Total Mice: 1
Total JoySticks: 1
        Device: OISKeyboard Vendor: Win32InputManager
        Device: OISMouse Vendor: Win32InputManager
        Device: OISJoyStick Vendor: Controller (XBOX 360 For Windows)

Creating Joystick 1
        Axes: 5
        Sliders: 0
        POV/HATs: 1
        Buttons: 10
        Vector3: 0
Startup done... Hit 'q' or ESC to exit.

Controller (XBOX 360 For Windows). Button Pressed # 0

Version 1.5:

*** OIS Console Demo App is starting up... ***
OIS Version: 1.5.1
Release Name: 1.5.0
Manager: Win32InputManager
Total Keyboards: 1
Total Mice: 1
Total JoySticks: 1
        Device: OISKeyboard Vendor: Win32InputManager
        Device: OISMouse Vendor: Win32InputManager
        Device: OISJoyStick Vendor: Controller (XBOX 360 For Windows)

Creating Joystick 1
        Axes: 6
        Sliders: 0
        POV/HATs: 1
        Buttons: 12
        Vector3: 0
Startup done... Hit 'q' or ESC to exit.

Controller (XBOX 360 For Windows). Button Pressed # 8

Lets just start there. Axis are also remapped (triggers). We see that a different number of buttons are reported. But most importantly, button A response is different.

Anyone else experiencing this?

[AnotherFoxGuy]

Anyone else experiencing this?

Yes, we ran into the same issue https://github.com/RigsOfRods/rigs-of-rods/issues/2891

[Ybalrid]

@AnotherFoxGuy Hi, I do not have a lot of free time to dig into the actual issue, but I would gladly review and merge a pull request that would fix it, if you or a developer from the ROR project wishes to contribute