# os. # I tried os.fork() to see if buffering was happening # the -u flag makes python not buffer stdios
#XINPUT TEST BLOODSTONE CODE#
My test code is below if helpful #!/usr/bin/python -u Moving your mouse will cause the data to print in buffered chunks just like your code. This can be verified with xinput test 15 | cat. When not connected to a TTY, it doesn't flush the stdout buffer with each new event. I re-wrote your code to eliminate buffering, but I couldn't get it to not come out in chunks, hence why I believe xinput is to blame. When running your code, keep moving the mouse and eventually xinput should flush stdout and you'll see your lines show up in chunks. They're going to face the same issues.Your code works for me however it looks like the xinput cmd buffers its output if not connected to a tty. I recently read that Steam/SDL2 are looking into combining HID and XInput devices to try to get past the 4-controller XInput limit because players are always asking for it. This would explain why things get mixed up and you can be controlling multiple devices with one controller while another controller is just dead and contributes no input. It's still fusing the HID device to the XInput device for the purposes of displaying the HID name and for determining whether to use XInput or HID for the element values. So it appears to me the Unity legacy code was changed at some point in the past to not read joystick values from HID combined with triggers from XInput like they used to, but it is switching between using the XInput or the HID device entirely for element values. Doing some controller unplugging and replugging easily confuses the XInput-HID fusion and you're left with physical controllers that control multiple Unity joysticks simultaneously - one being a HID device (no Axis 8, 9) and one being an XInput device (Axis 8, 9 work). Unity is combining XInput devices and HID XInput devices into a single list, and is still attempting to make an association between HID devices and their XInput id's. 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. Provided by: xinput1.6.3-1amd64 NAME xinput - utility to configure and test X input devices SYNOPSIS xinput OPTIONS DEVICE DESCRIPTION xinput is a utility to list available input devices, query information about a device and change input device settings.
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 BLOODSTONE 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)
