Best Pimax VR Settings for iRacing in 2026: A Complete Guide

Of every sim I run on Pimax kit, iRacing has the least setup friction. It’s also where getting the settings right pays back the most.

In 2026 I’ve stopped fighting the legacy stack. Pimax Play 2.0’s native OpenXR runtime does the headset-side work. The old PimaxXR standalone runtime is gone, OpenXR Toolkit is officially retired, and iRacing’s own foveated renderer handles the heavy lifting.

On the Crystal Super, the Tobii eye-tracking hardware now plugs straight into iRacing through the OpenXR XR_EXT_eye_gaze_interaction extension that landed in the 2025 Season 4 build. Eye-tracked Dynamic Foveated Rendering, no third-party middleware in the loop. The setup is genuinely simpler than it was a year ago. This is what works on my Crystal Light, what works on a Crystal Super, and the specific settings worth knowing about for both. Where it matters I’ve called out the differences between the two headsets, and where iRacing’s recent patches (2026 Season 1 and 2) have changed something behind the scenes.

Quick Navigation
Jump directly to what you’re looking for:
Why iRacing is the easiest sim to set up | Pimax Play 2.0 – your starting point | The MVP setting that changes everything | iRacing in-game settings by GPU tier | INI tweaks for foveated rendering | The FPS cap debate | Common mistakes and how to avoid them

---

Why is iRacing the easiest sim to set up in VR?

Three things separate iRacing from every other sim I run in VR. First, the renderer has been built on native OpenXR for years – no OpenComposite wrapper, no compatibility-layer overhead to fight. Second, iRacing added Multi-View Projection (MVP) in the 2024 Season 3 build as a quad-views foveated render that adds 20-30% GPU headroom on most kit. MVP didn’t replace the older Single Pass Stereo (SPS); it sits alongside it. SPS is still the non-foveated default, and on AMD GPUs it’s the only option because MVP requires an Nvidia RTX 2000-series card or newer.

Third – and this is the 2026 change that matters most for Crystal Super owners – the 2025 Season 4 build (September 2025) added native Dynamic Foveated Rendering through the standard OpenXR eye-gaze extension. The Tobii eye-tracking hardware on the Crystal Super now plugs into iRacing directly. The engine tracks gaze in real time and shifts the high-resolution render zone to follow your eyes.

The practical effect is that no third-party software layer is required to get a competitive image in 2026. That’s also why iRacing sits at the top of my VR sim racing games in 2026 guide – it’s the title that does the most work on your behalf when you put a headset on.

Pimax Play 2.0 – your starting point

One important caveat first: Pimax Play 2.0 is in Open Beta as of late April 2026, not stable release. The current stable branch is still 1.43.9. I run the 2.0 Open Beta for the native Quad Views path baked straight into the client, and that’s what every screenshot and setting below assumes. If you’d rather stay on stable, 1.43.9 still works fine in 2026 now that OpenXR Toolkit is officially retired – you just lose the in-client foveation toggles and revert to iRacing’s own MVP doing the work.

The PimaxXR standalone runtime (originally from mbucchia) and OpenXR Toolkit were the community standard for years. Both are now superseded. mbucchia retired from the Toolkit in 2024, there’s no active fork, and the legacy stack causes shimmer and the occasional crash on current iRacing builds. If you’ve still got the old PimaxXR shortcut on your desktop, uninstall it.

First thing every time after a Pimax Play update: General tab, set the OpenXR runtime to Pimax OpenXR. Skip this and iRacing opens as a 2D window on the monitor – that one happened to me twice in early 2026 before I learned to check it as muscle memory after every Pimax Play update. The Open Beta sometimes silently resets the runtime preference, which is the kind of thing you’d expect from a beta. Worth checking after every refresh until they polish it.

Then DisplayPort directly into the GPU. No USB-C adapters, no docking stations, no exceptions. The gap between a smooth session and a frustrating one isn’t peak FPS, it’s frame time consistency, and dodgy cabling wrecks frame time. I’ve spent more hours than I’d like to admit chasing perceived stutter that turned out to be a marginal DisplayPort connection. The full Crystal sorted-by-GPU walkthrough on this site, the Pimax Crystal settings library sorted by GPU, covers that DisplayPort-discipline message in more depth alongside the per-sim numbers.

