Hi all, doing a survey of some sort , since I got new display,mouse and computer i've been playing around with different settings, and im just curious what the rest of you are using !


so please take your time and just fill out the form:

Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?):
Mousepad :
Sensitivity settings (cm/360 , settings in qw client, settings in windows) :
Operating system :
Ezquake or other client? version? :
cl_maxfps :
cl_earlypackets :
sys_highpriority :
Gameresolution ? 1920x1080 or other? etc :
FOV :
Monitor that you are using, and what refreshrate, using lightboost? :
m_yaw and m_pitch settings? :
in_mouse 1/2/3 ? :

if you have the time you could also upload a screenshot with how your qw looks like!, at work now but i'll upload my own later today, and I might add more questions later,
but thanks anyway for the feedback !

Improve your skill dude, don't focus on hardware. One day, when you reach my level you will understand why.

Greetings,
pro.

9 cm / 380
cl_maxfps 0 (between 500 and 1000 fps)
xornet mouse 3600 dpi and 1000 hz
steelseries maxi pad
640x480 resolution
20 crt 150hz
fakeshaft 2
viewheight -7
lego quake
windows xp
amd sempron 2.8 and 2gb ram

Mouse : Razer abyssus, 1000hz, 450dpi, no drivers of course
Mousepad : Steelseries Qck+
Sensitivity settings : around 15 cm/360
Operating system : Win7
Ezquake or other client? version? : lastest Ezquake nightly build
cl_maxfps : 616
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution ? 1920x1080 or other? etc : 800*600
FOV : 115
Monitor that you are using, and what refreshrate, using lightboost? : Old Iiyama 120hz
m_yaw and m_pitch settings? : m_yaw 0.022 m_pitch 0.015
in_mouse : 3
Also I try not to pick dm2 during tournaments.

(Edited 2013-12-11, 15:42)

