I see that Unity will support > 4 XInput controllers (not possible using XInput), and ones that are not associated with an XInput device will still function, except Axes 8 and 9 do not function, as expected because they're HID devices. The symptoms have changed, but the underlying cause is still the same from what I can tell. I can still reproduce issues related to the HID->XInput association which Unity is still doing, though not the exact same issues as before. Only 4 XInput controllers can be used at once.Ĭlick to expand.Actually, I just did testing on 2019.3.0b2 on the legacy input system. In this case, XInput tells you one thing - this is a gamepad.
You must work within the limitations of the underlying input APIs. Rewired will never attempt this kind of "fusion" to work around Microsoft's built-in limitation, and I certainly hope Unity doesn't try to do this in their new input system. That's why you will see many complaints on the forum about XInput gamepads triggers responding on the wrong device when multiple devices are attached in some scenarios.
All attempts to do this fail at some point or another with multiple controllers attached. However, read the forums and you will see many, many problems that come from this "fusion" because there simply is no reliable way to fuse these devices because Microsoft gives you no way to associate an XInput device id to a HID device.
#Xinput test not connected windows
Unity has been combining XInput and HID for XInput controllers for years on Windows using the L/R trigger values from XInput and the name and other elements from the HID device. This is an XInput limitation and cannot be worked around reliably. This is one of the most common questions I get from Rewired users. Click to expand.The console is not using XInput to display that information, it's using information from the HID device.
0 kommentar(er)
