Best Pimax VR Settings for Automobilista 2 in 2026

AMS2 is the sim where the Pimax Play Quad Views call inverts again. In iRacing I leave it off (because iRacing has native MVP). In vanilla AC I leave it on (because AC has no native foveation at all). In AMS2 it goes back off – because AMS2 has its own native Fixed Foveated Rendering pass baked into the Madness engine, and the community consensus through May 2026 is that AMS2’s native FFR is visually more stable than Pimax Play 2.0’s Quad Views injection. The exception is eye-tracked DFR on the Crystal Super, which requires Pimax Play Quad Views to run because AMS2 has no native eye-tracking integration. So you flip Quad Views on for that one specific case. Otherwise it stays off and AMS2’s own renderer does the foveation work.

The other thing worth flagging upfront: a meaningful slice of the Pimax + AMS2 community runs AMS2 in Oculus rendering mode via SteamVR, not through Pimax Play’s OpenXR runtime directly. AMS2 was originally heavily optimised for the Oculus API back in its early days, and on 4090 / 5090 hardware some users report sharper images and higher frame rates running Oculus mode than going straight OpenXR. That’s not the dominant recipe (most Pimax users go straight Pimax OpenXR), but it’s worth knowing if your default config feels softer than it should. The current AMS2 build as of late May 2026 is V1.6.9.5, and the V1.6.9 branch (December 2025 onwards) shipped meaningful Madness-engine VR perf improvements that bridged the Crystal Super gap that existed during the mid-2025 1.6.x cycle.

Quick Navigation
Jump directly to what you’re looking for:
AMS2’s native FFR vs Pimax Play Quad Views | The Oculus mode community alternative | In-game AMS2 settings (TJR Sim validated) | Per-GPU tier recommendations | Eye-tracked DFR on Crystal Super | Known 2026 gotchas – TAA, DFR refresh crashes, head tracking lock | Sources

---

AMS2’s native FFR vs Pimax Play Quad Views

The Madness engine has a Fixed Foveated Rendering pass built directly into the renderer. It’s not labelled prominently in the in-game UI, but it’s active whenever VR is engaged, and it’s been tuned by Reiza for the way Madness draws scenes. The community testing through late 2025 and into 2026 was decisive on this: AMS2’s native FFR produces fewer visual artefacts at the periphery than Pimax Play 2.0’s Quad Views injection does. The peripheral resolution drop is more graceful, and the central focal zone holds together better under heavy graphical load.

The practical rule for standard rendering on a Crystal Light or Crystal Super (without eye tracking): turn Pimax Play 2.0’s Quad Views OFF in the General tab. Let AMS2’s native FFR handle the foveation. Pixel Density at the Pimax side at 1.0, render resolution per the GPU tier below. The result is sharper than running both foveation systems stacked, which is the most common mistake I see in the r/Pimax + r/automobilista threads – users leaving Quad Views on by default because it’s the right call for iRacing, then wondering why AMS2 looks soft.

The Oculus mode community alternative

This is the AMS2-specific quirk worth knowing about even if you don’t end up using it. AMS2 supports launching in Oculus rendering mode through SteamVR, which historically was the Reiza-optimised pipeline back when Oculus was the default sim-racing VR platform. On Crystal Light and Crystal Super hardware paired with a 4090 or 5090, some community testers report Oculus mode produces noticeably sharper images and higher frame rates than running straight Pimax OpenXR. The mechanism is roughly that AMS2’s renderer was tuned harder against the Oculus API than against generic OpenXR, and even today that tuning shows up.

The honest assessment: it’s not the dominant recipe. Most Pimax users go straight Pimax OpenXR for the simplicity, and the gap between OpenXR and Oculus modes on Tier 1 hardware is modest. But if your default AMS2 config feels softer than other sims on the same kit – say AMS2 looks blurrier than iRacing or LMU at the same Pimax-side render resolution – try launching AMS2 with the -vr command line argument set to force Oculus mode through SteamVR and see if the image cleans up. About one in five Pimax + AMS2 users I see on r/Pimax in 2026 use this path; the rest stick with straight OpenXR.

