You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found it odd that a lot of people (if not all people) seem to fix their tablet input issue in lazer with just disabling the "high precision mouse" setting (a.k.a raw input) when it's a setting placed on the mouse category of the input settings. Seems like this setting is messing up with tablet input and if that's intentional, then I guess renaming the setting back to raw input and not placing it in mouse category would clarify and settle things.
In my opinion, mouse settings and tablet settings should not have a setting where one would affect the other since they're completely different input devices. If that can't be followed, then at least have the naming make sense where both devices can agree on.
You have to understand that if you're using an external tablet driver, then the only way lazer can see this input is in the form of mouse events (as in, the tablet driver is emulating your tablet input into mouse input for the entire operating system). Stripping the name "Mouse" from the option is pretty much moving the issue from tablet users to mouse users, I do not see that as a valid solution.
I'm moving this to a discussion thread until something is settled here.
ppy
locked and limited conversation to collaborators
Feb 12, 2024
Type
Game behaviour
Bug description
I found it odd that a lot of people (if not all people) seem to fix their tablet input issue in lazer with just disabling the "high precision mouse" setting (a.k.a raw input) when it's a setting placed on the mouse category of the input settings. Seems like this setting is messing up with tablet input and if that's intentional, then I guess renaming the setting back to raw input and not placing it in mouse category would clarify and settle things.
In my opinion, mouse settings and tablet settings should not have a setting where one would affect the other since they're completely different input devices. If that can't be followed, then at least have the naming make sense where both devices can agree on.
Screenshots or videos
No response
Version
2024.131.0
Logs
compressed-logs.zip
The text was updated successfully, but these errors were encountered: