Document an opt-in MX Master 3S wheel workaround for GeForce NOW games

[SamiJ]

Proposal

Could Omarchy document an opt-in workaround for mouse wheels that work normally in desktop applications but need rapid spinning to register in a game? A troubleshooting entry in the mouse or gaming manual would be a useful first step; an optional setup command could follow if maintainers think it belongs in Omarchy.

The workaround below was confirmed to restore slow wheel zoom in Against the Storm through GeForce NOW while preserving normal Chrome scrolling. This is a compatibility workaround, not proof of a bug in Omarchy or a recommendation to disable high-resolution scrolling for everyone.

Workaround to document

For the MX Master 3S, keep the mouse hardware's high-resolution wheel mode enabled/kernel-managed. Disabling that mode in Solaar is a different change and made desktop scrolling slow in the test.

Instead, have libinput consume the kernel's accumulated whole vertical wheel steps:

1. Back up /etc/libinput/local-overrides.quirks if it already exists. Preserve unrelated entries.
2. Create the directory if needed with sudo mkdir -p /etc/libinput, then use sudoedit /etc/libinput/local-overrides.quirks to append:

[Logitech MX Master 3S vertical wheel compatibility]
MatchName=Logitech MX Master 3S
MatchUdevType=mouse
AttrEventCode=-REL_WHEEL_HI_RES;

3. Install the validation utility through Omarchy if needed and check the file:

omarchy pkg add libinput-tools
libinput quirks validate

Find the mouse's current eventN entry in /proc/bus/input/devices, then run libinput quirks list /dev/input/eventN using that actual path. It should include AttrEventCode=-REL_WHEEL_HI_RES;.

4. Save work, log out, and log back in. Reloading Hyprland configuration alone does not reinitialize libinput's quirks database. Restore the backup or remove the new section if validation fails before restarting the session.

Tradeoff: this replaces fine-grained vertical wheel input for the matched mouse across applications. It leaves horizontal wheel events and devices that do not match, such as the touchpad, alone. It has not been established as necessary for all MX Master users or all games.

Undo: remove only the section above, preserve other entries, validate again, then log out and back in.

Contribution scope

I would start with documentation. If an optional setup command is preferred, it should preserve existing quirks, validate changes, offer removal, and explain the session restart and scrolling tradeoff. No automatic migration or new global default is proposed.

Libinput documents local device quirks and validation and filtering high-resolution wheel event codes. The latter describes a different failure mode; it is a reference for the filtering mechanism, not a diagnosis of faulty mouse firmware. Quirks are internal API and may need revisiting after libinput updates.

Related: #7574 suggests a per-device input panel. Would a documentation PR be welcome, or would maintainers prefer a different place for this workaround?

[SamiJ]

I’ve also submitted this through GeForce NOW’s in-app Send Feedback and shared reproduction steps plus the confirmed workaround in the existing NVIDIA forum thread.

That reply links back here. The workaround is confirmed on my setup; the underlying cause remains unconfirmed.