protonscr

Quake Live mouse lags and inverse-accel (negative accel) 5.0+

protonclosed appid 282440
ValveSoftware/Proton#3685 · opened 2020-03-25 by ghost · updated 2020-04-11 · 5 comments · github · game page · search this game
?ghost 2020-03-25 github

Compatibility Report

  • Name of the game with compatibility issues: Quake Live
  • Steam AppID of the game: 282440

System Information

  • GPU: Intel HD Graphics 530
  • Driver/LLVM version: Mesa 19.2.8
  • Kernel version: 5.3.0-42
  • Link to full system information report as Gist: (private)
  • Proton version: 5.0

I confirm:

  • [X] that I haven't found an existing compatibility report for this game.
  • [X] that I have checked whether there are updates for my system available.

Symptoms

Same issue described as in the following ticket [#3529 (comment)](https://github.com/ValveSoftware/Proton/issues/3529#issuecomment-587539290) for Doom 2016 but for Quake Live.
Mouse sensitivity is registering different than on the Proton 4.0 branch.
[Edit: The default sensitivity and the feeling of it is overall 2x slower than the 4.0 branch and how the sensitivity should be. In addition to the inverse accel which I will mention below, the actual sens. is a lot slower in the game (2x).]

If you move the mouse quickly even with all acceleration parameters off and using raw input it will go a shorter distance than if you slowly move the mouse the same distance. Moving the mouse on the mat slowly results in a similar sensitivity like on the 4.0 branch and also makes it go twice as far in the game (in terms of 360's).

It's like some kind of reverse (negative accel) effect is going on in the game. Slow movements make the mouse travel further in the game and super fast one's are abrupt and short (for same distance).

I know this is a Proton bug b/c if I revert to the 4.0 branch the Quake Live sensitivity is not impacted by speed of my mouse movement as well it also matches a different game (which uses the same code = Quake III Arena, which I am playing natively on Linux outside of Steam).

Reproduction

Use either Ubuntu 19.10 or the Daily branch of 20.04. Move the mouse slowly in Proton 5.0 for a set distance. Then move the mouse very fast over this same distance. Even with all OS acceleration turned off and the mouse will be two very different 360 degree turns in the game. Fast will give you ~ 2.5x less of a 360. Slowly moving the mouse will give you 2.5x more 360. Distance should be ==

Kkisak-valve maintainer 2020-03-25 github

Hello @username2222232, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/3406#issuecomment-603815301.

Wwfstuff 2020-03-26 github

Hi, I can't reproduce it. I'm running Quake Live with proton 5.0.5 and Ubuntu 19.04. Mouse sensitivity seems the same as in Proton 4.x
Do you use mouse acceleration in Quake Live? I'm not using any mouse acceleration in game and in Ubuntu at all.
I'm planning to update my Ubuntu installation the next weeks. Will check after the update if it happens for me with 19.10 or 20.04.

Wwfstuff 2020-03-26 github

I'm using a Razer Abyssus 2014 which seems to have 1000Hz polling rate. In my config "in_mouse" is set to "2"

Wwfstuff 2020-03-26 github

I had a short research and it seems I set in_mouse to 2 for some good reason in the past ;) Perhaps you could try in_mouse 2 and see if there is still some negative acceleration. Of course you'll need to adjust the sensitivity, too.

Some quotes from my research:

New 'raw device' input mode. Set in_mouse 2 to bypass DirectInput and talk to your mouse device directly. We have seen bad interference from various software, and in general you might get more reliable / better quality mouse input with in_mouse 2.

-1 - Windows cursor input, subject to cursor ballistics
0 - No mouse input
1 - Dinput (direct input)
2 - WM_INPUT (raw)

Wwfstuff 2020-03-26 github

Seems to cap at 460 for me

Proton versions

Upstream links