Difference between revisions of "Lag compensation"
m (Applied filters to Lag compensation (Review RC#73726)) |
GrampaSwood (talk | contribs) |
||
| (32 intermediate revisions by 25 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Quotation|'''The Soldier'''|Stop lagging and start tagging, men!|sound=Cm soldier pregamelostlast 02.mp3}} | |
| − | + | ''Team Fortress 2'', being based on the [[Source Engine]], is generally configured to make use of '''lag compensation'''. Lag compensation is most commonly the technical reason behind cases of kills or actions that would otherwise seem infeasible in given circumstances; for example, when players perceive themselves to have been "shot through a wall" by a [[Sniper]], [[backstab]]s being performed at the incorrect angle (known as ''[[Backstab#Issues|facestabs]]''), or otherwise missing entirely (known as ''[[Backstab#Issues|failstabs]]''). | |
| − | This is an intentional engineering and design decision, a | + | When a high-latency (high-ping) player attacks, the server temporarily "rewinds" its copy of the action in order to compensate for their lag. For example, the enemy Sniper shoots when he sees your head, at that moment you and most other players may believe you successfully ran behind a wall. When the server receives the fire message from the Sniper, it "rewinds", finds out if you had ought to have been hit, and then deals damage, leading to the appearance of being "killed through a wall". |
| + | |||
| + | This is an intentional engineering and design decision, a trade-off to enhance the realism of attacks at the expense of the realism of taking damage. Were lag compensation disabled, shots that look like they hit the enemy without inflicting any damage, which is still an issue due to [[Hit detection|hit registry]] and which is more of an issue with melee weapons, would become more common. | ||
== Exceptions == | == Exceptions == | ||
| − | Projectile weapons such as [[rocket]]s, [[grenade]]s, | + | Projectile weapons such as [[Rocket Launcher|rocket]]s, [[Grenade Launcher|grenade]]s, [[syringes]], and [[Flare Gun|flares]] are not lag-compensated. The [[Pyro]]'s [[compression blast]] and [[Flamethrower]] are also not lag compensated, despite the effects appearing immediately after firing on a player's screen. This makes Pyro an increasingly difficult class to play at higher latencies. |
| + | |||
| + | Spectators do not have lag compensation. If you are spectating someone in first person, you are not seeing exactly what they are seeing, rather you are looking at what the server is seeing. This is especially noticeable with high-latency Snipers, where you should expect to see unusual shots that may appear to miss or jerk about from your perspective. | ||
| − | + | == Update history == | |
| + | '''{{Patch name|7|7|2022}}''' | ||
| + | * Fixed lag compensation when [[Weapons|melee]]-ing teammates | ||
== See also == | == See also == | ||
| − | * [[Backstab#Issues]] | + | * [[Backstab#Issues|Backstab issues]] |
* [[Source Engine]] | * [[Source Engine]] | ||
== External links == | == External links == | ||
See the following links for in-depth technical explanation of how lag compensation works in the [[Source Engine]]: | See the following links for in-depth technical explanation of how lag compensation works in the [[Source Engine]]: | ||
| − | |||
* {{vdc|Lag compensation}} | * {{vdc|Lag compensation}} | ||
| + | * {{vdc|Latency_Compensating Methods in Client/Server In-game Protocol Design and Optimization}} | ||
* {{vdc|Source Multiplayer Networking}} | * {{vdc|Source Multiplayer Networking}} | ||
* {{vdc|Prediction}} | * {{vdc|Prediction}} | ||
| + | |||
| + | {{Mechanics Nav}} | ||
[[Category:Gameplay]] | [[Category:Gameplay]] | ||
Latest revision as of 15:11, 11 August 2024
| “ | Stop lagging and start tagging, men!
Click to listen
— The Soldier
|
” |
Team Fortress 2, being based on the Source Engine, is generally configured to make use of lag compensation. Lag compensation is most commonly the technical reason behind cases of kills or actions that would otherwise seem infeasible in given circumstances; for example, when players perceive themselves to have been "shot through a wall" by a Sniper, backstabs being performed at the incorrect angle (known as facestabs), or otherwise missing entirely (known as failstabs).
When a high-latency (high-ping) player attacks, the server temporarily "rewinds" its copy of the action in order to compensate for their lag. For example, the enemy Sniper shoots when he sees your head, at that moment you and most other players may believe you successfully ran behind a wall. When the server receives the fire message from the Sniper, it "rewinds", finds out if you had ought to have been hit, and then deals damage, leading to the appearance of being "killed through a wall".
This is an intentional engineering and design decision, a trade-off to enhance the realism of attacks at the expense of the realism of taking damage. Were lag compensation disabled, shots that look like they hit the enemy without inflicting any damage, which is still an issue due to hit registry and which is more of an issue with melee weapons, would become more common.
Exceptions
Projectile weapons such as rockets, grenades, syringes, and flares are not lag-compensated. The Pyro's compression blast and Flamethrower are also not lag compensated, despite the effects appearing immediately after firing on a player's screen. This makes Pyro an increasingly difficult class to play at higher latencies.
Spectators do not have lag compensation. If you are spectating someone in first person, you are not seeing exactly what they are seeing, rather you are looking at what the server is seeing. This is especially noticeable with high-latency Snipers, where you should expect to see unusual shots that may appear to miss or jerk about from your perspective.
Update history
- Fixed lag compensation when melee-ing teammates
See also
External links
See the following links for in-depth technical explanation of how lag compensation works in the Source Engine:
- Lag compensation on the Valve Developer Community
- Latency_Compensating Methods in Client/Server In-game Protocol Design and Optimization on the Valve Developer Community
- Source Multiplayer Networking on the Valve Developer Community
- Prediction on the Valve Developer Community
| ||||||||||||||
