This means, we may miss input events like button presses: If I manage to press a button multiple times per 100ms, it will register just one button press/release.Īccording to btmon there was no other Bluetooth activity from other devices at the same time, so it's probably not an air-time issue. Many console devs are dumb and use triple buffer vsync. Also, each report reflects the input state of the controller at that point in time (the live state), it's not like the events are just buffered and replayed from a queue. Could somebody that has an Xbox Series X and plays kbm tell me what the input delay is like thank you. This introduces a lag of 100ms for events because reports may come in up to 100ms late. The problem is reproducible for axis movement.The incoming reports stop after some seconds, seems to depend on the amount of events generated before.
After stopping pressing buttons, HID reports still come in at 10 Hz, key bits are 0.
HID reports will have their key bits updated immediately with the next 10 Hz cycle.Releasing the button again, and repeating the first two steps in a quick succession generates reports at 10 Hz.Pressing a button will generate a report immediately.I'm not sure if that may be an issue of the device firmware itself, or if there is some HID report throttling inside bluez: It is somewhat difficult to describe, it's not exactly high latency but a strange effect. While testing the device, I found a high latency of input. The xpadneo project is a driver for such a HID device.
Input delay xbox series x drivers#
The new model of the Xbox Series X|S controller is a BLE device, it thus uses virtual/uhid to create a HID device in user space inside the bluez daemon and exposes it to kernel drivers this way.
0 kommentar(er)
