SRCDS Steam group


Member
#1
Member
Reply
#2
no that's not normal. btw, server netsettings all start with sv_, not with cl_, so it must be:
sv_maxcmdrate 66
sv_mincmdrate 66

I don't think this is your problem though (standard settings should be also fine). is it only for you, or do other players have the same problem? and please give us details on the server:
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
Reply
#3
Hm.. I got that problem too, only on my Gmod server tho.
Reply
#4
This is a known thing with the source engine. The client and server run in different time configurations. In order for the client to see other clients, the server has to send all information between clients. Because the data is old (not in present time) the server tries to update information with what happened previously, hence the jumps etc.

There are some client commands you can use to experience better gameplay, but I can't remember them.
Reply
#5
I think one of them is cl_interp.

If its not happening on other servers, its probably due to a lower latency, thus "faster" reactions and predictions.
Reply
#6
yes, I forgot in my statement: it's not normal unless you or someone else has a very high ping. you can expect some "strange" behaviour in the order of the sum of your and the respective opponent's ping. but usually this should be into the past, not into the future, i.e. he shoots you but you live a short time longer and e.g. hide behind a corner before you die. usually you get set back to the position where you really died, so for you it seems you jump back in time. that's perfectly normal and the only way things can be handled correctly and fair. from your opponent's perspective he killed you right at that position and you did not even move behind that corner.

the described behaviour by you looks like you have a very high ping on that server, or you have some very high cl_interp setting (which effectively increases the ping -> which doesn't mean you should set it to 0). cl_interp should be 2-3 times the time between two ticks, i.e. (at tick 66) 0.03 or 0.045 (or something similar). 0.1 would also be fine, but not 1.0 or so...
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)