Phasmophobia: Best settings.json for VR Performance

The primary goal for Phasmophobia VR optimization is Frame Timing Stability and Flicker Reduction. The game often reprojects frames if it cannot hit a native 90Hz, which creates a “doubling” effect on ghost models. This configuration focuses on disabling Anisotropic Filtering and Ambient Occlusion, which have disproportionately high costs in stereo rendering (VR).

Hardware & System Prerequisites

  • Refresh Rate Lock: Always target 90Hz. Users on 72Hz or 120Hz often report “choppy” movement even on high-end cards (RTX 3080/4090/5090).
  • OpenXR Runtime: Ensure your headset (Oculus/Meta, Index, WMR) is set to its native OpenXR runtime to bypass SteamVR’s extra layer of overhead.
  • VRAM Bottleneck: Phasmophobia’s “High” textures are massive. If you have less than 10GB VRAM, set textures to “Half” or “Quarter” to prevent the “Pink Texture” glitch.

File Location

The game stores its core settings in the Windows Registry or a local JSON file depending on the build. For the standard Steam version, look here:

%USERPROFILE%\AppData\LocalLow\Kinetic Games\Phasmophobia\saveData.txt (Note: Some VR-specific flags are handled in the settings.json found in the same folder or via the Unity Registry keys.)

Technical Configuration (Code Block)

For VR, it is often better to use Launch Options in Steam alongside the config file to force a lighter rendering path:

Steam Launch Options:

-vrmode openvr --enable-vr -window-mode exclusive

Recommended JSON / In-Game Overrides:

{
  "Graphics": {
    /* Essential: Anisotropic filtering causes major stutter in VR */
    "AnisotropicFiltering": 0,
    
    /* 0 = Low, 1 = Normal. Keep shadows 'Hard' for performance */
    "Shadows": 0,
    
    /* Disabling AO removes the 'dark halo' glitch in VR headsets */
    "AmbientOcclusion": false,
    
    /* Use FSR or DLSS (Balanced) to hit the 90fps target */
    "FidelityFX_FSR": "Balanced",
    
    "AntiAliasing": "SMAA"
  }
}

Strategy for Spectral-Smooth VR

To ensure you can outrun a Revenant without your headset lagging:

  • The 90Hz Golden Rule: Recent 2026 community testing confirms that Phasmophobia’s internal clock is most stable at 90Hz. At 72Hz or 120Hz, the physics engine often desyncs from the display, causing “micro-stuttering” even if your FPS is high.
  • Ditch SteamVR (if on Quest): Using Oculus Link or Virtual Desktop (VD) with the “Vdxr” (OpenXR) runtime allows you to bypass SteamVR completely, saving roughly 15% of your GPU overhead.
  • Window Resolution: Even though you are in VR, the game renders a “mirror” on your desktop. Set the PC Window Resolution to the lowest possible setting (e.g., 1280×720) and minimize it once the game starts. This saves a small but vital amount of VRAM.

Key Performance Parameters

ParameterRecommended ValueImpact
Anisotropic FilteringOffEliminates the primary cause of VR micro-stutter.
Shadow QualityHard / LowReduces CPU draw call overhead significantly.
Refresh Rate90HzMatches the game’s internal physics tick rate.
Anti-AliasingSMAAFixes “shimmering” on fences/railings without blurring.

Frequently Asked Questions (FAQ)

Why does my mic stop working in VR?

Phasmophobia’s voice recognition is sensitive to the “Active Window.” If you click on your desktop or another app while in VR, the game loses focus and the mic stops working. Always ensure the Phasmophobia window is in the foreground on your PC.

Is FSR/DLSS worth it in VR?

Yes, but only if set to “Quality” or “Balanced.” “Performance” mode can make the ghost’s fingerprints or EMF lights look too “ghostly” (blurry) to read properly.

How do I fix the “Pink Textures” in VR?

This is a VRAM overflow. Restart the game and lower your Texture Quality. Unity fails to clear old textures when loading between Sunny Meadows and the Lobby, eventually leading to the “pink” crash.

Why can’t I find the “Options” menu in VR?

In VR, the main menu is on your Journal. Point at the journal on your belt, pull it out, and use the tabs at the top to find the settings.

Conclusion and Expected Results

By manually refining your settings.json to disable anisotropic filtering and locking your refresh rate to 90Hz, you are stabilizing the Unity-to-VR bridge. You can expect a significant reduction in “head-tracking” jitter, clearer visibility in dark corridors, and the elimination of the most common VR-induced crashes.

Leave a Comment