Steam for Linux > Dyskusje ogólne > Szczegóły tematu
DIRT 12 Lis, 2013 - 7:05
Matching windows mouse in linux
Linux seems to be more sensitive than windows. It turns out you cant adjust your base sensitivity in linux only the acceleration. (xorg.conf doesn’t work with all mice.)
I got around this by purchasing a roccat kone pure that lets you change the dpi to any oddball number you want.
Other people who cant change dpi this might be a problem so a fix is be needed. Serious gamers are really picky about their cm/360 movement.

Any one have any info on windows mouse acceleration? I heard it moves 6 pixels then it will accelerate but I don't know how much. Also would like to know base sensitivity in windoes.

Also found my self changing the sensitivity from 3.5 to 2.5 in valve games to get close to the sensitivity I had in windows. windows was using a razer deathadder set to 900 dpi and linux was with a roccat set to 800 dpi. I'll take better measurements later computer is down atm.
Wyświetlanie 1-15 z 21 komentarzy
< >
Letalis Sonus 12 Lis, 2013 - 7:29 
Read the manpage of xinput and use it to check the actually available properties.
There's lots of stuff like constant/adaptive deceleration, velocity scaling, a whole transformation matrix and several acceleration profiles (check ), most of them are not available through any configuration GUI.
Ostatnio edytowany przez: Letalis Sonus; 12 Lis, 2013 - 7:29
DIRT 12 Lis, 2013 - 7:44 
Ok I didn’t see that velocity scale or deacceleration. It says using velocity scale with constant deacceleration might cause problems though.
And yeah there needs to be a gui. People moving to linux for gaming wont want to edit text files or use the command line.
The people I play with say that is one of the top reasons they wont use linux.

Just one question. What happens when people switch to wayland?
Ostatnio edytowany przez: DIRT; 12 Lis, 2013 - 7:47
LOLCAT 12 Lis, 2013 - 12:53 
Serious gamers are really picky about their cm/360 movement.
A nice fix would be returning to play games for fun.
blackout24 12 Lis, 2013 - 12:58 
Serious gamers are really picky about their cm/360 movement.
A nice fix would be returning to play games for fun.

For some people competitive playing is fun and requires proper configuration and hardware.
Ostatnio edytowany przez: blackout24; 12 Lis, 2013 - 12:58
|Pro Kittens| Medic Plz 12 Lis, 2013 - 15:01 
For me, the best settings (true, 1:1 raw input) is best achieved in KDE with 1.0x acceleration, at 1600 DPI on a Roccat Kova. Super accurate.
UraniumDeer 12 Lis, 2013 - 16:57 
Just one question. What happens when people switch to wayland?
If you're asking about input:
I'd say that it depends entirely on the Wayland compositor/displayserver abilities vs. the distros interface.
I just read that someone proposed to make a common library for input handling, based on Weston, that people could optionally use when creating a Wayland displayserver/compositor.

If you're asking in general:
The first few years, while Wayland compositors gains ground, you'll have a bunch of software using XWayland, which is one 'fullscreen' X-server instance per XWayland surface. So running a lot of software that has no Wayland support, will require more of your computer than an X-server (+ compositor) requires today. It should still result in 'perfect frames' and less inputlag than X-server has had (a lot of the changes done to X-server while preparing for XWayland, has afaik, removed a lot of roundtrips in the current, and upcomming version of X-server). Running only Wayland software though, should result in a more smooth user experience, and use less system resources. Check out videos on youtube with RPi running X-server, and Wayland.
Other than running some software in XWayland compatibility-mode, a little chaos, some failed Wayland compositor attempts and stuff like that, there shouldn't be that much difference, other than hopefully more efficiency, and 'perfect frames'.
DIRT 13 Lis, 2013 - 18:22 
I didn't notice an input lag too much. The input lag I do notice is form double/tripple buffering where the video card renders 3 frames ahead.

I had a neat fix for this when there was no native steam. I would disable vsync in the game then tell kwin to use vertical sync. It got rid of all the screen tearing and the responsiveness was about the same as with having vsync off.
Native steam games don't seem to want to do that for me they just tear.

