The primary challenge in DiRT Rally 2.0 VR is the CPU-bound nature of the engine’s VR implementation. The game often spends too much time calculating shadows for trees and grass, causing “reprojection” or dropped frames. By modifying the configuration file, we can implement a “VR Stability” profile: disabling high-cost volumetric effects and adjusting the Mirror resolution to ensure your GPU focuses entirely on the headset’s twin displays.
Hardware Compatibility & Expectations
- Headset Focus: Essential for Valve Index, Meta Quest 3 (via Link), and HP Reverb G2 users.
- VRAM Management: VR rendering requires nearly twice the VRAM of flat-screen play. These tweaks help keep usage under 8GB.
- Refresh Rate: To avoid nausea, you should target a locked 90Hz or 120Hz. The config tweaks below are designed to keep your “1% Lows” above these thresholds.
Backup and Preparation
The hardware_settings_config.xml for VR is separate from the standard one and can be tricky to find.
- Completely exit DiRT Rally 2.0.
- Navigate to your local Documents folder (path below).
- Copy the hardwaresettings folder and save a backup to your desktop.
- Open the original file with Notepad++.
File Location
The configuration file is located in your local user Documents: C:\Users\%USERNAME%\Documents\My Games\DiRT Rally 2.0\hardwaresettings\hardware_settings_config_vr.xml
Best Config Settings for VR
Search for these specific tags in the XML. Update the values to match this “High-Performance VR” profile:
<resolution width="1024" height="768" fullscreen="0" />
<refreshRate rate="90" />
<multisampling type="off" />
<postprocess quality="1" />
<shadows enabled="true" size="1024" mask_quality="0" />
<particles enabled="true" emission="0.5" />
<weather quality="0" />
<trees quality="1" />
<crowd enabled="false" />
<mirrors enabled="true" width="256" height="128" />Pro Tip: Setting the
<resolution>to a low value like 1024×768 in the config only affects the “Mirror Window” on your desktop monitor. This significantly reduces the GPU load of rendering a third image, giving those resources back to your VR headset.
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| resolution | 1024×768 | Lowers the desktop mirror load; does not affect VR headset resolution. |
| shadows size | 1024 | Keeps shadows readable but prevents the massive CPU lag of 2048/4096 maps. |
| crowd | false | Removes the 2D spectators; a massive FPS boost in stages like Poland and Argentina. |
| trees | 1 (Low) | Essential for VR. High-quality trees in this engine cause massive frame drops in forests. |
| mirrors | 256×128 | Keeps the rearview mirror functional but at a very low resource cost. |
In-Game Settings vs. Config
To complement your VR config, match these in-game Advanced Graphics settings:
- Shader Quality: Set to Medium. This affects the lighting on the car and track. “High” is often too taxing for VR.
- Ground Cover: Set to OFF or Low. This removes the long grass, which is the #1 cause of stuttering in the “Wales” and “New England” stages.
- Anisotropic Filtering: Set to 16x. This is “free” performance on modern GPUs and keeps the track surface sharp in the distance.
- TAA: Set to ON. VR in DiRT 2.0 looks incredibly jagged without TAA. Use the config’s
postprocess quality="1"to keep it from being too blurry.
Troubleshooting & Common Fixes
- Everything looks “Shimmering”: This is a lack of Anti-Aliasing. Ensure TAA is on. If it’s too blurry, use your headset’s software (Oculus/SteamVR) to increase Super Sampling to 1.2x.
- The “Grey Screen” or “Stutter”: This is a CPU hitch. Ensure you have disabled the
crowdand setground coverto OFF in the config. - Settings Resetting: DiRT Rally 2.0 resets the VR config often. Once satisfied, right-click hardware_settings_config_vr.xml, select Properties, and check Read-only.
Frequently Asked Questions (FAQ)
Does “Weather Quality 0” mean no rain?
No. You will still see rain and snow, but the game will not render the complex “puddle reflections” and volumetric spray that are invisible in most VR headsets but tank the FPS.
Should I use ASW (Asynchronous SpaceWarp)?
Ideally, No. Try to hit a native 90Hz using these tweaks. ASW can cause “wobbly” artifacts on the fast-moving trees and fences in rally.
Is “Ground Cover” really that heavy?
Yes. In VR, rendering every individual blade of grass across the entire field of view is the single most intensive task for the EGO engine. Disabling it can provide a 30% boost in frame consistency.
Conclusion and Expected Results
By manually refining your hardware_settings_config_vr.xml, you are stripping away the hidden “desktop-class” overhead that ruins the VR experience. You can expect a locked 90/120Hz frame rate, zero motion-sickness-inducing hitches, and a clear, responsive view of the rally stage ahead.