The universal Pimax Play settings I run for every sim including iRacing:

• Refresh rate: 90Hz on RTX 5090/4090, 90Hz on RTX 5080/4080/4070 Ti, 72Hz on RTX 4070 and below. The Crystal Light can do 120Hz in lighter sims, but iRacing’s grid sizes mean 90Hz is the sweet spot – and I’d rather have headroom for the start of a heavy field at Daytona than chase a refresh rate the GPU can’t hold.
• Render resolution: 1.0 on RTX 5090/4090. 0.85 with 0.25 sharpening on RTX 5080/4080/4070 Ti – looks close to native on the Crystal Light, and to my eye the 0.85 + sharpening combo is preferable to 1.0 with no sharpening. 0.65-0.75 on Tier 3 GPUs (and at that tier a Crystal Super isn’t really viable – too many pixels for the hardware to feed).
• Smart Smoothing: Off. Every time I’ve left it on in a race, the trackside barriers ghost on high-speed sections. Only about one in ten Pimax owners enables it for sim racing in the community surveys I’ve seen. Always disable for racing.
• Brightness: 80% for daytime, 65-70% for night races. 100% wears the eyes out over an endurance stint.
• Auto IPD: Off. Get a manual measurement from an optician and dial it in via the physical slider. The Crystal Light has only the physical slider anyway – which is fine, it stays put and doesn’t drift over a session.

NVIDIA Control Panel: Power Management to Prefer Maximum Performance, VSync off, VR Pre-Rendered Frames to 1, Shader Cache to 10GB (Unlimited can bloat a drive faster than you’d think, I’ve seen it eat 40GB on a single shader recompile after a driver update), Image Sharpening at 0.25. Low Latency Mode set to Ultra gets recommended a lot but it’s disputed for VR – might be a no-op, harmless to enable either way.

The setting that matters most in iRacing VR: foveated rendering

Inside iRacing, the setting with the biggest performance impact on Pimax kit lives under Display Settings → VR. Set VR Mode to Foveated and enable Allow Eye Tracking (a new checkbox the 2025 Season 4 build added to the graphics menu, sitting next to Show Eye Tracking). Turning this on activates Multi-View Projection rendering: the quad-views foveated mode that arrived in 2024 Season 3, with the native eye-tracking integration on top from 2025 Season 4.

On a Crystal Super, MVP wires the Tobii eye tracker into the render pipeline directly. It tracks your gaze and keeps the focal point sharp while reducing peripheral detail to free up GPU overhead. Behind the wheel it’s invisible. The frame counter notices though: on an RTX 5090, a Nordschleife stint that wobbled between 60-70 FPS with DFR off locked to 90 FPS with DFR on, mirrors enabled and graphics maxed, even in heavy rain. That’s the kind of swing where the eye-tracking integration earns its money on Crystal Super hardware.

On a Crystal Light, MVP runs as Fixed Foveated Rendering: no eye tracking, but a fixed high-resolution central zone with reduced periphery. Still a meaningful jump. On my own Crystal Light at Spa in a Ferrari 296 GT3, the difference between MVP off and MVP on with the in-game UI’s foveated settings is the difference between a watchable session and a properly competitive one. Crystal Light owners on an RTX 4070 at Imola routinely report going from 60-70 FPS pre-MVP to a locked 120 FPS post-MVP once Quad Views is enabled.

The critical rule: never stack FFR layers. If you’ve turned on iRacing’s native MVP foveated mode (and you should), turn off Pimax Play’s per-game Quad Views, turn off Pimax’s FFR, and uninstall OpenXR Toolkit entirely if it’s still on your machine. Running multiple foveation systems at once doesn’t compound the benefit. It compounds the blur. I’ve seen this thread on the iRacing and Pimax subreddits more times than I can count: someone wonders why their image looks soft despite a strong FPS counter, and nine times out of ten they’ve got two or three FFR layers fighting each other in the render chain. Honestly, this is the single most common false-positive issue in 2026 Pimax + iRacing setups.

