maccabi wrote:
Nutshell fast answer all lag comp does is smooth out the gameplay between players of differing pings, as a difference means players recieve and send updates at differing times without it the game would appear with players skipping about, standing still, rubber banding ect. that its.
first off seperate host the player to host the server.
Every player in the game (including the host P) see's a slightly different version of the game their gamestate is unique to them everyones game is slightly rewound and staggered in starting, when an action is performed in game the players update the host S, which then works out using its own version of a game (which is the pure gamestate)) what the correct outcome was or the correct outcome based on what both players reported happened).
The host P has the same system applied to them as well although slightly higher as being on the host S that player is updated faster than the player so the game has to account for this else the host has an advantage or disadvantage depending where that setting is placed.
Everything else you described is basically the effects of either this system or the interpolation applied to each players gamestate (interpolation is basically the game filling in the blanks easiest explaniation)
First off, thanks for the explanation, but why would you separate the host (player) and host (server)? The host (server) is the console in which the clients are sending updates to correct? Aside from the time necessary for the hardware to process what the "correct outcome" should be the only delay that would be calculated into lag compensation is the clients, since the host (player) update should be immediate correct?
maccabi wrote:
Lag comp DOES NOT add artifical latency , it DOESN'T penalise people with so called "faster connections"
Perhaps "lag compensation" as you explained it does not artificially inflate people's latency but I have a hard time believing that some type of host disadvantage that artificially inflates latency wasn't there in some form when the game was first released because of the situation outlined below.
The green/red bars in Call of Duty represent your latency. If I recall correctly from reading a PC players report of dissecting the game files, each bar represents 100ms of latency. So a 4 bar connection should be 0-100ms latency, 3 bar should be 100-200ms, 2 bar should be 200-300ms, 1 bar should be 300ms+. When the game was first launched I was often times selected as host (which I determine by the amount of seconds left on the countdown to the game starting when I first join) yet everyone in game had a 3 bar connection including myself as host. This would happen anytime I played with friends on the East coast (I live in the West) and pulled host until the title updates addressing "host disadvantage" were released. How is it possible that I could have a 100-200ms latency when my console is literally the host? I'm a co-owner of a local game center and any games we play on our own host/servers never ping above 5ms for in-network clients.
PS... I know you are very knowledgable in this area maccabi, but without a response from a developer or an actual break down of the network code within MW3, I think it's pure conjecture for you to make a blanket statement saying there is no artficially inflated latencies in MW3.
