The core of Overwatch 2’s input delay optimization lies in the SIM number (visible via Ctrl+Shift+N). If your SIM value is fluctuating or above 10ms, you are experiencing significant engine lag. By tuning the Settings_v0.ini, we can force the game to bypass texture filtering and anisotropic loops that the in-game “Low” preset often leaves active at a baseline level.
File Path
The configuration file is stored in your personal documents folder. Ensure the game is fully closed before making edits.
C:\Users\[YourUsername]\Documents\Overwatch\Settings\Settings_v0.ini
Technical Configuration (The 2026 “Zero-SIM” Template)
Open the file with Notepad. Under the [Render.13] section, update or add the following lines to hard-cap latency-inducing features.
[Render.13]
DesiredFrameRate = "600"
FrameRateCap = "600"
MaxAnisotropy = "0"
MaxEffectsAnisotropy = "0"
MaxExtraQualityAnisotropy = "0"
LocalFogDetail = "0"
EffectsQuality = "1"
ModelQuality = "1"
PhysicsQuality = "1"
HighTickInput = "1"Parameter Breakdown:
- MaxAnisotropy = “0”: Completely disables texture filtering. This removes a layer of GPU processing that adds ~0.5ms–1ms of delay, making the image sharper and “flatter” for better visibility.
- DesiredFrameRate = “600”: Tells the engine’s internal scheduler to aim for the maximum possible tick rate, regardless of your monitor’s actual refresh rate.
- HighTickInput = “1”: A semi-hidden command that ensures the game polls mouse input at the highest possible frequency relative to the engine’s frame delivery.
- LocalFogDetail = “0”: Nukes volumetric fog. In 2026 maps like Lijiang Tower or E-District, fog creates a “heavy” feeling; setting this to 0 keeps the SIM value stable.
- PhysicsQuality = “1”: Simplifies ragdoll and debris physics. During a chaotic 5v5 team fight with multiple ultimates, high physics quality can cause “Input Spikes” exactly when you need precision most.
Strategy for 2026 Input Lag Mastery
- The “SIM” Rule: Press Ctrl + Shift + N in the Practice Range. Look at the three numbers on the far right (e.g., 3.4 / 4.1 / 5.8ms). The middle number is your average delay. With this config, your goal is to keep that number under 5ms at all times.
- NVIDIA Reflex + Boost: Ensure this is ON + BOOST in-game. In 2026, “Boost” is essential because it prevents the GPU from “down-clocking” during quiet moments (like walking back from spawn), ensuring it’s at full speed the moment you see an enemy.
- High Precision Mouse Input: Always set this to ON in the Gameplay settings. It allows the game to register clicks between frames (Sub-tick aiming), which is critical if you aren’t hitting the 600 FPS cap.
- The “Alt-Tab” Bug Fix: Overwatch 2 has a long-standing bug where Alt-Tabbing can break the “Reduce Buffering” feature, doubling your input lag. If the game feels “floaty” after an Alt-Tab, toggle “Reduce Buffering” OFF and then ON again in the video menu.
Key Input Lag Metrics (SIM Values)
| Metric | Competitive Goal | Impact |
| SIM (Avg) | < 5.0 ms | Snappy, “1-to-1” feel with mouse movement. |
| SIM (Max) | < 8.0 ms | No noticeable spikes during Ultimates. |
| GPU Usage | 90% – 95% | Avoids 99% usage to stay within Reflex’s low-lag window. |
| Render Scale | 75% – 100% | Use 75% for extra FPS/SIM reduction on mid-range GPUs. |
Frequently Asked Questions (FAQ)
Does “High Quality Upsampling” (DLSS/FSR) add lag?
In 2026, NVIDIA DLSS 3.5+ and FSR 3.0 are very fast, but for the absolute lowest input delay, Default (OFF) is still superior. Upscaling requires a “Post-Processing” step that can add ~1-2ms to your SIM value.
Should I set Settings_v0.ini to Read-Only?
Yes. If you don’t, Overwatch 2 will often reset MaxAnisotropy back to 1 on the next launch. Right-click the file > Properties > Read-only.
Why does my mouse feel “floaty” despite 300+ FPS?
Check if V-Sync or Triple Buffering is accidentally ON. Also, ensure your Windows “Enhance Pointer Precision” is OFF. If it still feels floaty, check your “Aim Smoothing” in the controller settings—even on PC, it can occasionally bug out and affect mouse input.
My SIM value is high but my FPS is high. Why?
This is usually a CPU bottleneck. High SIM with high FPS means your CPU is struggling to process the game logic. Lowering PhysicsQuality and ModelQuality in the .ini is the best fix for this.
Conclusion and Expected Results
By manually stripping anisotropic filtering and forcing the HighTickInput via the .ini, you are ensuring that the Overwatch 2 engine is focused purely on raw frame delivery. You can expect a lower and more stable SIM value, the removal of “floaty” aim during high-action team fights, and near-instant registration of your flick shots.