When trying to implement an asynchronous force-feedback forwarding identical to the example given in the docs, using the fftest tool, there are many duplicate ecodes.EV_FF events which cause highly unpredictable rumbling behaviour on the physical gamepad.
Simply altering it to a synchronous version with for [...] read_loop(), as per the docs, instead of async for [...] async_read_loop() causes correct behaviour, but this means I can't fire it off asynchronously with an event processing loop for the physical device. I assume this is some sort of bug in the asynchronous handling of EV_FF events (the upload/erase events seem to be working fine, in contrast).
I guess the workaround from my perspective is to manually multithread my two processing loops, instead.
When trying to implement an asynchronous force-feedback forwarding identical to the example given in the docs, using the
fftest
tool, there are many duplicateecodes.EV_FF
events which cause highly unpredictable rumbling behaviour on the physical gamepad.Simply altering it to a synchronous version with
for [...] read_loop()
, as per the docs, instead ofasync for [...] async_read_loop()
causes correct behaviour, but this means I can't fire it off asynchronously with an event processing loop for the physical device. I assume this is some sort of bug in the asynchronous handling ofEV_FF
events (the upload/erase events seem to be working fine, in contrast).I guess the workaround from my perspective is to manually multithread my two processing loops, instead.