Destiny 2: Best cvars.xml for PVE vs PVP Latency

The key to this optimization is the low_latency_mode. While the in-game menu has a toggle, the cvars.xml allows you to force “Boost” mode (Value 2), which keeps the GPU clock high even in low-load areas (like orbiting or waiting for spawns), preventing the “cold start” latency spike when an engagement begins.

File Path

Destiny 2 stores its persistent preferences in the Bungie application data folder.

%APPDATA%\Bungie\DestinyPC\prefs\cvars.xml

Technical Note: If you want to maintain separate profiles for PVE and PVP, we recommend creating two versions of this file (cvars_pve.xml and cvars_pvp.xml) and swapping them before launching the game.

Optimized “Competitive & Latency” Configuration Block

Search for these specific lines in your cvars.xml. This setup is designed for maximum PVP responsiveness while maintaining enough clarity for high-end PVE.

Parameter	Recommended Value	Technical Purpose
low_latency_mode	2	On + Boost. Keeps GPU at max clock to eliminate clock-speed-switch latency.
window_mode	3	True Fullscreen. Bypasses Windows DWM composition for $10–15\text{ms}$ less lag.
framerate_cap	[Hz - 3]	e.g., 141 for 144Hz. Keeps the game within the G-Sync/FreeSync range.
force_enable_multi_threaded_render	1	Forces the engine to distribute the render queue across all CPU cores.
mouse_smoothing	0	Disables internal Unity-style input interpolation.

<cvar name="low_latency_mode" value="2" />
<cvar name="window_mode" value="3" />
<cvar name="framerate_cap" value="141" />
<cvar name="force_enable_multi_threaded_render" value="1" />
<cvar name="mouse_smoothing" value="0" />
<cvar name="motion_blur" value="0" />
<cvar name="film_grain" value="0" />
<cvar name="chromatic_aberration" value="0" />

HowTo: Engineering the PVE vs PVP Balance

Follow these GameEngineer.net steps to fine-tune your performance based on your current activity:

1. The Shadow Quality Split: In PVP, set shadow_quality to 0 (Low). This makes player silhouettes easier to spot in dark corners. In PVE, you can keep this at High to better track “Taken” or “Hive” ground telegraphs (like fire pits).
2. Field of View (FOV): Set FOV to 105. While a higher FOV lowers FPS slightly, the peripheral vision is a mandatory advantage in both PVP (flanking) and PVE (enemy density).+1
3. Steam Launch Options: Add -high -USEALLAVAILABLECORES to your Steam properties. This tells the Windows scheduler to prioritize the Destiny 2 process over background apps like Chrome or Discord.
4. The ADS Stutter Fix: If you experience micro-stutters when Aiming Down Sights (ADS), ensure depth_of_field is set to 0 in the cvars.xml. The bokeh effect used in ADS is extremely GPU-heavy and can desync your aim.
5. Wind Impulse: Set wind_impulse to 0. This disables the physics effect on capes and grass. While it sounds minor, during a 12-player Crucible match, calculating 12 capes flapping in the wind can lead to $1\%$ low frame drops.

Technical Explanation: NVIDIA Reflex Boost (Value 2)

When you set low_latency_mode to 2 in the cvars.xml, you are enabling Reflex + Boost. Standard Reflex (Value 1) works by aligning the CPU work with the GPU to ensure the GPU doesn’t have a “backlog” of frames.

Boost Mode goes a step further: it prevents the GPU from entering its power-saving states. In a game like Destiny 2, where you might spend several minutes in a slow-paced PVE platforming section before a high-intensity boss fight, your GPU might normally downclock to save power. When the action starts, the $50\text{ms}$ it takes for the GPU to ramp back up to full speed results in a massive frame drop. Value 2 ensures your GPU is always “Ready to Fire,” which is the difference between a successful dodge and a wipe.