for me , the simplest test was 144 hz no light boost, trying tracefree 40/60/80 and rocketjumping really fast around different maps, and 120 hz lightboost at 10% and doing the same, and the difference is clear as night and day for me, 144hz feels a tiny bit more responsive with the mouse, but theres huge blurring compared to the lightboost mode, where there is basically zero blur and no artifacts either,


hard to explain but its like in 144hz it takes a bit extra time (milliseconds) for the picture to "stabilize" but in lightboost its completely clear all the time, its like less brainlag in lightboost mode, even if the actual input delay is higher...


anyway theres no right or wrong here, its all about what you feel is the best for you I guess.


edit: you should try 1001 maxfps 1000hz mouse and lightboost at 10% , while making sure to disable everything with 3D/stereoscopic stuff from nvidia drivers, its so smooth it's insane, while when I put 616 fps , and rest same settings, there is slight tearing and slightly more sluggish mousefeeling, although in a way it helps aim almost because you have more control over you aim and movement, again hard to explain, but yeah

well at 144hz any tracefree setting I can still force the monitor to produce artifacts, on dm3 I found a real easy way, just jumping around the ring area while watching the ground, and in lightboost these artifacts completely 100% disappear ,

although im playing with gl_max_size 1 and this mode is very unforgiving regarding artifacts , while if i use textures , like lego quake, these artifacts are very hard to produce at 144 hz , and there are none in lightboost..


so if you are going to use 144hz i'd recommend using eyecandy or lego textures, not gl_max_size 1 or one-colored walls/floors) as in these modes its extremely hard to notice the artifacts....

I guess that's the thing. While it's obvious that a responsive mouse is beneficial, its less obvous if slight blurring really hurts your qw game. I mean you already know the maps inside out so there is nothing to see there really. As long as you can clearly see mates, enemies and items, I dont know if it hurts your game if the image is not 100% clear. In games like BF its another story because it's often quite difficult to spot things like a camo soldier in the forest.

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?): Logitech G400, the old revision with angle snapping
Mousepad : Ulti-mat breathe x4
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : sensitivity 44.44444, ~11cm/360
Operating system : Linux
Ezquake or other client? version? : Ezquake 2.2
cl_maxfps : 616
cl_earlypackets : 1
sys_highpriority : -
Gameresolution ? 1920x1080 or other? etc : 1920x1080
FOV : 137
Monitor that you are using, and what refreshrate, using lightboost? : Asus VG278H 120hz, no lightboost
m_yaw and m_pitch settings: 0.001
in_mouse 1/2/3 ? : 3

nice screenshot! , keep us updated with lightboost experimenting people! also milton , can you upload your enemyskin somewhere? would like to try it !

PS : thats an interesting sens/m_yaw/pitch combination, any idea behind it?

I have a roccat pyra mouse with paint spots, a roccat sense mousepad with paint dots, an ultra cheap sometimes partly (if at all) working headphone and an adorable cute laptopt with an orange line around the keys. I use a seperate keyboard for Quake because I hammer on the keys and not want to destroy my laptop.

Also, forgot to tell, my Quake dolls are white with coloured socks and hats. Same colours as is used in the tab view. So that I know who I'm shooting.

And of course BuurVrouw, a wee glass of wine... Essential kit for all serious FFA aficionados! lol

Seeing which direction the enemy player model is moving in quakeworld more clearly is always beneficial.

Well, even with my first gen 120hz display, I don't feel I have any trouble seeing which way opponents move. But I would have to see lightboost in action to see if it matters. One thing's for sure though, any delay in controls is disastrous. That's why vsync is such a failure for gaming.

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?):Roccat Savu, no drivers, 4000dpi, 1000hz and Logitech G13 for left hand.
Mousepad : Razer Goliathus Speed
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : sensitivity 1.68, ~10cm/360
Operating system : Win7
Ezquake or other client? version? : Ezquake latest
cl_maxfps : 1155
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution : 1920x1080, con: 640x360
FOV : 135
Monitor that you are using, and what refreshrate, using lightboost? : Asus VG278HE 144hz, no lightboost
m_yaw and m_pitch settings: 0.022 (default)
in_mouse : 3

