The Tiger Engine (an evolution of the Halo engine) powers Destiny 2, and it relies heavily on a configuration file named cvars.xml. This file controls several advanced parameters that are not exposed in the game’s graphical UI, such as local light shadows, environmental detail distances, and specialized memory budgets. By fine-tuning these settings, you can achieve a more consistent frame-time graph, which is vital for both high-stakes Trials of Osiris matches and complex PVE encounters.
Hardware Compatibility & Expectations
- Competitive PvP Players: This config focuses on maximum frames and lowest latency for a 144Hz+ experience.
- Mid-Range Hardware: Helps eliminate stutters caused by “Local Light Shadows” and “Wind Impulse” physics.
- High-End PCs: Can use this to force higher FOV stability and clean up visual noise without losing the game’s artistic intent.
Backup and Preparation
Before modifying your CVARS, ensure the game is not running, as Destiny 2 will overwrite the file upon closing.
- Completely exit Destiny 2.
- Navigate to the AppData folder (path below).
- Right-click cvars.xml, select Copy, and save a backup on your desktop.
- Use a text editor like Notepad++ to modify the file.
File Location
Destiny 2 stores its configuration file in a specific Bungie-related folder in your local AppData: %AppData%\Bungie\DestinyPC\prefs\cvars.xml
Best Config Settings
Open cvars.xml and look for the following lines under the <cvar name="..." value="..." /> tags. Update the values as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
<cvars>
<cvar name="force_enable_multi_threaded_render_submit" value="1" />
<cvar name="local_light_shadows" value="0" />
<cvar name="dof_enable" value="0" />
<cvar name="motion_blur" value="0" />
<cvar name="wind_impulse" value="0" />
<cvar name="low_res_effects" value="1" />
<cvar name="mouse_acceleration" value="0" />
<cvar name="mouse_smoothing" value="0" />
<cvar name="environment_detail_dist" value="0" />
<cvar name="character_detail_dist" value="1" />
</cvars>Key Parameters Explained
| Parameter | Recommended Value | Impact |
| force_enable_multi_threaded_render_submit | 1 | Ensures the engine utilizes all available CPU cores for rendering tasks. |
| local_light_shadows | 0 | Disables shadows from small light sources (torches, lamps), providing a huge FPS boost in Raids. |
| wind_impulse | 0 | Disables physics calculations for cloth and foliage movement, reducing CPU spikes. |
| low_res_effects | 1 | Renders particles (explosions, supers) at a lower resolution to maintain FPS during chaos. |
| mouse_acceleration/smoothing | 0 | Essential for raw input and consistent aim during competitive play. |
In-Game Settings vs. Config
To complement your cvars.xml tweaks, ensure these are set in the in-game Video menu:
- Anti-Aliasing: SMAA (Better performance than FXAA in this engine).
- Texture Anisotropy: 16x (Very low performance cost, huge visual impact).
- NVIDIA Reflex: On + Boost (Significantly reduces input lag).
- Depth of Field: Off (Matches the config setting to ensure it’s fully disabled).
Troubleshooting & Common Fixes
- Settings Resetting: Bungie occasionally updates the CVARS structure. If your settings reset, you may need to re-apply the edits. Avoid setting this file to “Read-only” unless necessary, as it can sometimes prevent the game from updating essential data.
- Game Crashes: If you experience crashes after changing
force_enable_multi_threaded_render_submit, set it back to0. Some older CPUs do not handle this flag well. - Missing Textures: If characters look like “blobs,” ensure
character_detail_distis set to at least1.
Frequently Asked Questions (FAQ)
Does changing CVARS affect my account standing?
No. Modifying the cvars.xml is the only official way to adjust certain settings (like multi-threaded rendering) and is fully supported by Bungie. It is not considered “modding” or cheating.
Why should I disable ‘Wind Impulse’?
In areas like the Pale Heart or the EDZ, the engine calculates how wind affects every blade of grass and every piece of cloth on your Guardian. Disabling this frees up CPU cycles for more important tasks like tracking enemy movement.
Will this fix the FPS drops in the Tower?
The Tower is a social space where dozens of players are rendered simultaneously. While these tweaks will help, the Tower is naturally CPU-bound; however, you will notice much better stability in actual combat zones.
Conclusion and Expected Results
By optimizing your cvars.xml, you are streamlining how the Tiger Engine handles lighting and physics. Most players report more stable minimum frame rates and a noticeable reduction in stuttering during 6-man activities. This configuration is the best balance between maintaining the game’s iconic look and achieving professional-level performance.