In-game AMS2 settings (TJR Sim validated)

TJR Sim (Larry Ray) has done the deepest Pimax + AMS2 benchmarking I trust – 57 PPD Crystal Super on a 4090, full benchmarks at 72Hz and 90Hz, validated through May 2026 against the V1.6.9.5 build. The recipe below is the community-consensus version of his work, adjusted for the small 1.6.9 shifts. The cross-sim version of these per-tier numbers (iRacing, LMU, AC, ACC) lives in the Pimax Crystal settings sorted by GPU reference, which feeds the interactive Pimax Settings Tool on this site.

The universal AMS2 calls that hold across every GPU tier:

• Anti-Aliasing: MSAA 4x (not TAA). TAA looks broken in VR – severe ghosting whenever you move your head. MSAA is significantly sharper inside the Pimax lenses and avoids the temporal smearing TAA has on AMS2 specifically. Go High if your GPU has the headroom.
• Reflections: Low + Environment Map: Medium. High reflections tank rain frame times catastrophically on the Crystal Super.
• Shadow Detail: HIGH + Shadow Maps: Track Only. The 2026 update to the community recipe – previous guides recommended Medium shadows, but the V1.6.9 optimisations made High Shadows essentially free (1-2 FPS) for a big stereoscopic depth perception improvement. Track Only restricts shadow rendering to track geometry rather than every car and trackside object – the cost saving on a full grid is real.
• Particle Density: High + Particle Detail: Low or Medium. The split is the key: Particle Density at High gives you the visceral immersion of dirt spray and rain effects, but the underlying Particle Detail level is what costs CPU at race starts. Splitting them is how you get the look without the bottleneck.
• Detailed Grass: OFF. The single biggest FPS lever in the entire Madness engine VR pipeline. It looks worse, you stop noticing within ten minutes, and you get back 15-25% of your frame time. Always off for VR.
• Exposure Compensation: 0.6 (0.6-0.8 range). Crystal Light and Crystal Super displays are very bright. AMS2’s default exposure crushes the highlights and blows out the daytime skyboxes. Dialling Exposure Comp down to 0.6 brings it back to a natural-looking range.

Per-GPU tier recommendations

RTX 5090 / 5080 / 4090 (Tier 1)

Crystal Super 50 PPD at 90Hz, locked. Recent May 2026 benchmarks confirm a Crystal Super on an RTX 5080 can hold a stable 90 FPS even on the Nordschleife in heavy rain – provided eye-tracked DFR is enabled through Pimax Play’s Quad Views (the one case where you turn Quad Views on). MSAA High, Shadows High, all the in-game settings above pushed to their high-quality variants. The Crystal Super at 50 PPD is the visual benchmark – if you’ve got the hardware, this is what AMS2 was waiting for.

RTX 4080 / 4070 Ti (Tier 2)

Crystal Light at 90Hz, Pixel Density 1.0, MSAA 4x. To hold 90Hz lock on a full grid in wet conditions you need to turn off cockpit mirrors (virtual mirror only) and disable any optional Enhanced Effects. AMS2’s native FFR doing the foveation work means you’re not paying the Quad Views cost on top. Crystal Super on a 4080 is feasible but it’s pushing the GPU into the dirt the first time you hit Nordschleife in the rain – Crystal Light is the sweeter recipe at this tier.

RTX 4070 / 4060 Ti (Tier 3)

Crystal Light at 72Hz, capped at 69-72 FPS for frame pacing. Pixel Density drops to 0.75-0.85, Simple AA with Pimax Play sharpening claws back clarity. Detailed Grass off, all optional effects off, Particle Detail Low. The pattern that holds at this tier is the same as iRacing: a stable 72Hz feels better than a 90Hz that drops to 75 every other corner. Crystal Light is the only viable headset here – Crystal Super isn’t worth the pixel count at this GPU tier.

Eye-tracked DFR on Crystal Super

