Pulsar Mouse Linux, an unofficial configuration tool for Pulsar gaming mice on Linux, has been released in version v0.1.21.

The update follows versions 0.1.19 and 0.1.20. A page now counts as read only when all fields that Apply writes come back. It also fixes a timing problem after a mouse swap, where reads from the tray and the window got in each other’s way.

A follow-up to v0.1.20, from four runs of it on hardware.

A page is only marked read when everything Apply writes came back

Previously, Apply could write an unread page after the DPI stage read had completed on its own. Now, “every field Apply writes now has to come back on that pass.” Missing fields that drivers don’t implement are not treated as failures - only actual incomplete responses keep a page unread.

Timing issue after a device swap

After a swap, the tray and the window could read at the same time. The window queues its initial read on the main loop, so the tray’s read could slip in between window initialization and that queued read. The fix: “A read now counts as in flight from where it is queued rather than from where its thread begins.”

Testing on a Pulsar X3 with a 1K dongle showed different behavior, including a sleeping mouse reporting 125 Hz on a device configured for 1000 Hz.

Contributors: f-o-o-g-s

Source: GitHub