Mouse: mx518
Umpf, seems to run at 125hz, gonna see if i can fix dat.
Got it fixed, 500hz now
Mousepad : Raptor-Gaming P9 DKT E
Sensitivity settings : roughly 10cm/360, sensitivity: 5
Operating system : Linux, sometimes OpenBSD (mouse is not precise enough, everything else is fine there)
Ezquake or other client: jquake 0.3-dev built 4099 (dimman's client), fodquake 0.3 (with some changes) or 0.4 sometimes
cl_maxfps : 250
cl_earlypackets : 1 in jquake
Gameresolution ? 1920x1080
FOV : 110
Monitor: EIZO fg2421 @120hz, Turbo on (~lightboost)
m_yaw: 0.02
m_pitch: 0.02
in_mouse 1/2/3: 1 (2/3 don't exist neither in jquake nor fodquake, both use xinput2 i think

(Edited 2013-12-12, 07:52)

Mouse: wmo 1.1a with modified steelseries feet 400 dpi
Mousepad : zowie speed spawn pad gft speed
Sensitivity settings : 4cm 360
Operating system :xp
Ezquake or other client:ez
cl_maxfps :450
cl_earlypackets :
sys_highpriority : 1
Gameresolution ? 1300res
FOV : 90
Monitor: gdm fw900 24inch crt up to 2500 res playing at 140 hz
m_yaw: to lazy to look
m_pitch: to lazy to check
in_mouse 1/2/3: 2

Mouse: Logitech g400, 1000 hz, logitech drivers, 400dpi
Mousepad: Func 1030 sUrface Archetype
Sensitivity settings: ~20cm/360, 5 sensitivity ingame, standard notch in windows (no multiplier), no accel, 400dpi
Operating system: win7 64bit
Ezquake or other version: Ezquake ~ some stable build
cl_maxfps: 1155 (Renzo recommended it with 144hz, it's close to 144*x (refreshrate of monitor) and 77*x (physfps)
cl_earlypackets 1
sys_highpriority: default
Gameresolution: 1920x1080 144hz (conwidth 640 x 360 conheight)
FOV: 120
Monitor: Asus VG248QE, 144hz, no lightboost
m_yaw/m_pitch: 0.022 , 0.022
in_mouse: 3



/andeh

Mouse Microsoft Intellimouse 3.0 500hz
Pad Steelseries Qck Heavy
Sens QW 5.5 Windows 6/11 All mouseacceleration eliminated
OS Windows XP 32bit
Client Ezquake 2.2
Maxfps 308
Res 1920x1080 (640 conwidth x 360 conheight)
FOV 120
Monitor BenQ XL2420T 120hz
m_yaw/m_pitch 0.022
in_mouse 3

mouse: Microsoft Intellimouse Explorer 3.0, 500hz, with Hyperglide mouse skatez
mousepad: Roccat Taito mTw edition with edges peeling up
sensitivity settings: 14.84cm per 360 (sensitivity 7.0) - all mouse accel disabled
operating system: Linux
version: ezquake 2.1 stable, build 3331
cl_maxfps: 500 (for some reason feels better than 1001+)
cl_earlypackets: 1
sys_highpriority: does not exist in Linux
resolution: 1920x1080
FOV: 126.332001
monitor: Asus vg248qe, 144hz, no lightboost needed
m_yaw and m_pitch: default 0.022
in_mouse: 3



Edit: dunno why the bar is covering the red zero in the bottom right... it doesn't do that normally, so must be a glitch

Mouse: Logitech G400, 800dpi, 1000Hz
Mousepad : Thin cloth pad
Sensitivity settings : 6cm/360
Operating system : Windows 7
Client: ezQuake 2.2 stable
cl_maxfps : 770 for duel, 616 for 4on4
cl_earlypackets : 1
sys_highpriority : 0
Gameresolution ? 1680x1050
FOV : 108 (126 with widescreen mode enabled)
Monitor: Samsung rz2233 @ 120hz and no lightboost
m_yaw and m_pitch settings? : default (inverted
in_mouse: 3

Tsobo - You should really fix your maxfps instead of using 0. Figure out what the highest multiple of 77 that your FPS never drops below and set it to that. Try 616.

Andeh - with a Logitech G400 you should only ever use 800dpi or 3600dpi as they are the only dpi's that the mouse normally runs at. The other dpi's are interpolated and not as smooth. Try setting it to 800dpi which is apparently the best. You will need to exactly HALVE your mouse sensitivity.

I've experienced a shitton with this... 800 dpi and half sensitivity really doesn't feel as good as 400dpi. I believe Carapace uses 400dpi as well for the same reason (although with about double my sensitivity). I've experimented and I've tried so many different settings but this is the one that feels best, and 400dpi really haven't been an issue for me whatsoever. I know where you're coming from though as I've read about it as well and I talked to Renzo about it as well, but 400 just simply works better for me.

(Edited 2015-11-06, 17:32)

thanks dirtbox

thanks for all the answers so far, keep them coming!

i'll update with the settings i'm using at the moment :



Mouse (what mouse,hertz, using drivers or no drivers, dpi settings?): Logitech g400s @ 800 dpi 1000 hz with drivers (for trying out different hz/dpi settings easier)
Mousepad : allsop gigapad XL cloth mat
Sensitivity settings (cm/360 , settings in qw client, settings in windows) : about 20cm/360 sens 2 in qw 6/11 windows, all accel disabled
Operating system : win 7 64bit
Ezquake or other client? version? : ezquake stable
cl_maxfps : basically swapping between 616 and 1001 , 616 at the moment
cl_earlypackets : 1
sys_highpriority : 1
Gameresolution ? 1920x1080 or other? etc : 1920x1080
FOV : 120
Monitor that you are using, and what refreshrate, using lightboost? : asus vg248qe lightboost enabled
m_yaw and m_pitch settings? : 0.2 / 0.2
in_mouse 1/2/3 ? : 2 at the moment (for some reason works better for me than 3, which seems wrong but hey)


and screenshot of my qw :



( for full image )


thanks again for the replies !

also want to add a question:

what color on skins for enemy / teammate do you use ?

i have white mates yellow enemy !

kingpin - i use fluorescent green for enemy and maybe blue or white for teammates... cant remember... i only play 1on1

andeh - that is interesting... i only ever used 3600 and SoboL gave me some articles and proof about the benefit of 800 and even though i refused i eventually tried it and I had to increase my sensitivity to match and honestly once i gave it a shot it i could feel the better consistency of it... but if 400 works for you, no probs!

kingpin - is your asus monitor the 24" 144hz model? do you recommend it and also do you have to right lightboost for it to be good? lightboost is only at 120hz right?

yes thats the one, its really good without lightboost also, no overdrive artifacts at all basically, but after extensive testing theres no doubt that lightboost is better IMO, its as close to CRT as you can get, no motion blur no artifacts.

lightboost is max 120 hz (for now) so 144hz is faster but the motion is much, much clearer on 120hz lightboost = you aim better and play better, google blurbusters and read about lightboost, its SICK !

I really likr your cfg

How can you aim better when lightboost actually increases input lag, like that "turbo mode" on eizo does?

During my own testing, the "performance" that came with lightboost was negated by increased input lag, making normal 144Hz actually feel better.

Yeah, I'm the most un-technically minded person in the world. Only recently started playing semi-regularly again so never really thought about it.... Really need to learn what half the s*** I have actually means/does! lol :-)

Mouse: Some 4 button USB jobby I got for $15 in the shop down the street (Its made by Microsoft if that helps lol)
Mousepad : the slipmat of one of my DJ decks! (Does the trick! )
Monitor: Some 16" Philips flat screen I got of the next door neighbor when they moved out.
Sensitivity settings: '4.000000' according to my cfg (what ever that means, but feels comfortable). Accel disabled.
Operating system : Vista
Client: ezQuake 2.1
cl_maxfps : never really checked.
Gameresolution: 640 x 480
FOV : 130

Yeah, pretty shoddy set up to be honest... But I have whiskey so its all ok!! :-) lol

I see what you did there...

Nevermind lightboost does increase input lag by half a frame. But it probably is negated by the fact that it makes tracking whats going on with your eyes smoother.

there is known issues with input lag and lightboost on some systems and driver combinations, something about that you have to disable the 3d overhead processing from the computerside, and that is not default after enabling lightboost, or something like that (very vague I know, try to google lightboost + input lag )

and after playing around with settings and removing everything to do with 3D from nvidia drivers, I feel no input lag whatsoever , and I aim and play better now than with the CRT imo, probably a combination of bigger display, new mouse and rock solid fps ingame though..

lightboost is amazing IMO.

I agree. I don't know why Renzo would prefer -3ms with a blurrier picture than +3ms with a clearer picture. Maybe that extra half frame has decided his fate in multiple game situations.

Simply because it feels worse. And while you get clearer motion, the image looks worse because you are loosing control of your brightness setting, color settings and even overdrive settings (which becomes maxed out) and this causes inverse trailing caused by the overdrive overshoot.

It was the same with 2233rz -> xl2410t transition: xl2410t looks a lot worse because of overdrive overshoot trailing, but feels more responsive because the input lag is lower. With VG278HE the difference is not that big in QW even if it is highly noticeable using monitortests like those on testufo.com and other similar tests (pixperan, monitortest from flatpanels.dk).

Also, VG248QE is so much faster monitor that even with the inputlag increase of lightboost it would still be faster in terms of image processing lag as VG278HE is without.

You honestly think it feels worse in game? Or do you mean it feels worse outside of game. Because honestly I think 144hz or just 120hz no lightboost feels worse than lightboosted 120hz. Just because moving makes everything so fucking blurry.

At least Milton said that lightboost is much worse for Quake from his experience. I think I will wait for gsync support before I buy anything now.

The biggest problem is that it makes input feel laggier than normally, image quality issues in a game (this means only qw) would not be so important since qw doesn't look that good even with the better textures and/or extra graphics effects.

And in Quake the fullbright skins are so obviously visible that I think blurring is less of a harm than laggy feeling in input. In something like battlefield where it can be very difficult to detect enemies from the background, I can see why blurring could be a real issue.