[SOLVED] Mouse too sensitive in 3D games (it was due to dwl)

[LemonadeLlama]

I have recently built a new gaming PC. I have an AMD 7000 XT. I'm running Gentoo Linux with wayland, SDDM, dwl (like dwm but for wayland).

The graphics card works fine, but I think there's something wrong with my mouse or my drivers. I have tested out both 2D games (Hexcells and Slay the Spire) and 3D games (Doom 2016 and Slime Rancher 1). All of this is tested through Steam. In the 3D games, the mouse sensitivity is so high that it's unusable. Characters will just spin violently in a circle with the slightest movement.

Even after turning the in-game sensitivity to the lowest setting, and even after using the DPI button on my mouse to turn DPI to its lowest setting, 3D games are still unplayable.

I have attached my dmesg output here: https://pastebin.com/uqj0gunh

The only other thing I could find was an error in my Xorg.0.log file (I didn't think these logs existed for wayland but okay I guess):

[shadowless]

Those warnings in that Xorg log are unrelated to the mouse.

WARNING: Incorrect information below
In wayland... input devices, such as a mouse, can be tweaked with by configuring libinput.

You might want to try reducing the pointer acceleration or disabling it:
https://wiki.gentoo.org/wiki/Libinput#Pointer_acceleration

[CooSee]

your mouse has a DPI cycle button to decrease or increase!

please look at it in the manual/setup guide.


_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier "

[LemonadeLlama]

[shadowless]

I apologize. I believe I have given you incorrect information. That configuration is for X, not wayland.

Wayland actually does not use libinput's configuration, but rather leaves that to the desktop environment / window manager.

https://github.com/djpohly/dwl

And dwl says to edit the config.h and recompile. I do actually see settings for mouse acceleration in there, so hopefully this will help.


Also... wayland doesn't leave a log like X does by default, but with sway, you can redirect the stderr output to create somewhat of a log when you launch it... You could try this with dwl to see if it gives you anything useful:

[LemonadeLlama]

I have tried configuring dwl's mouse acceleration options. You can choose between LIBINPUT_CONFIG_ACCEL_PROFILE_FLAT and LIBINPUT_CONFIG_ACCEL_PROFILE_ADAPTIVE in the configuration file.
Neither of them fixed the issue.

[LemonadeLlama]

I only stuck with dwl because I used to use dwm when I had an X11-based PC. I might try switching to sway and see if that makes a difference.

[LemonadeLlama]

Well, for some reason, it turns out dwl was the issue all along.

I just switched to using sway and everything just works.

Time to annoy the dwl devs

[jackfrostenson]

I saw what happened to you and it scared me, it's the typical thing that one would never in life want to happen to them and that is to build their own gaming pc and have errors, I'm very glad that you were able to solve everything ♥