Thank you. So what's the problem for me, you would ask. The problem is, that players on my server to often die, when they are already out of firing range, so I decided to find something about this "unlag" system.
----- Original Message ----- From: "Peter Kirby" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, January 20, 2006 8:00 PM Subject: Re: [hlds_linux] sv_unlag On 20/01/06, Evaldas Žilinskas <[EMAIL PROTECTED]> wrote:
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hello again, Can anyone tell the right meaning of the sv_unlag?
Well we wish it was sv_unlag 1 to remove all lag from the server ;) Really it should always be on (maybe not if you're playing on a seriously low ping LAN). Setting sv_unlag to 0 should have the same effect as setting cl_lc 0 on all clients. The server would not bother calculating for lag compensation (e.g. most people's shots wouldn't register because they would be 50 or so ms behind real time). e.g. Usually when you shoot at someone on your screen (the client) your crosshair is on the other player's head. But when you hit fire, the command is sent. During which the play has moved on. Most of the time by the time the command gets to the server that player would have moved on (hence the player would see no hit). What actually happens (when unlag is 1) is that the server checks the history for both you and the player at the time you hit fire (I don't know if it uses ping or whether with the fire command the client sends the server frame number IT was receiving at the time for comparison) to decide if you made a hit or not. This is why sometimes you die when you KNEW you made it out of firing range ;) Better to leave it on and let clients decide which they prefer. Something worth playing with might be sv_maxunlag. It defines the maximum number of seconds the server will compensate upto. I think by default this is 0.5 (500ms). If you are catering only for DSL you could lower this. I am not sure whether a lower value would translate to less taxing CPU workloads. I've never bothered changing from default. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
