why shouldn't you? its not like mouse rate and display refresh are related

according to steelseries it does:

SteelSeries ExactRate allows you to define a limit to this data and you can allow it to correspond to your in-game frame rate and monitor refresh rate for a homogenous, synchronous and consistently smooth mousing experience. Set this value to correspond to the lowest value in either your in-game frame rate or monitor refresh rate.

Example: If you utilize a screen with 60Hz, you should try setting this at 960Hz (or something else that is dividable by 60). With this setting your report rate will be synchronized to the refresh rate of your screen, improving consistency and smoothness of your movements.

hmm, sounds like advertisement to me
anyway, one shouldn't set lower com_maxfps, because it limits packets sent (or thats how it is in q3 iirc)

mouse sensitivity is affected by monitor refresh rate cause of number of pics that are displayed on the screen...the more frames u have the slower/smoother sensitivity may feel and reversed.Its no advertising trick its true just not the way steelseries say it is

smells liek bull

Read below. I recalled that something like that is true for Q3. From what I recall com_maxfps set to 125 actually is 123? Is that true?

no idea

It's even divisors of 1000, so it's 125 exactly. In Q3 networking and the display are linked. Maybe someday there'll be a client where they are separated (doesn't fuhquake do this?).

Only think I remember like this was players setting com_maxfps "120" to be the same as r_displayrefresh

...... I've no idea if that's even relevant to this thread \:D/

Wrong, according to arQon the 125fps setting is more important netcode-input-wise than the slight tearing it generates vs a full synced 120fps/120hz setup IIRC.

hz=fps is not a good idea :/

How come? I have 75 hz screen right now and 75 com_maxfps (I can't sustain a perfect 125 in big battles on Siberia for example). Is that bad?

i forgot the technical explanation of it but this has been talked through multiple times on esr. just set hz = fps and you will see some graphical glitches ('the line'). if you set fps (slightly) > hz there won't be any and the excessive frames will not be displayed or in any way cause problems.

that's why a lot of people use 125fps/120hz (q3) and 77fps/75hz (qw) to get a smooth game without vsync.

I have a razer death adder, and for me when I lower the r_displayrefresh the sensitivity increases slightly, and increaseing my r_displayrefresh the sensitivity decreases a bit. I have measured the distance my mouse needs to travel on the pad to make a 360 degree roatation in game on high refresh rates and lowe refresh rates, with low refresh rates the distance travelled on the mouse pad is a bit less and on high refresh rates a bit more.
I don't think either of them is the better or worse, just know that changing your refresh rate slighlty adjusts your sensitivity.

anymore info on this stuff?

This is a good start. Dont know how much it apply to QL tho.

Thank you!

displayrefresh/hz changes the sensitivity (but only slightly). Thats why cheese s mousefix has different .reg files in it.

See also: ...note that Windows scales the Y coordinates by the computer screen's refresh rate, typically 60Hz to 120Hz.

And: ...Aside from the *minute* imperfections in the acceleration curve, the Hz scaling effect, explained in the previous paragraph, causes the users sensitivity to scale in accordance with the screen's refresh rate. This means that cursor outputs using the CPL Mousfix are rarely, if ever, perfect 1-to-1 representations of the actual mouse's outputs. The imperfections in the line, in theory, cause inconsistant mouse movement, but they are so small they aren't noticable by anyone--thus the CPL mousefix does a perfectly decent job of eliminating all mouse acceleration.

Taken from cheesefix readme.txt

http://www.microsoft.com/whdc/archive/pointer-bal.mspx
for further information

does it still makes sense using the hz. regfiles, when playing with "in_mouse 2" ?

If you use anirs accelfix, it does not make sense at all.

Don t really know about in_mouse 2, because I only used it in q3 days. However, if there would be any affect it should be really marginal.

no, just using wcafix. i tested cheese's reg fixes on "in_mouse 1" a while back. they felt diffrent.
sure i could just try it for myself. but im not even sure which hz files to use, as im playing on 75hz (1680x1050, samsung t220)
i read somewhere on tft screens its not really 75hz. its actually 72. ?
should i use 75hz or 72hz reg file?

75

this stuff doesn't make sense at all.. my pc can easily run at 125 fps yet my monitor is running at 75hz and if i set my fps above 75 i get terrible stuttering... it's like i'm playingon 15fps instead of 125... The only thing i've noticed from using 75fps is the fact my mouse has some kind of lag but you can just about get past that.. unless anyone can explain why a powerful pc can't run at 125fps with an lcd monitor :(