usually you want a max fps of 125 and refresh rate of 125

That's entirely preference now.

please explain. i just started playing again casually after a long hiatus

The only reason people went max fps 125 is because it was tied to the physics, and it was optimal for getting more speed and jump height. QL (and CPMA, even) unlatched the physics from the FPS, and so you can use whatever framerate/hz you want, so long as it's comfortable.

Netcode and FPS are tied together afaik so if you run 75 fps you only get 75 maxpackets. Ideally you run 125 fps 125 maxpackets and 125 Hz on a CRT but if you can't get 125 Hz then it doesn't matter, just don't put vsync on or you're limited to 75.

Besides, does 75 fps even exist? Valid values are 1000/x which means 125, 100, 90 and some more.

This has been the case for cpma and you still were wrong using non-even combos of 100 fps and 125 maxpackets or 125 fps and 100 maxpackets.

Unless arQon says otherwise, that is.

what if i use vysnc and have 120hz displayrefresh and the vsync locks the fps to 125?

good one

Don't you mean the fps will lock to your max HZ, because otherwise you will get an "out of sync" message.

cba to test with ql atm, but maxpackets and framerate should still be connected as pushpabon said. you can check udp packets/secs with perfmon to verify this.

Personally i find anything under 100hz/fps shuttery in q3

My monitor is a LCD it only goes to 75Hz, matching framerate with refresh rate give you a smoother game as far as I know.

Nop

Where are you playing QL btw?

tBone, we got a server from ISGAMING

Pings a bit bad for me, but I'm happy for you guys :)

It's entirely possible that r_displayrefresh isn't happy with your value of 75. I've had ql kick out some of my values and only refresh at something like 60 hz (although it looked really rather choppy).

There is even anecdotal evidence to suggest that it is _independent_ of refresh rate. I checked my monitor settings and they hadn't changed after a different r_displayrefresh value, but the game was obviously running at a much lower framerate. I can only adjust my refresh rate with a third party utility or with windows settings, although I am using a CRT.

Try different values of r_displayrefresh and see what results you get.

If u don't force vsync in drivers, make sure tripplebuffer is disabled.

btw, i experienced some very unstable mousefeeling a few weeks ago (in_mouse 2) .
i found out cl_packetdup "3" was the isue. console says default is "1", which should be fine. so better don't mess with netsettings to much.

try this with vsync off

1) r_displayrefresh 75
2) com_maxfps 77
3) the native resolution of your tft
4) m_filter 0
5) cg_fov whateveryouwant but i'd go for 90-110

since you never said what kind of stutter you're experiencing it could be punkbuster or your connection aswell.

Like m_filter has anything to do with running smooth or not. (Besides m_filter 1 rox - toxjq cypher e.g.!)

Yes it does.

If you have a really low polling rate your mouse movements will look choppy.

Also, with most current day mice and hardware, m_filter makes little to no difference input lag wise afaik.

All users preference, for as many pros using it, there are a lot of pros not using it.

But it does actually cause 'input lag'.

"But now in QL these values doesn't smooth out the graphics at all."

He talks about the graphics. m_filter doesn't have to do anything with graphics. Fact.

You said nothing about graphics yourself.

I simply stated that could in fact smooth things out, I didn't say it would smooth out graphics.

(m_filter is basically mouse smoothing)

I know. :)

m_filter 1 feels terrific. Even with 500hz or 1000hz mouserate i can still feel a diff, 1 will always do what i want, flick, aim etc, consistent as fuck. 0 will always have a bit of a weird feeling during some games.

you're becoming borderline ignore material

Elaborate.

if you read the op you'd realize he's a newb. what he believes to be 'unsmooth graphics' could be anything and is most likely pb related but could also be his obviously shit config.

who cares what cypher and toxic use(d). this guy needs basic recommendations not useless 'm_filter 1 r0x cuz cyph3r owNz ze w0rld' posts. besides that m_filter does change how 'smooth' your graphics appear to be - when you start moving your mouse around :)

No it does not. :) And I fail to see how I should see he's a noob just because he doesn't understand how shitty LCDs work. Being unsmooth is in the nature of LCDs.

if you don't see it i can't help you.

hint: http://www.esreality.com/?a=post&id=1779398#pid1779398

I is noob.
Could someone please explain to me why is vsync bad (other than it restricts your fps to 60)?
I have an ancient computer with GeForce4 64MB, a CRt with 60 Hz max refresh rate, so I'm using vsync (com_maxfps 60) and maxpackets 60.
amidoingitwrong?

as far as i remember its bugged, and cuttin ur fps to half :|

no, you're screwed anyway.

[+]'d for sincerety :-P

Read this (paragraph starting with vsync): http://www.witnessthis.co.za/2010/06/07/verti...explained/
and maybe this (talking about old CRTs and vsync): http://www.d-silence.com/feature.php?id=255
Yeah, and this: http://www.quakelive.com/forum/showthread.php?12964-Cons-of-vsync

