Actually, i thought his post was a bit more conciliatory than usual.
cl_timenudge is unchanged afaik. Values beyond -50 and 50 have no effect anyway, regardless of what the client sets them to. Timenudge just affects calculations, not packet flow, IIRC.
The only other packet packet 'timing' settings are serverside, via sv_snaps. The other settings such as antilag only alter which snaps are considered for hit determinations and the like (aka not the packet flow itself, AFAIK). (/me needs to consult with the Oracle of Reyalp)
reyalp wrote:
Timenudge operates on the client system (as the cl_ prefix indicates). It affects the client time, which in turn affects how snapshots (information from the server) are treated, and the timestamps of commands sent to the server.
- Using negative timenudge moves your client time forward, causing you to use more recent snapshots, even if this requires extrapolation. This gives you a warpier, but more up to date view of the server.
- Positive timenudge moves your client time backwards, causing you to use older snapshots, even if more recent ones are available. This essentially simulates a higher ping, although on a fluxy connection, it could make things smoother as well.
- Timenudge moves the command time of your commands sent to the server in the same way.
- Regardless of PB or etpro restrictions, the game itself will never let timenudge actually go less than -50. It also caps the positive value. Although you can set the cvar to -500, it will only move your client time by 50 ms.
In etmain, timenudge is purely client side (in the sense that the server doesn't do anything with your cl_timenudge value. Since it affects your command times, it does have some effect on information on the server.) The only reason the value is sent to the server is so the server can display it in /players.
It appears that when the pings involved are extremely low (< 10 ms) using -50 timenudge can have a small impact on how you show up on other peoples screens. This is due to another bug, but from my testing it happens rarely, even on a 100mbit LAN. The timenudger must have high FPS, high maxpackets, and a sub 10 ms ping. Even then, the resulting delta is quite small. If the timenudger is playing on the internet, this will never be factor. (note: this is due to the g_smoothsclients thing, but in practice, should be a non-issue)
The above dissertation is from the mod making forum at Splash Damage. A value for timenudge of 50 or -50 is one full snap (if sv_snaps is set to 20).
u dont allow cl_timenudge (its one cvar thats fixed)... suggestion,,clamp more cvars like.. cl_nodelta, pmove_fixed ect instead..and free the nudge..
