1 WINE / PROTON - RAW MOUSE INPUT
3 [linux_gaming] 2018-10-09_08-00
5 o Reference: 2018-10-09_08-00_Wine___Proton_-_Raw_Mou
6 o News link: https://www.reddit.com/r/linux_gaming/comments/9l4iyd/wine_proton_raw_mouse_input/
10 I am struggling to find 1:1 parity with mouse input between
11 Linux and Windows for games run via Proton/Wine. For games
12 with native builds, I am able to achieve perfect 1:1 mapping.
18 sensitivity 2.2 @ 800 dpi == ~23.7cm/360
20 ezquake uses "Raw Input" in Windows and "EVDEV mouse" in
21 Linux. My sensitivity is exactly the same in both OS.
23 I was able to replicate this exact sensitivity in CS:GO, same
26 Wine example (via Steam Play (Proton 3.7-7))
30 sensitivity 2.2 @ 800 dpi == way larger than my mousepad
32 I found that I could get close to 23.7cm/360 with a
35 in_mouse 2 in_MouseMode win32(raw)
37 My hunch is that by default, Wine is not reading the raw input
38 and is instead using X11 mouse in some way and then telling
39 the windows game that it is raw (when it is in fact not). Is
40 this a setting that can be changed?
42 Also worth nothing - I have disabled acceleration via xorg
43 config: Section "InputClass"
49 Option "AccelerationProfile" "-1"
51 Option "AccelerationScheme" "none"
53 Option "AccelSpeed" "-1"
58 ** some_random_guy_5345
59 I play Quake Live in WINE and I'm having no issues with this
60 profile (1:1 parity with windows):
61 /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
67 Option "AccelProfile" "flat"
70 My hunch is that by default, Wine is not reading the raw input
71 and is instead using X11 mouse in some way and then telling the
72 windows game that it is raw (when it is in fact not). Is this a
73 setting that can be changed?
74 Why would this matter? Doesn't your profile disable mouse
75 acceleration (and presumably use 1:1 input)?
78 I don't think X11 pointer movement is identical to raw input
79 even without acceleration. [1]libinput tries to do
80 normalization for high dpi mice down to 1000 dpi. I'm not
81 sure if "one mickey = one pixel" is even true for 1000 dpi
83 EDIT: The desktop environment might also override Xorg's
84 libinput settings at runtime. For Plasma desktop, I had to
85 enable the "flat" profile in the mouse settings gui because
86 my xorg.conf.d file stopped working after some update. Of
87 note here is that that mouse gui doesn't have a perfect
88 middle setting for the sensitivity slider (called
89 acceleration here), so I had to set
90 XLbInptPointerAcceleration=0 in "~/.config/kcminputrc". The
91 one left of the middle would result in a value of -0.11 and
92 the one right of the middle is 0.11.
98 https://wayland.freedesktop.org/libinput/doc/latest/normaliza-
99 tion-of-relative-motion.html#motion-normalization
103 I don't suspect it does matter - but I thought sharing it
104 would cut off the default recommendation to disable
106 This is why I am getting 1:1 for native apps - issue is that
107 Wine seems to do something else with mouse input, and I
108 cannot find any details on configuration options on that
112 Native apps that have raw input (CS:GO) will have 1:1
113 tracking even if you leave non-linear pointer acceleration
116 ** some_random_guy_5345
117 This is what I suspect is happening. The profile in the
118 OP probably isn't 1:1 tracking.
119 Native games use raw input whereas WINE probably
123 I wonder why Wine doesn't support it.
130 Just switched to your conf, and I now have perfect 1:1