For hitscan classes (Scout, Heavy, Engineer and Sniper), this sets snapshot_buffer_safe. snapshot_buffer=auto: Automatically sets the best interpolation value per class.Also known as linear interpolation (lerp or interp).ĭefault setting: snapshot_buffer=auto (all presets). packet_rate=standard: The standard 66 packet rate which is the maximum for all normal servers.Ĭontrols how reliable to consider the snapshots you receive from the server to apply client-side buffering/smoothing between snapshot receives.packet_rate=congestion: A halved (33) packet rate for congested networks, usually bad Wi-Fi, or very slow CPUs.sourcetv=on: Keeps compatibility with SourceTV.Ĭontrols how fast you send to and receive from the server.ĭefault setting: packet_rate=standard (all presets, except Very Low).Cannot be switched off until a game restart. sourcetv=off: Reduces the latency of changing spectator targets, but breaks compatibility with SourceTV.Optimizes spectator view, or ensures compatibility with SourceTV.ĭefault setting: sourcetv=on (all presets). Networking modules ¶ SourceTV Compatibility ¶ You can apply these new modules using apply_overrides. This means that you can change this alias in game, and have multiple versions of your modules for different quality preferences you may have. The modules you choose in overrides/modules.cfg are executed by the modules_c alias. You can reset your modules back to what they were on startup by entering run_modules into the console. So you could enter textures_high into console to temporarily set your texture quality to high for that game session. Since modules aliases act like normal commands, they can also be used in console to easily change game settings. You will have to use alias snapshot_buffer alias net_projectiles alias net_hitscan alias net_spy to fully disable it. An exception for this rule is the Snapshot Buffer module. This will prevent mastercomfig from running texture commands. If you want to disable running a module entirely, you can put (for example) alias textures in overrides/modules.cfg. Modules are backed with aliases, so you can easily use them in advanced customization and scripting. 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.These steps are entirely optional and are only for advanced customization. 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 makes Pyro an increasingly difficult class to play at higher latencies.

The Pyro's compression blast and Flamethrower are also not lag compensated, despite the effects appearing immediately after firing on a player's screen. Projectile weapons such as rockets, grenades, syringes, and flares are not lag-compensated. Were lag compensation disabled, many players would complain that they shot the enemy without inflicting any damage, which is still a issue due to hit registry and which is more of a issue with melee weapons. This is an intentional engineering and design decision, a tradeoff to enhance the realism of attacks at the expense of the realism of taking damage. 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'. 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 a high-latency (high-ping) player attacks, the server temporarily 'rewinds' its copy of the action in order to compensate for their lag. 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). Team Fortress 2, being based on the Source Engine, is generally configured to make use of lag compensation.

Tf2 ping console command