AMS2 doesn’t implement the OpenXR XR_EXT_eye_gaze_interaction extension natively – only iRacing has done that work on the major sims so far – so eye-tracked Dynamic Foveated Rendering on a Crystal Super for AMS2 has to come from Pimax Play 2.0’s Quad Views runtime-level injection. This is the one case where you flip Quad Views back on in the Pimax Play General tab, accepting the visual trade-off in the periphery in exchange for the GPU headroom that DFR buys you (usually 20-30% on a full grid).

When you do enable Quad Views for DFR on AMS2, you’re stacking Pimax Play’s eye-tracked foveation on top of AMS2’s native FFR. In theory that would be the layer-stacking mistake I warn against on every other sim, but in practice the combination behaves: Pimax Play’s Quad Views takes precedence at the runtime level, and AMS2’s native FFR sits dormant when Quad Views is active. The community testing through May 2026 confirms this is a stable combination on V1.6.9.5. If your image looks unexpectedly soft after enabling Quad Views, double-check the in-game graphics settings haven’t reverted (AMS2 sometimes does this after a Pimax Play update) – that’s a separate issue from the foveation layering.

Known 2026 gotchas – TAA, DFR refresh crashes, head tracking lock

Three issues show up regularly in the AMS2 + Pimax community threads in May 2026, and they’re all worth knowing about because the symptoms are spectacular and the root causes aren’t obvious.

TAA ghosting in VR. If your AMS2 image has motion smearing whenever you move your head – especially noticeable on trackside fences and pit-wall signage – the cause is almost always TAA being enabled. Switch to MSAA 4x and the smearing disappears. This isn’t a Pimax-specific issue; it affects every VR headset running AMS2 with TAA enabled, but it’s pronounced on the Crystal Super’s higher PPD because there’s more detail for the ghosting to muddy.

DFR + refresh-rate change crash. If you’ve got Quad Views enabled for DFR on the Crystal Super and you change the Pimax Play refresh rate (say swapping from 72Hz to 90Hz between sessions), AMS2 will frequently crash on the next launch. The Quad Views eye-tracking integration is bugged on refresh-rate swap and doesn’t reinitialise cleanly. Workaround: after every refresh-rate change in Pimax Play, reboot the Pimax Play client and the headset before launching AMS2. Takes thirty seconds, prevents a crash that costs a session restart.

Head tracking lock (the cockpit moves with your head). Periodic SteamVR updates have a habit of breaking AMS2’s camera mapping, with the symptom that the cockpit interior moves with your head while the world stays static – exactly the opposite of how it should be. Two fixes work: verify game files through Steam (forces AMS2 to re-pull its camera config), or switch to Oculus render mode as a workaround until the next AMS2 patch realigns with the SteamVR change. If you’re running straight OpenXR and this hits, file verification is the faster fix.

Pimax $25 discount: use code SIMRACINGCOCKPIT at checkout on pimax.com for $25 off any Crystal Light, Crystal Super or Dream Air.

---

Sources and credits

The settings numbers in this guide come from TJR Sim / Larry Ray’s AMS2 + Pimax benchmarking work (his 57 PPD Crystal Super on RTX 4090 / 72Hz benchmark series), validated against the V1.6.9.5 build through r/automobilista and OverTake.gg community testing in May 2026. The native FFR vs Quad Views call is the consensus position from r/Pimax + r/automobilista threads. The Oculus mode alternative is documented across Reiza’s own community guides and several long-running r/Pimax threads on the Crystal Light.

Wider SRC reference points worth pairing with this guide: my interactive Pimax Settings Tool generates the recommended settings for your exact headset + GPU + sim combination; the sister Pimax + iRacing, Pimax + LMU, and Pimax + AC guides cover the different Quad Views calls for each sim (AMS2 off, iRacing off, LMU on for DFR, AC on full-time); and the recently rebuilt Best VR Headsets for Sim Racing buyer’s guide is the place to start if you’re choosing between Crystal Light, Crystal Super, and the Dream Air. The AMS2 wheel-settings side is covered in my AMS2 wheel settings page.

V1.6.9.5 is the current AMS2 stable as of late May 2026. When Reiza ships V1.7 – rumoured to include the long-awaited dynamic weather overhaul and further Madness-engine VR optimisations – I’ll come back to this page and update.