Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proton 5.0-5 High Polling Rate Fix = non sequitur, please report 1000 Hz mice bugs #3700

Open
ghost opened this issue Mar 28, 2020 · 7 comments

Comments

@ghost
Copy link

ghost commented Mar 28, 2020

The change mentioned as the fix to regression for high polling rate I can only guess fixed somethings but made some things irreparably worse https://github.com/ValveSoftware/Proton/wiki/Changelog#50-3 I'm surprised only I'm reporting on it. If anyone notices similar issues using a 1000 Hz pro-gamer mouse polling rate please give a response here.

I play a game using OpenGL code that is outfitted with mouse input: DirectInput API, Win32 (with cursor ballistics), and Win32 (Raw Input excludes all Window Cursor accels).

Standard practice is to use the Win32(Raw) to negate all accels or simply use the Win32 input assuming accel should also be off. DirectInput works noticeably fine too.

On 125 Hz mouse things seem normal as on 4.11 branch (I've tested using a Microsoft Wheel Mouse). The moment you use 1000 Hz pro-gamer mouse you get treated to something awful. Maybe its the mesa version 20.0 but I doubt it because the 4.11 branch works fine.

1000 Hz a negative acceleration is deeply ingrained in my game. Accel is off on the OS-level. Raw input should negate any accel coming from the Wine environment. No... the slower I move my mouse hand the more accurate the sensitivity is to how it should be but if I move my hand very fast my distance traveled is 1/3rd as much.

In addition: the overall sensitivity in the game is now 1.80-1.84 times slower. This game uses same sensitivity as many other games (similar formula for 360 degrees) and it's clear what the original speed should be.

I'm not too optimistic if this will be fixed. I'm using 4.11 branch for now and praying it doesn't get messed up either. It's really not a surprise for me because historically even when Loki games was porting Linux titles over, many had some kind of acceleration glitches for 4-5 years before a fix was done. I don't understand why no one else is seeing this. My Logitech mouse is quite popular. Many people using Mesa 20.0, and OpenGL many games running on.

I'm hoping more people can chime in and give a penny.

@matyat
Copy link

matyat commented Mar 29, 2020

I'm using a corsair m95. And yeah can confirm, mouse response in 5.0-5 is weird.

@ghost

This comment has been minimized.

@aeikum
Copy link
Collaborator

aeikum commented Mar 30, 2020

@username2222232 What model mouse are you having the problem with?

@aeikum
Copy link
Collaborator

aeikum commented Mar 30, 2020

@username2222232 Also what specific game(s) are you seeing this issue in?

@aeikum
Copy link
Collaborator

aeikum commented Mar 30, 2020

More info here, #3685

@duud
Copy link

duud commented Mar 31, 2020

In addition - the recent stem client update worsened the mouse responsiveness for me in Quake Champions - despite using a custom dinpu8 implementation which read the mouse input directly using kernels evdev interface. Probably because of your gameoverlayrenderer implementation.

Please put more effort into input and output latency.

@Xinayder
Copy link

Xinayder commented Apr 6, 2020

I've just downloaded Neverwinter and tried it with Proton 5.0-5 on Steam. I had input lag inside the game, I moved my mouse around and it seemed that it had about 100-120ms delay. Clicking the UI was also laggy, sometimes I had to click twice to confirm an action.

I have a Logitech G203 at 1000Hz polling rate, switching to 500Hz via Piper reduced the input lag, though it was still visible when moving my mouse too fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants