r1ch.net forums
* Home Help Search Login Register
r1ch.net  |  r1ch.net stuff  |  R1Q2  |  Topic: Need 2 cvars explained.
Pages: [1]
Print
Author Topic: Need 2 cvars explained.  (Read 2917 times)
Weasel
Member

Posts: 85



« on: December 11, 2004, 11:02:10 am »

Could you explain a little more detail about the allow_download_xxx cvars and why the servers might be set to 3 when the original server only had a 0/1 setting.

Also ths sv_msec cvar could this be causing choppiness if it is set too low?
Logged
R1CH
Administrator
Member

Posts: 2625



« Reply #1 on: December 11, 2004, 01:37:23 pm »

allow_download* is now a bitmask in preparation for TCP downloading. 1 = allow UDP downloads, 2 = allow TCP downloads, thus 3 allows all types.

sv_msecs is the milliseconds of movement a client is allowed. You shouldn't need to change this unless you know why. R1Q2 does however default sv_enforcetime to 1 which enforces the sv_msecs value by refusing movements that exceed it. In conditions where the server CPU is overloaded or otherwise not able to "keep up" with real-time, clients will find their movements get refused much more often because while the client may be sending 60 movements/sec, if the server is unable to keep up, it may take 1.5 seconds to process 1 second worth of data, so it looks like 90 movements to the server and thus some will be capped.

If you suspect the CPU is overloaded, try sv_enforcetime 0 to disable the movement restrictions. However this won't be the only problem occuring from such a condition, everything else will also appear sluggish.
Logged
Pages: [1]
Print
r1ch.net  |  r1ch.net stuff  |  R1Q2  |  Topic: Need 2 cvars explained.
Jump to:  

Powered by SMF 1.1.19 | SMF © 2013, Simple Machines