![]() ![]() However, XInput only operates by a 'UserIndex" value and doesn't expose any kind of hardware ID, and so there's no way to reliably map a UserIndex with a HID hardware ID. The 2 triggers are combined to a single axis making it impossible to read them independently using HID, and instead the only way to read trigger input is via XInput. The core problem is caused by the way Microsoft choose to implement Xbox gamepads (Xbox 360 and Xbox One) on Windows, in that the left and right triggers cannot be properly read by the HID interface. This bug is part of a much larger issue with InputManager that's been around for a long time.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |