Bug 2948 - g_skipCorrection and g_maxWarp
Status: RESOLVED WONTFIX
Alias: None
Product: Tremulous
Classification: Unclassified
Component: Misc
Version: unspecified
Hardware: All All
: P2 enhancement
Assignee: Tremulous Bugs
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2006-12-09 15:15 EST by Tony J. White
Modified: 2007-07-19 11:17:39 EDT
0 users

See Also:


Attachments
svn866 g_skipCorrection/g_maxWarp (6.12 KB, patch)
2006-12-09 15:16 EST, Tony J. White

Description Tony J. White 2006-12-09 15:15:50 EST
This idea comes from Neil Toronto's unlagged project.  When a player
experiences packet loss they appear to "warp" from one place to another
when their first cmd is processed after a series of missed ones.  This
can be very annoying to the other players.

g_maxWarp - the maxiumum number of server frames a client is allowed to miss
            before it's next movement is clipped.  Default is 3 ( 150ms on most
            servers )  Set this to 0 to disable it.

g_skipCorrection - if set to non-0, the server will guess where there player
                   would have moved based on his current trajectory and
                   sends this position in the next snapshot to all clients.
                   Also, other players will be able to hit them at this
                   predicted location.

                   If g_maxWarp is enabled, then this will happen for up to
                   g_maxWarp server frames, otherwise it will happen for up to
                   3 server frames.
Comment 1 Tony J. White 2006-12-09 15:16:21 EST
Created attachment 1193 [details]
svn866 g_skipCorrection/g_maxWarp
Comment 2 Tony J. White 2007-07-19 11:17:39 EDT
I think this whole implementation is flawed.  Abandoned.