Use the best Pimax Crystal settings for X-Plane 12, with practical Pimax Play, OpenXR and graphics values for sharper cockpits and smoother VR.
For X-Plane 12, start the Pimax Crystal at 72 Hz, 0.75 render quality, Smart Smoothing off, parallel projection off and conservative fixed foveated rendering. In X-Plane, use full rendering resolution, 2x MSAA, high textures, medium clouds and shadows, high objects, and disable parked aircraft. Raise resolution only after frame times are stable.
This is a balanced starting profile rather than a universal maximum. Complex airports, weather, aircraft systems and plugins can make X-Plane 12 CPU-limited even when the Crystal's very high resolution appears to be the obvious problem.
Recommended Pimax Crystal settings for X-Plane 12
This Pimax Play profile preserves cockpit clarity without starting at an unnecessarily expensive render resolution.
| Setting | Recommended baseline | When to change it |
|---|---|---|
| Refresh rate | 72 Hz | Use 90 Hz if 72 Hz flicker bothers you or the system can sustain 90 fps, or a steady 45 fps with smoothing. |
| Render quality or resolution scale | 0.75 | Try 0.85 and then 1.0 only after testing a demanding airport and heavy weather. |
| Smart Smoothing | Off while tuning | Enable it only when frame rate remains close to half the headset refresh rate: 36 fps at 72 Hz or 45 fps at 90 Hz. |
| Fixed foveated rendering | Conservative or balanced | Reduce or disable it if side instruments become visibly pixelated when you move your eyes without turning your head. |
| Dynamic foveated rendering | Off initially | Enable it only if the selected runtime path confirms working eye tracking and X-Plane shows no peripheral or one-eye artefacts. |
| Parallel projection compatibility | Off | Enable it only to correct double vision, incorrect culling or another verified compatibility problem. |
| Hidden area mask | On | Turn it off if scenery is clipped near the lens edges. |
| Local dimming | Balanced | Adjust for black level and bloom at night; it is not a meaningful performance control. |
Avoid multiplying resolution in several places. Set the primary scale in Pimax Play, leave X-Plane at full internal resolution, and keep any additional OpenXR or SteamVR scale at 100%. Two simultaneous supersampling controls can push the actual per-eye resolution far beyond what their individual percentages suggest.
Best X-Plane 12 graphics settings for the Crystal
X-Plane 12 should render at full internal resolution while the headset software controls the main resolution reduction.
| X-Plane setting | Recommended baseline | Performance guidance |
|---|---|---|
| Rendering resolution | 100% or full resolution | Avoid sub-native upscaling unless resolution changes in Pimax Play are insufficient. |
| Anti-aliasing | 2x MSAA | Try 4x only with spare GPU time. FXAA is cheaper but can soften cockpit lettering. |
| Texture quality | High | Use maximum only when VRAM usage remains controlled with the intended aircraft and scenery. |
| Anisotropic filtering | 8x or 16x | Usually inexpensive and useful for runway and taxiway sharpness at shallow angles. |
| Cloud quality | Medium | Lower this before sacrificing cockpit resolution in dense cloud layers. |
| Shadow quality | Low or medium | Medium retains useful cockpit shading; lower it when the GPU frame time spikes. |
| World object density | High | Reduce this first at detailed airports when the CPU frame time is the limiting factor. |
| Rendering distance | Medium to high | Long distances can add CPU and GPU load for limited benefit during cockpit-focused flying. |
| Vegetation density | Medium | Raise it for low-level VFR only after airport performance is acceptable. |
| Parked aircraft | Off | Static aircraft consume resources and can conflict visually with traffic add-ons. |
Texture quality should not be the first setting lowered unless VRAM is overflowing, which often appears as severe hitching when views change. For a wider explanation of the controls, our guide to balancing X-Plane 12 graphics quality and performance covers scenery detail, clouds, shadows and anti-aliasing.
Should I use OpenXR or SteamVR with the Pimax Crystal?
Use X-Plane 12's native OpenXR path when it is available in the installed build, with Pimax selected as the active OpenXR runtime. This avoids adding an unnecessary SteamVR translation layer and makes resolution management easier to understand.
Use SteamVR when the installed X-Plane build, aircraft or VR-related plugin specifically requires its OpenVR path. Do not launch both paths or apply supersampling in Pimax Play, OpenXR and SteamVR at the same time. Our step-by-step X-Plane 12 VR setup explains the simulator-side activation and controller checks.
The original Crystal includes eye tracking, but that does not guarantee dynamic foveated rendering in every runtime path. Eye tracking, the runtime and the application must all support the chosen method; otherwise fixed foveated rendering is the safer option.
How should I tune the Crystal for a stable frame rate?
Tune against a repeatable demanding scenario, not an empty runway in clear weather.
- Establish a clean baseline. Use 72 Hz, 0.75 Pimax render quality, 2x MSAA and the settings above. Disable Smart Smoothing so it cannot hide unstable frame times.
- Test the aircraft you actually fly. Load a detailed airport, a complex cockpit and representative clouds. Simple default aircraft can conceal a CPU bottleneck that returns in an airliner.
- Identify the slower frame time. If CPU time is higher, reduce world objects, rendering distance, traffic and CPU-heavy plugins. If GPU time is higher, reduce Pimax render quality, anti-aliasing, clouds and shadows.
- Change one control at a time. Retest the same view and weather after each adjustment. Large groups of changes make the real bottleneck impossible to identify.
- Add smoothing last. Smart Smoothing works best when the simulator reliably holds 36 fps at 72 Hz or 45 fps at 90 Hz. An arbitrary 30 fps cap does not divide evenly into either refresh rate.
- Spend spare performance on resolution. Raise Pimax render quality in small steps before increasing MSAA. The Crystal usually gains more cockpit readability from additional render resolution than from very high anti-aliasing.
Why does X-Plane 12 still look blurry in the Crystal?
Persistent blur usually comes from lens alignment, duplicated scaling or sub-native rendering rather than texture quality alone.
- Set the headset's IPD, vertical position and strap tension before judging software settings. The eyes must sit in the lens sweet spot.
- Keep X-Plane at full rendering resolution and scale in one runtime only.
- Avoid aggressive fixed foveated rendering if instruments blur whenever you look towards the edge of a lens.
- Use 2x MSAA rather than a softer post-process anti-aliasing option when cockpit text is the priority.
- Check that VRAM exhaustion is not forcing texture swapping, especially with detailed scenery and aircraft.
If the centre of the image remains soft, work through our X-Plane 12 VR blur troubleshooting checklist before increasing supersampling again.
Why does the Crystal stutter when GPU usage is low?
Low GPU usage with stuttering normally indicates a CPU or frame-pacing limit, not spare performance for more resolution. X-Plane's main simulation work, complex avionics, traffic and scenery preparation can hold back the graphics card.
Reduce world objects, rendering distance, traffic and demanding plugins first. Also watch the smoothing threshold: fluctuating around 36 fps at 72 Hz or 45 fps at 90 Hz causes repeated transitions between reproduced and unsmoothed frames, which feels worse than a steady lower setting. Propellers, rotor blades and moving glass-cockpit text may show interpolation artefacts even when smoothing is holding correctly.