-
Notifications
You must be signed in to change notification settings - Fork 1k
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
DOOM (379720) mouse issues! #4464
Comments
You can compress logs, they usually compress very well. |
This seems to be a fairly common issue with the Wine layer, was supposed to be fixed but it still seems to happen under certain hardware/software combinations. I had the same issue with every game I played under Proton until I changed my mouse polling rate. Anything above 125hz would make FPS drops in any game, the longer I played the more it would drop, but only when the mouse moved. After changing it to 125hz I have no issues anymore and from the sounds of it you have a very similar issue, try changing the mouse poling rate to 125hz. |
as for the mouse, i already have it at a 125hz polling rate as i do not require more, and i managed to send the logs compressed in a zip file here |
Have you used evhz to check your mouse is definitely polling at 125hz? I only ask because I set my mouse to a lower polling rate but it didn't take effect, evhz still said polling between 500hz and 1000hz. I had to log into windows and run the mouse software and set it that way so it was saved to the mouse, rebooted back into Manjaro and it was working at 125hz. evhz is also available on the AUR. |
This is going to get merged into #3548 |
I also have big frame drops in the menu, is this suposed to be fixed? |
Lately after switching from Ubuntu to Manjaro, when trying to play DOOM i've encountered the issue, when if i do anything with the mouse in-game it suffers a horrible performance drop, even in menu when i just move the mouse, but if the mouse is static there aren't any problems and the game runs at a fine framerate. As i've said i didn't encounter that bug on Ubuntu, but i have it on Manjaro, will check at some point if it also happens on a vanilla Arch install on my secondary machine.
System Info:
GPU: GTX 960M
I wanted to attach the proton log but it ended up being a 26MB file, i assume it spams the error but i can't figure out what does it exactly mean. If the log would be required let me know of a way i could upload it...
The text was updated successfully, but these errors were encountered: