You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes when a device is created on the server, the device never creates axis events, only buttons/keys. LowLevel.writeEvent returns 0 but nothing happens. As far as I've seen, it only happens when the gamepad is interacted with within a second or so of loading. Refreshing and waiting briefly usually fixes it.
Could be a libevdev bug. Hard to diagnose further without more testing in different environments.
The text was updated successfully, but these errors were encountered:
As far as I've seen, it only happens when the gamepad is interacted with within a second or so of loading.
I'm increasingly sure this is what makes the difference. So it seems that there is some kind of race condition at startup. We need to wait for the device to be fully initialised, whatever that means.
It's possible this only requires changes in the evdev library, and not in monpad itself.
georgefst
changed the title
evdev events not firing
evdev race condition
Aug 6, 2020
Sometimes when a device is created on the server, the device never creates axis events, only buttons/keys.
LowLevel.writeEvent
returns 0 but nothing happens. As far as I've seen, it only happens when the gamepad is interacted with within a second or so of loading. Refreshing and waiting briefly usually fixes it.Could be a libevdev bug. Hard to diagnose further without more testing in different environments.
The text was updated successfully, but these errors were encountered: