wrote:

By the way, since we're talking about server lag — I wanted to ask about xp_delagWeapons.
[...]
On the other hand, xp_delagWeapons rewinds the server state based on the player's ping, making hitscan weapons register exactly when the crosshair is over the enemy on the client's screen.

it does not, it turns off server confirmation for the weapons its enabled for. So instead of printing the rail the way the server sees it, it displays it as your client sees it. so on higher ping and slopes/stairs the actual rail position is off the actual position. it also causes a lot of "shooting through" due to your rail being printed before rail confirmation or your own death confirmation gets send. A lot of players complaining about "their rail going through" and I all had to tell them to turn off delagweapons to get what you see is what you get.

@Fubar - it doesn't matter. antiwallhack by itself is just buggy and thats why it was mandatory to have it zero on clanwars and any server with good players on it. in that situation I was supposed to get the kill any day of the week and yet I didnt because the server denied me the position info. the video just shows part of the picture since the effect is even worse live. antiwh also contradicts xp_improveprediction which was made to circumentvent bugs in the q3 culling/netcode that causes the same effect around specific corners in specific maps. both cvars do roughly the opposite. I am done with elitez server and this is the last sentence about it.