Dirt Rally 2.0: Best hardware_settings.xml for VR Particles

The primary objective is to lower the Particle Density while maintaining high Shader Quality, which allows the dust to look “thick” without overwhelming the VR headset’s dual-eye draw call limit ($D_{limit}$).

File Path & Setup

1. Navigate to: C:\Users\[YourName]\Documents\My Games\DiRT Rally 2.0\hardwaresettings\hardware_settings_config.xml
2. Open with: Notepad++ to preserve the XML hierarchy.
3. Pro Tip: If you are using an Oculus/Meta headset, ensure you are using the Oculus VR launch mode rather than SteamVR to maximize the performance gain from these .xml tweaks.

Optimized “VR Clarity” Configuration Table

Parameter	Recommended Value	Technical Purpose
particles	low	The VR Fix. Reduces the raw count of 2D sprites in the air.
weather	low	Reduces rain/snow particle complexity to stabilize frame times.
ground_cover	off / low	Saves massive CPU overhead in foliage-heavy stages.
objects	ultra	Keep high to ensure track-side markers and turn-in points are sharp.
postprocess	low	Disables heavy bloom/blur that looks “smudgy” in VR lenses.

<?xml version="1.0" encoding="UTF-8" ?>
<hardware_settings_config>
    <cpu>
        <workerMapFile>hardware_setup_config_workerMap8Core.xml</workerMapFile>
    </cpu>
    <particles enabled="true" quality="low" />
    <weather enabled="true" quality="low" />
    <shadows enabled="true" quality="low" maskQuality="0" />
    <postprocess quality="low" />
    <ground_cover enabled="true" quality="low" />
</hardware_settings_config>

HowTo: Engineering the VR Particle Stability

Follow these GameEngineer.net technical steps to eliminate the “Gravel Stutter”:

1. The Particle Buffer Strategy: In VR, the game must render everything twice (once per eye). Setting particles quality="low" reduces the Overdraw Count ($O_c$). In dust-heavy stages, this prevents the GPU from being “smothered” by overlapping transparent textures.
2. Shadow Mask Optimization: Under the <shadows> tag, set maskQuality="0". This removes the soft-edge shadows from particles, which are almost invisible in VR but require significant $T_{frame}$ calculation time.
3. Worker Map Correction: Ensure your <workerMapFile> matches your CPU. If you have a modern 8-core CPU, manually pointing it to the 8Core.xml (found in the game’s install directory) can resolve “Stutter-Spiking” during high-speed sections.
4. Disabling “Smear” Effects: In the <postprocess> section, ensure motionblur is disabled. In VR, motion blur is the #1 cause of nausea and adds unnecessary rendering passes to every frame.
5. Multi-Sampling Protocol: In the XML, verify <antialiasing quality="taau" /> or msaa="2x". For VR, CMAA or TAA is generally preferred over high MSAA, as MSAA will multiply the particle rendering cost exponentially.

Technical Explanation: Alpha Blending and Stereo Draw Latency ($L_{stereo}$)

In Dirt Rally 2.0, every piece of gravel or cloud of dust is a “Billboarded Sprite.” In VR, these sprites must be depth-sorted and rendered for both eyes simultaneously.

$$L_{stereo} = (N_{particles} \times T_{alpha}) \times 2$$

When $N_{particles}$ (Number of particles) is too high, the GPU spends too much time on Alpha Blending ($T_{alpha}$). By setting the quality to low, we reduce the particle density, significantly lowering the Stereo Draw Latency. This ensures your headset stays at its native refresh rate, providing a “smooth-as-silk” experience even as you’re throwing your Subaru sideways through a cloud of Australian red dust.