Im not good at programing otherwise id start working on a gui. QT interfaces are easy but I dont know how to make the interface actually do something.

for the 1:1 with 1600 dpi. everyone likes different sensitivity. I was pretty good with the default windows xp mouse settings and a 900 dpi mouse. I haven't found any info on the windows mouse acceleration and I wish I could mimic that in linux.
I use to not have to think about aiming at all and still have better accuracy than 95% of players but now im a total noob.
DIRT 14 Lis, 2013 - 8:43
Ok looks like they will have a common input library. Wonder if its going to be like xorg where there is like 3 input libraries as stuff developes they keep old libraries around.
Ghost 16 Lis, 2013 - 4:40 
While you don't state which distro you use I had similar issues when I started dual booting Ubuntu 12.04 LTS with Windows 7.

In Windows you can easily disable mouse acceleration by going to mouse properties and then pointer options. Pointer speed should be on the 6th notch and enhance pointer percision should be unchecked. I was using a Steelseries Sensei (with built-in ARM processor). I was disappointed by the lack of Linux support for Steelseries Engine, but the mouse worked fine although default xinput / ubuntu settings have way too much acceleration.

I solved this issue through the terminal by entering the following commands: (you will have to see your device's ID (mine was 8) and 268 was the accel property yours may be different so read through until you see accel and input that number and set it to -1)

xinput list-props 8
xinput set-prop 8 268 -1

more info here:
Ostatnio edytowany przez: Ghost; 13 Gru, 2014 - 11:46
DIRT 27 Sty, 2014 - 12:31 
I found out what was wrong with my sensitivity. It turned out my TV has around a 1/4 second delay in the video. Its barely noticeable. (to bad they didn’t post that in the specs) It took me forever to realize this because for me aiming just happens. I try not to think to hard about aiming.
So this wasn’t even a sensitivity issue to start with. Very handy info anyways. I might make a GUI written in QT for tweaking mouse settings. Because, its 2014. Why are we still editing text files for a desktop environment?
Ostatnio edytowany przez: DIRT; 27 Sty, 2014 - 12:32
Lord Battlesheep 27 Sty, 2014 - 14:25 
So this wasn’t even a sensitivity issue to start with. Very handy info anyways. I might make a GUI written in QT for tweaking mouse settings. Because, its 2014. Why are we still editing text files for a desktop environment?
Kone Pure has a GTK(?) GUI -- konepureconfig (in roccat-tools package). Two things need to be adjusted in configs: sound server (Pulse default, or ALSA), and angle snapping needs a script writing 0x86 into register 0x42 (works from GUI too, though, but doesn't save it between sessions).
Kone Pure can change profiles, DPI and sensitivity on the fly, it even can talk when chages it. Be sure to start "roccateventhandler" (user-side driver) first.
Mouse acceleration on X can be turned off completely, say, in xorg.conf:
Section "InputClass"
Identifier "KoneMouse"
MatchIsPointer "true"
MatchProduct "ROCCAT ROCCAT Kone Pure"
Option "AccelerationProfile" "-1"
Option "AccelerationScheme" "none"
Option "SendCoreEvents" "true"
Option "SendDragEvents" "true"
Ostatnio edytowany przez: Lord Battlesheep; 27 Sty, 2014 - 15:38
DIRT 27 Sty, 2014 - 15:12 
so basically editing text files.
Lord Battlesheep 27 Sty, 2014 - 15:29 
so basically editing text files.
Hmm.... You mean, you want a QT GUI to manage xorg.conf??
Anyway, it'll be good if you make another GUI for Roccat.
DIRT 27 Sty, 2014 - 16:39 
There seems to not be a way of changing the base sensitivity in linux with a gui, only the acceleration. That is the problem.
I dont even have an xorg.conf so Im assuming that the mouse settings might be somewhere else?
DIRT 27 Sty, 2014 - 16:51 
Found out xorg is device specific. probably not the best for a universal sensitivity setting
Wyświetlanie 1-15 z 21 komentarzy
< >
Na stronę: 15 30 50