PLUSES! FREE PLUSES! Git yer free pluses right here!
thanks mate

I have found the command to smooth out the tearing
"\cg_filter_Angles 1"

set that to "1" along with r_displayrefresh the same as your com_maxFPS and it's smoothed out to the max.

Thanks for the input guys.

cg_filter_angles "1" smoothed things out for me as well.

r_finish "1" helped too.

I'll keep playing with it to see if its just placebo though.

i find this post quite amusing, given that i know what filter_angles actually does.

i really wouldn't recommend it - you'd probably be horrified if you knew what it is actually doing.

Please tell us. =)

hint: use a larger value such as 300 to make the effect noticeable. :)

hahah, that's great.

screenie for lazy people, please?

wouldnt be able to see it on a screenshot

probably an already asked question, do com_maxfps and cg_maxpackets must be set to 125 or 120 with r_displayrefresh 120hz?

125 to all. Even if your monitor only refreshes 120 times a second the hardware still does the work for 125 frames (unless you enable vsync I think).

What the hell is the difference between this and m_filter?

subtle difference: filter_angles only affects the client-side camera - it doesnt affect your actual input or the view angles that determine where you are aiming.

with filter_angles on, the camera will be looking in a slightly different direction to that in which you are aiming.

toggled postprocessing yet?

if i don't set r_displayrefresh to 75 and com_maxfps to 75 my monitor looks like it's on a 40fps machine... I can easily get 125 fps but i can't set it that high, guess this lcd is just pap :[

i thought ppl with an lcd often set r_displayrefresh to 60, and com_maxfps and maxpackets on 120, does that not work? oO

Because the game is running in a browser it might never be like Quake 3 was (the smooth refresh rate).
But I've gotton used to it now. I went back on Quake 3 and the game was so smooth It didn't feel the same at all.

I leaving my settings now as deafult - it's still the same eitherway. Thanks for the suggestions "+'s"

I have a TFT LCD 1600x900 @ 60hz:

r_mode 19 //1600 x 900
r_aspectRatio 1 //16:9
com_maxfps 125
cl_maxpackets 125
cl_packetdup 1
r_displayrefresh 60
r_swapinterval 0

What does r_finish do (I can't find a description)? Also, my monitor supports 75hz at lower resolutions- which is better 60 or 75hz?

edit: I added cl_packetdup 1 and I'm getting 125fps now, even though displayrefresh is set to 60.....

Use 60 hz, seeing as the 75hz is fake. At least, that's what I'd do but I'm far to comfy with my crt:P

You're getting 125 fps with displayrefresh 60 because you don't have vsync on, wich is good.

Thanks!

I guess I thought that refresh rate must = fps or close to it- or something.

Even if the 75hz is fake it feels alot more responsive etc then 60hz.Easier on the eyes to.

I play with maxfps 125 , maxpackets 125 and 75 hz at a 2ms LCD and it works fine tbh. When i drop the fps to 75 the game feels less responsive.So imo 125/75 is better then 75/75.

I had a 5ms screen before and that was totaly unplayable for me.Over 2ms is a pain.

Edit: i play at 1024x768 with black bars on the side.Widescreen makes me dizzy :P

every now and then after playing for awhile, I get headaches. I like the widescreen tho- feels like I can see more

Think I have the same monitor as you :P
T220?

I'm using 125fps at 75hz and it feels fine to me. Anything lower then 75hz (60hz basically), and it feels so bad and gives me a headache. If I sync the framerate it just doesn't feel as responsive.

Yes thats the screen i have :) And i agree 125/75 feels best by far.Gonna buy me a 120hz lcd when they drop in price but tbh this one is better then i expected.

Same, I'm so close to selling the T220 and getting a 2233rz (or even just keeping the T220 for my Mac) but it's the price that's clinching it for me. I don't play so seriously that the ghosting would be such a problem for me, so it all comes down for the money. My crt died so long ago and it was just too f**kin' big for my desk anyway, so I'm not that fussed 'bout ghosting :P

Why fov 85? xD

Because he is Daler's dad!! :P

What is the command for Vsync?

dumb norwegians...

r_swapinterval
r_finish

Don't know if this helps anyone but these settings worked for my old 75Hz limited LCD and i could finally feel like smooth moving.

com_maxfps "71.4"
r_displayrefresh "75"
cl_maxpackets "72.4"
r_swapinterval "0"
(don't have a setting for r_finish + have low graphics settings)

m_filter "0" (should i bother?)

oh the power of make-believe, how wondrous.

I love the com_maxfps "71.4"

me too, maxpackets greater than fps is genius aswell.

I doubt maxpackets is still tied to fps in ql. Could be but I higly doubt they'd let something so archaic survive.

Just checked, it still is. Which explains why people with low fps look so horrible.

absolutely fantabulous

Actually, since the game CAN'T get 75 fps stable, your fps does not sync with your refresh rate, hence causing stutter.