I've spent the last 4.5 years standardizing a wide variety of input devices across over a dozen platforms. The fact that a controller maps differently when connected wirelessly and wired is the hardware manufacturer's doing. Hardware manufacturers basically do zero standardization (apart from Xbox controller clones). And the mappings of those buttons almost always change on different platforms because no two OS's input systems work the same way with regard to how they expose elements on controllers.
They simply provide a list of numbered buttons, axes, and sometimes hats. Most operating systems and HID devices do not give you any information about "sticks" or buttons by name. Their input system is just a thin wrapper on top of what the operating system input API provides. If this can help, find some details about the drivers here.Ĭlick to expand.You're expecting features that their input system has never provided because it wasn't ever intended to.
On steam, the Steam Controller work fine on Win 10 with old mapping (even if emulating a XBO ctrl), so it's quite difficult to find a fix/workaround for the Xbox controller without breaking the Steam Controller support.ĭo you (Unity tech team) have any news about that ? Here are a few threads about this (kind of) issue : Mechanic Escape (Unity 4 - released in April 15th 2014) Level 22 (Unity 5 - released in January 29th 2016) We reproduced the bug on a lot of unity games using the Xbox controller, for instance : Dpad not anymore on 6 and 7 but on 7 and 8 Triggers no more mapped on the 3th axis but on the axis 3 (left) and 6 (right) Indeed some axes mapping changed, especially : We have an issue with the Xbox controller axes since few days on Win 10 (only).
0 kommentar(er)