I had quite much testing with lightboost and asked some setting / tweaking help from KP. Used http://www.blurbusters.com/zero-motion-blur/lightboost/ guide, reinstalled drivers, removed 3d vision etc. And I have to say that with 120hz and lightboost 10% enabled it is not smooth at all. I don't know what it is but somehow really hard to see anything when moving fast. It can be better than my old 120hz but 144hz / no lightboost is just at own level. Back in the days I started with 60hz LCD monitor, then upgraded to 75, 120 and now 144hz. The previous monitor was ViewSonicVX2268wm and the difference between ViewSonic and Asus 278HE is quite the same as 75hz compared to 120hz. So all I have to say that this new monitor is really good!



(Edited 2013-12-18, 18:59)

O_O

Actually, a woohoo glass of beer.
But it helps killing in FFA yes.

Usually go for a wee Jim Beam (or 2) myself lol

Cheers!

Long time since I started ze quake

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?): Steelseries Sensei RAW, 1000 hz, drivers, 900 CPI
Mousepad : Qpad CT 4 mm Large
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : 3.6 in game/~22 cm
Operating system : Win 7 64
Ezquake or other client? version? : Ezquake 2.2
cl_maxfps : 600
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution ? 1920x1080 or other? etc : 1920x1080 conwidth 320 conheight 240
FOV : 125
Monitor that you are using, and what refreshrate, using lightboost? : Samsung SA950 120 Hz
m_yaw and m_pitch settings? : 0.022/0.042
in_mouse 1/2/3 ? : 1

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?): Zowie EC1 black, 1000 HZ, 1000 DPI, no drivers
Mousepad : Zowie Spawn GTF Speed
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : cm/360 approx. 13 cm (it's about 20% lowet for shaft), 0.27 ingame, windows default
Operating system : Win7 64 bit
Ezquake or other client? version? : EZQuake some nightly build
cl_maxfps : 1001
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution ? 1920x1080 or other? etc : 640x480, con 320x240
FOV : 113
Monitor that you are using, and what refreshrate, using lightboost? : CRT IIyama Vision Master 512, 22 inch, 200 Hz - but I'm considering a new 144 hz Asus or that new Eizo 240 HZ
m_yaw and m_pitch settings? : yaw 0.21, pitch 0.22
in_mouse 1/2/3 ? : 3

How does that monitor not burn up lol! I'd want to try playing on a real 200hz monitor before I die :-) (remember eizo 240hz aren't actually 200 real hz)

It displays 200 Hz in 640x480 and 800x600 - therefore, I dont use higher resolutions . The colours are already washed out but it's still incredibly smooth. Ofc, I use it only for QW.

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?): Logitech g400, 1000 HZ, 800 DPI, no drivers
Mousepad : Razer Goliathus Control
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : cm/360 ~20 cm, 0.235 ingame, windows default
Operating system : Win7 64 bit
Ezquake or other client? version? : EZQuake 2.1 stable
cl_maxfps : 616
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution ? 1920x1080 or other? etc : 1920x1080, con 640x360
FOV : 125.461342
Monitor that you are using, and what refreshrate, using lightboost? : BenQ XL2410T 120hz
m_yaw and m_pitch settings? : yaw 0.25, pitch -0.245
in_mouse: 3

LOL, I love you er <3

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?): Razer Deathadder, Drivers, 500DPI/500HZ
Mousepad: Zowie GT-F Speed
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : sensitivity 5.8 ~16cm/360, Windows driver default settings
Operating system : Win 7
Ezquake or other client? version? : Ezquake 2.2
cl_maxfps : 462
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution : 1920x1080, con: 960x540
FOV : 120
Monitor that you are using, and what refreshrate, using lightboost? : Asus VG278HE 144hz, no lightboost
m_yaw and m_pitch settings: 0.022 (default)
in_mouse : 3

Hey, just a quick question:

What exactly are the differences between for example 4000 DPI / 1 ingame and 400 DPI / 10 ingame? I was playing on 3000/1 for now, but here in this thread almost everyone uses quite bigger ingame sensitivity options.

With sensitivity 1 and 4000 dpi the mouse cursor minimum movement is 1/10th of what it would be with sensitivity 1 and 400dpi making it a lot more accurate. In qw this does not necessarily mean better playability though, since something like 800-1600dpi will feel "more responsive" than 4000dpi for example.

Thanks for clearing that up!

I have read some discussions on overclock.net forum considering mouse sensors in general. There seem to be some true mouse experts there with great knowledge of mouse sensors and the software used to operate the sensors which also have great impact on the actual performance.