iRacing in-game settings by GPU tier

The per-tier breakdown for iRacing’s graphics settings assumes you’ve enabled MVP and you’re running Pimax Play 2.0’s native OpenXR runtime. The foveated render is doing the heavy lifting in the periphery, so what you’re tuning here is the centre of the image. For the cross-sim version of these numbers (ACC, AMS2, LMU, the lot), see my Pimax Crystal settings sorted by GPU reference – which feeds the interactive Pimax Settings Tool on this site.

RTX 5090 / RTX 4090 (Tier 1)

Maximum everything. Pixel density 1.0. MSAA x4, Shadows High, HDR on if you want the sun-glare effect through the Crystal Super’s OLED panels (HDR costs roughly 40% FPS based on community benchmarks – worth it at this tier). Cockpit mirrors enabled – virtual mirror is the default because cockpit mirrors carry a 15-20 FPS cost, but you’ve got the headroom here. Real mirrors (not virtual) at maximum count (4), high-resolution 2048×2048 car textures on, Video Memory slider to maximum.

RTX 5080 / 4080 / 4070 Ti (Tier 2)

Pixel density stays at 1.0. Virtual mirror only – cockpit mirrors cost 15-20 FPS on this tier and that 20 FPS is the difference between a stable 90 and a wobbly 75. Shadows Medium. Disable crowds, grandstands, and pit objects. Heat FX off. Shader Quality on High – barely costs anything for a noticeable improvement to brake-disc glow under heavy braking.

RTX 4070 / 4060 Ti (Tier 3)

Drop refresh rate to 72Hz, pixel density to 0.75, Simple AA with sharpening. Shadows Low. All optional effects off. Limit visible cars to 30. The strategy here is to strip the scene to what matters for racing – cars, track surface, brake markers – and let the foveated render handle the rest. The 72Hz drop from 90Hz feels like a step backwards but in my experience it’s a much smoother step backwards than running 90Hz with frequent drops to 75.

INI tweaks for foveated rendering

For owners who want to tune the foveated render beyond the in-game UI, iRacing exposes two variables in the OpenXR renderer’s config file. The file lives at Documents/iRacing/rendererDX11OpenXR.ini under the [OpenXR] header.

• FoveatedOuterPctRes – controls the outer zone resolution as a percentage. Range is 25-50. Lower means more aggressive peripheral reduction (and more GPU headroom). Start at 35.
• FoveatedInsetWidthPct – controls the size of the inner focus zone as a percentage of eye width. Range is 25-50. Start at 40.

Two cautions worth flagging because both will cost time if you miss them. The variable names are case-sensitive – camelCase exactly as written above. iRacing won’t throw an error if you mistype them; the variables will just be silently ignored and the change won’t take effect. I learned this the hard way after spending half a session wondering why a tweak made no difference. Second: these INI values sit above the in-game UI in the override chain, so changing the in-game foveation preset will overwrite them. Set the in-game values first, then come into the INI for fine-grained control.

The FPS cap debate

The iRacing VR community is split on where to cap frame rate, and there are three camps with reasoned positions.

Cap at 87 FPS – three frames below the 90Hz refresh rate so the compositor has breathing room to never miss a deadline. This is the safest setting for older hardware and the most-cited recommendation in the Pimax community. It’s where I tend to land for races on my Crystal Light because the consistency outweighs the three frames you’re notionally giving up.

Cap at exactly 90 FPS to match the refresh rate. Holds in most testing on a Crystal Light or Crystal Super paired with a 5090/4090. On lower tiers it can produce frame timing spikes when the GPU briefly dips under 90.

Uncapped. Works on a 5090 where there’s headroom to spare and the render can occasionally run faster than refresh without causing problems. Not recommended below a 4080. The GPU swings between high and low frame times, stutter perception goes up, and the raw FPS counter lies about it. I ran uncapped for a full week of practice on the Crystal Light during a Bathurst special event last year and binned the car twice into the wall at the Cutting before I worked out the perceived choppiness was the FPS sitting at 110 then dropping to 60 over the crest. Switched back to 87 for qualifying and the same hardware felt smoother by an order of magnitude. The lesson: trust frame time consistency over the headline FPS number every time.

