Mousewheel Scroll issues.

[HORSE ARMOR ENTHUSIAST]

50.09 borked my mousewheel controls. Last patch was just fine, but now any sort of delicate mousewheel movements (going up or down one z-layer) will misread the direction of my mousewheel input. This results in any scrollwheel movements invariably going to the top z-level or top of a list. Any help is appreciated.

[Nautilus]

I haven't had this exact issue but I did have my mouse wheel randomly stop scrolling z levels a few minutes after updating. And I fixed it by resetting all my keybinds to default.

[Fletch]

Have you tried rebinding yet?
Settings --> Keybindings --> General --> Zoom In / Zoom Out

I did read in the Kitfix Discord #bug-discussion[discord.com] channel where Putnam reworked the mouse code and you may just need to rebind those settings in the options menu to fix it. If all else fails, report the issue in that discord channel. Good luck!

[Dandurandurandurand]

I am having this issue as well. I am going to try reverting to the current release instead of the public test and see what that does.

[Python Boot]

I am experiencing this issue now on Fedora with DF 50.13. When I try to re-bind, it only recognizes Mouse Wheel Down as the input—it looks like it is triggering both up and down when I scroll, but it triggers down last so that is what gets detected.

[Python Boot]

Originally posted by Python Boot:

I am experiencing this issue now on Fedora with DF 50.13. When I try to re-bind, it only recognizes Mouse Wheel Down as the input—it looks like it is triggering both up and down when I scroll, but it triggers down last so that is what gets detected.

Although, I recent tested on another machine running Fedora, and the scroll wheel works fine on that one. Looks like I have b0rked my main install somehow.

[AlP]

See if it happens in other games.

[BoogieMan]

I recently starting having a problem where I'd scroll and it just wouldn't respond until I scrolled for like 2 seconds. Normally I could just scroll up or down a little bit and it would go one level at a time. But as I said, I sometimes have to do it for a few moments before it responds.

[dddave]

I too am having this issue. Fedora 40 (KDE) on framework laptop. Happens on both mouse and trackpad. It's like under/over sensitive? When trying to set the keybinding to mouse up/down it will be very jumpy, not sure how to better describe. Basically when scrolling up it will say mouse down unless I scroll far, but then the settings start to scroll.

Wondering if it's OS, hardware or just a general bug.

Mouse MX Master 3 (just saw someone mention it here: https://dwarffortressbugtracker.com/view.php?id=12636

e: fixed broken url

[Mat0uz]

Originally posted by dddave:

I too am having this issue. Fedora 40 (KDE) on framework laptop. Happens on both mouse and trackpad. It's like under/over sensitive? When trying to set the keybinding to mouse up/down it will be very jumpy, not sure how to better describe. Basically when scrolling up it will say mouse down unless I scroll far, but then the settings start to scroll.

Wondering if it's OS, hardware or just a general bug.

Mouse MX Master 3 (just saw someone mention it here: https://dwarffortressbugtracker.com/view.php?id=12636)

I'm running fedora 40 (gnome) myself and use a mx master 3, rebinding doesn't work. I updated the firmware of the mouse mouse which didn't help. A work around that works seems to be running the game in compatibility mode using steam linux runtime 1.0 (Scout).
I'm using scout because its the first thing that work.

BTW that link to the mx3 bug issue doesn't work

[Python Boot]

I have found that the issue does *not* happen in other games.

I noticed that another poster also has a Framework laptop running linux—that makes me suspicious that there may be an issue with how the touchpad firmware interacts with the OS.

I did a fresh Fedora install a couple of days ago and it did not resolve the problem, but when testing it today the scroll issue is not occurring with the touchpad or a physical mouse (Logitech M720 connected via Bluetooth), even though it *did* occur with both inputs before.

Clearly, my computer is haunted.