Stop using ‘sv_fps 30’ on servers.
The game (RTCW, ET) are hardcoded around a 50ms frame time. 30fps = 33.333ms frames. This causes all kinds of problems in the game – from rounding errors to just plain breaking stuff totally.
It might “lower your ping” but it also increases the bandwidth required. This usually makes the game play worse even though your ping might look “better”.
There’s good reason why ID chose sv_fps 20.
Please, stop doing it.
Um, no, it doesn’t 
In fact, not only does the Wolf/ET code recognize and understand higher sv_fps, so does the antilag code. Using sv_fps 30, as you rightly point out, shaves a good 17ms off the round trip between client and server, making the game both more responsive and much less soupy in large firefights.
The problems associated with it largely boil down to client inexperience, ie not setting snaps to the corresponding value, and server host inability to provide the extra bandwidth. And no, it doesn’t make your ping look better; as it happens the score board ping code is broken with regard to other values of sv_fps and as a result ends up looking higher Hence the need for ch_showping and similar cvars in Quake 3 competition mods.
I suggest you go do some homework m8 
Why? Because he’s coding a poorly researched competition mod? I’ve already discussed this with Locki, and his assurance, along with the knowledge of well established coders such as Promode’s arQon are the reason we opted for higher sv_fps on the Savage League servers. The same reason I’d imagine CB are using it for theirs.
Next?
fire up ET with sv_fps 30. (probably happens in RTCW OSP also, i havent checked though)
have ref pause the match.
notice anything interesting?
there are many places in rtcw/et which depend on the timer landing on exact 50/100ms boundaries. with sv_fps 30 that just doesnt happen. so stuff breaks.
we did some testing, and the flamethrower range is dependent on fps. sv_fps 30 it fires about 1 meter further than it does at 20fps… likely, other weapons are affected as well.
it’s possible to fix the code so that it’s fps independent, but the current code is broken.
And keep in mind that ET/RTCW != Q3. So invoking arqon and locki sounds cool but is irrelevant. RTCW/ET code isnt Q3 code ( q3 code is roughly 1/2 the size of ET/RTCW :disgust: )
I’m also curious to know what specific features about my mod you believe are poorly researched.
Please be exact.
btw if you want to see real ET strangeness, try sv_fps 50 on a server.
if your claim that ET/RTCW was fps independent was true, it should play exactly the same as sv_fps 20.
but it doesnt 
Silence… waiting for the next response…
Hey guys share your popcorns, i forgot to bring some with me… :drink:
/me brings along some women
can’t have popcorn and beer without the women (who else is going to bring us the beer :D)
In years of running and administrating Q3 leagues, we’ve always used sv_fps 30 to reduce latency whenever we felt the server CPU and bandwidth could handle it. This has always guided my advice on the subject.
However, I’ve double-checked this with my programmers here and they’ve told me that in ET (and RtCW too) there are sections of the code which depend on game code running at 20 hz- ie: 50ms interval between game frames - there will definitely be problems (some not necessarily visible) if sv_fps is not set to 20.
We definitely now recommend that all servers (especially league servers) run with sv_fps 20 set.
Paul/Locki.
A few of the more player-noticable things bani and I found were framerate dependent:
[ul]
[li] The pausing bug he mentioned.
[/li][li] Flamethrower range (this one can be particularly nasty.)
[/li][li] The amount of time it takes for a covert ops to steal a uniform.
[/li][/ul]
There are more problems with framerate-dependency–some of them are rather subtle, and not all of them will occur at all framerates, but they definitely exist.
In short, do not taunt the happy fun bani.