Based on these discussions I have come to following conclusions:

The trend with these "gaming mice" the past couple of years (as it is with most of the consumer electronics really, unfortunately) is that the actual knowledge of the consumers is next to non-existent and the marketing teams are the actual thriving force behind deciding what properties and features are "needed" by the end users.
What that means is that we get these 12 000 DPI mice with led lights that make absolutely no sense when it comes to actual performance and suitability for gaming. But it is the big numbers that sell apparently, instead of the real-life and in-game performance of the sensor. In other words; the movement of your hand rightfully registered by the sensor and processed correctly and send to your computer by the MCU board on the mouse, which contains the software(firmware) of the mouse.
I have understood that the best mice sensor-wise, if you want more than 400dpi (and you should want if you have a sensitivity higher than let us say 20cm for 360 degrees in-game) are Razer Abyssus and the 3500-dpi versions of Razer Deathadder.
The problem with these 12 000 DPI mice is that in order to get the pointless and insanely high (unless you use some 3x 4k-monitor setup) DPIs to work in a way that the tracking is not all over the place, they have to add something called smoothing to software operating the sensor. Think of this as m_filter 1 sort of (not exactly the same thing, but close). This same smoothing algorithm is then used even when selecting the lower DPI values.
Also different mice have different native DPI values which you should prefer if you want optimal performance. You can try googling your mouse + native dpi.

So what is the best DPI to use with qw?
This of course depends on your personal preferences and the mouse you have. I personally like to think that using the lowest native DPI which doesn´t skip too many pixels with single count on your monitor is close to optimal*. I also don´t believe that there is any special advantages gained using 1:1 pixel/DPI ratio in game (there is a calculator for that somewhere on internets).
* you can test this by moving your mouse around as slowly as you ever can in qw on idle server, and changing sensitivity to lower to see which is the smoothest you can get and compare that to the settings you use normally.
Now I know there are several very good players that use settings that don´t fill these requirements so to speak, so understand that in the end it all comes down to what you are used to.

If you need guidance in your path to the optimal settings in the game of quakeworld, feel free to bug me on IRC.

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?):
Steelseries Rival, had DeathAdder 2013 before that. Really like both mices, but I like Rival's shape better. Sensor-wise both are great. 1800 DPI/1000 Hz/SS driver
Mousepad : QCK Heavy
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : ~10,5cm/360, 2.2 sens in qw. Windows 6/11.
Operating system : Win7
Ezquake or other client? version? : ezquake 2.2
cl_maxfps : 1001
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution ? 1920x1080 or other? etc : 1680x1050
FOV : 125
Monitor that you are using, and what refreshrate, using lightboost? : Samsung 2233rz, 120hz, doesn't have lightboost.
m_yaw and m_pitch settings? : default
in_mouse 1/2/3 ? : 3

Mouse: Logitech G400, with Logitech drivers, 1000 Hz, 800 dpi
Mousepad: QPad
Sensitivity: ca. 12cm/360, m_yaw 0.038, m_pitch -0.030, sensitivity 2.3 ... Windows settings? What settings?
System: Win 7 running on Macbook Pro (yes)
Client: Ezquake 2.2
Gameresolution: 1440x900
Monitor: Macbook Pro, 60 Hz
cl_maxfps: 308
sys_highpriority: -1
fov: 120
in_mouse: 3
cl_earlypackets: Not in my config. Seems to be set to 1 by default when I checked at foppa?

BTW: Feel free to suggest improvements! 3600 dpi, would that be any point? Windows mouse settings, what's there to do? (Pointer precision is off, btw.)

Mouse : Zowie EC2 eVo (450dpi, 1000hz)
Mousepad: Zowie GT-F Speed
Sensitivity settings : 16,58cm/360°, 5.969 in game, 6/11 win
Operating system : Win 7 64bits
Ezquake or other client? version? : Ezquake 2.2 stable
cl_maxfps : 616
cl_earlypackets : 1
sys_highpriority : 1
Gameresolution : 1680x1050 , con 560x350
FOV : 125
Monitor that you are using, and what refreshrate, using lightboost? : 2233rz Samsung @120hz
m_yaw and m_pitch settings: (default)
in_mouse : 3

I was wondering the same thing about the yaw/pitch settings... as far I know, Bulat uses 1 bor both.