If you’re getting micro-stutter despite a strong average frame rate, try 87 first. After enough sessions on the Crystal Light the pattern becomes obvious: a locked 72Hz feels smoother than a 90Hz spiking down to 65 every few corners. Frame time consistency tends to beat peak FPS in racing-relevant feel.

Common mistakes and how to avoid them

Five mistakes show up on the iRacing and Pimax subreddits often enough that they’re worth calling out individually. All five are avoidable.

• Stacking FFR layers. iRacing MVP + Pimax Quad Views + OpenXR Toolkit FFR all enabled simultaneously. Symptom: soft image despite high frame rate. Fix: pick one (iRacing’s native MVP is the right choice in 2026) and disable the rest. Nine times out of ten this is what’s causing a “why is my image blurry” thread.
• Still running PimaxXR standalone + OpenXR Toolkit in 2026. mbucchia retired from the Toolkit in 2024. iRacing officially asked users to uninstall OpenXR Toolkit in late 2025 because it causes crashes with the native foveated renderer. Uninstall both. Pimax Play 2.0’s “Switch to Pimax OpenXR” button replaces them entirely.
• Skipping eye-tracking calibration on the Crystal Super. Tobii eye tracking needs precise alignment. Tighten the strap mid-stint, even just a notch, and the gaze tracking drifts – DFR can’t find your eye and the high-resolution zone starts hunting around your peripheral vision. Calibrate at the start of every critical session. Takes 30 seconds.
• USB-C adapters or docking stations between headset and GPU. DisplayPort signal integrity is everything for frame time consistency. DisplayPort directly into the GPU, no exceptions. I’ve never seen this work cleanly through an adapter.
• Cockpit mirrors enabled on mid-tier GPUs. The 15-20 FPS cost is real and disproportionate to the immersion benefit on anything less than a 5090/4090. Virtual mirror at a 30Hz update cap. Real mirrors are a Tier 1 luxury and they’re nice, but not for the price they extract from a 4080.

One last confession to round out the mistakes list: the mistake I keep making myself is fiddling with foveation settings mid-week and forgetting to roll them back before a race. I’ll be testing an INI tweak on Friday, then sit on the grid at Daytona on Saturday wondering why the dash text looks fuzzy. The fix is a stable saved INI you don’t touch on race day. The lesson is the discipline to leave it alone once you’re racing.

---

Sources and credits

The numbers and screen-by-screen settings in this guide come from three places: Pimax’s own Pimax Play 2.0 Open Beta documentation, the iRacing 2025 Season 4 and 2026 Season 2 release notes, and a handful of recent Pimax + iRacing settings videos worth watching end-to-end.

• Aidan Sim Racing – Best iRacing VR Settings in 2026: Pimax Graphics & FPS Guide (May 2026). Freshest dedicated Pimax + iRacing 2026 walkthrough; the bracket layout for in-game settings tracks closely with the GPU tiers above.
• Next Level Sim Gaming – Pimax Super VR Settings: Smooth 90 FPS in iRacing (March 2026). Crystal Super on an RTX 5090, the eye-tracked DFR pathway in full effect.
• TrackJunkieRacing – iRacing VR Settings for Pimax 57PPD (February 2026). Deep dive on the 57 PPD Crystal Super engine specifically – useful if you’re considering the higher-PPD optical module.

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 Best Pimax VR Settings for Assetto Corsa Evo covers the same procedure for AC Evo; 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. If you want the spec background, my VR specs explainer walks through what PPD, foveated rendering and pancake lenses actually mean for sim racers. For the flat-screen side of the picture, my best sim racing PC games guide ranks every credible title for 2026. And if you’re tuning the wheel side of iRacing alongside the headset, my force feedback setup guide covers the FFB calibration that pairs with these graphics settings.

Settings change with every iRacing season. 2025 Season 4 brought DFR. 2026 Season 1 fixed SPS rain reflection shaders in VR. 2026 Season 2 cleaned up the VR UI position bugs and the mirror-flickering-at-init issue. When 2026 Season 3 lands I’ll come back to this page and update.