Forum
Unstable 120fps vs Stable 60fps
Created 26th October 2010 @ 01:04
Add A Reply Pages: 1 2 3 Next »
On a 60hz screen…
What would you rather play with…
Unstable 120fps vs Stable 60fps?
Depends what you mean by “unstable”, there’s too many what if’s. tbh, Just try both for a while and see which you prefer.
(oh protip, assuming you’re using fps_max to limit it, set it to 67, not 60. Also if you’re using it to limit it to 120 atm, set it to 0. The network stuff is thrown in along with the graphics in terms of FPS, so with fps_max 60 on a 66 tick server (i.e. everything but fantastically shit 32 man publics) you’re going to drop every 11th tick which isn’t really an issue, but can sometimes cause really weird hit reg issues.)
Last edited by Skyride,
It depends on what you mean by ‘unstable’, but assuming you mean it often dips below, as long as it doesn’t dip below 66 you shouldn’t actually notice the drop all that much.
Last edited by octochris,
For me a stable fps makes my mouse much easier to control.
Just go lower untill stable, instead of such a jump. like 100 maybe?
Quoted from quad
For me a stable fps makes my mouse much easier to control.
Just go lower untill stable, instead of such a jump. like 100 maybe?
That should only happen if you go below your refresh rate or your cmdrate. Either way it shouldn’t affect the performance of your triggerbot.
Last edited by octochris,
So if i understand correctly, i dont have to worry about anything if my fps stays above 60?
Last edited by Martn,
Quoted from Martn
So if i understand correctly, i dont have to worry about anything if my fps stays above min 60?
It’s not really as simple as that, your cmdrate should be 67 ideally too, so really 67 is your minimum limit, but you don’t want to be constantly running at that.
The game also does suffer a bit when getting below 1.5*refresh.
Quoted from octochris
[…]
It’s not really as simple as that, your cmdrate should be 67 ideally too, so really 67 is your minimum limit, but you don’t want to be constantly running at that.
The game also does suffer a bit when getting below 1.5*refresh.
I know that your cmd rate should the value you want + 1 but since etfl restricts it to 66 it has no effect to set it to 67 or am I wrong?
Quoted from XHunter
[…]
I know that your cmd rate should the value you want + 1 but since etfl restricts it to 66 it has no effect to set it to 67 or am I wrong?
You’re wrong — the server sends 66 updates in either case, it is the client side which is affected by the 67 setting.
Quoted from octochris
[…]
You’re wrong — the server sends 66 updates in either case, it is the client side which is affected by the 67 setting.
But you can’t set it to 67 because of sv_maxcmdrate 66 which will set it to 66 or is the client still using the 67 value oO im a bit confused.
Plz help me :P
Last edited by XHunter,
assuming thread hijack.
Asrock 4CoreDual-SATA2 (chipset VIA PT880 that is), C2D 2.8GHz, Sparkle GF7600GS, Samsung Syncmaster 2232BW (60Hz that is). Running TF2 at native res (1680×1050) causes smooth lag – input processing is delayed, fights with lots of particle processing involved lower fps as well. It’s not just an fps drop though, the game itself just slows down for a moment, like it insisted to render everything instead of skipping it like a man. Should I just lower the fps cap until it disappears or just stay at lower res?
Im so confused, tried dx9 config and its giving me the same results pretty much as maxframes…. surely that shouldnt be?
maxframes – max fps 120 – constant drop to 30-40
dx9 – max 67 – drops tp 30-40 but its easier to play on as drops arent severe :S
unstable fps_max 121
read the cadred articly why
i second their opinion, that capping it to double the fps of ur hz +1, has better feeling than capping to HZ + 1
i got 100hz monitor, capping fps to 201 is soo much smoother than with fps_max 120, even if i have only 120-200fps
Last edited by AnimaL,
Add A Reply Pages: 1 2 3 Next »
content rss