Get practical Pimax Crystal Super settings for MSFS 2024, covering OpenXR, resolution, DLSS, LOD, foveation and Smart Smoothing.
For the Pimax Crystal Super in Microsoft Flight Simulator 2024, use Pimax as the OpenXR runtime, 90 Hz, 75–80% headset render quality, DLSS Quality, High clouds and 100–150 Terrain/Object LOD. Keep Smart Smoothing off initially, enable eye tracking, and use balanced dynamic foveated rendering only when it tracks reliably.
Recommended Pimax Crystal Super baseline
The Crystal Super's very high render resolution makes 100% an image-quality target rather than a sensible universal starting point. We recommend establishing stable frame times at 75–80%, with MSFS render scaling left at 100%, before increasing headset resolution.
| Headset setting | Recommended baseline | When to change it |
|---|---|---|
| OpenXR runtime | Pimax OpenXR directly | Avoid routing MSFS through SteamVR unless another application specifically requires it. |
| Refresh rate | 90 Hz | Use a lower supported rate if 90 Hz produces unstable frame pacing or you want an easier reprojection target. |
| Render quality | 75–80% | Raise towards 100% only after testing a demanding airport, complex cockpit and poor weather. |
| Smart Smoothing | Off while tuning | Enable only when the PC can maintain at least half the selected refresh rate without repeated drops. |
| Eye tracking | On and calibrated | Recalibrate after changing headset fit or IPD. |
| Dynamic foveated rendering | Balanced, where supported | Disable it if the sharp region lags behind your gaze or peripheral instruments become distracting. |
| Parallel projection | Off | Enable only if the cockpit view is visibly misaligned; it carries a substantial rendering cost. |
| Local dimming | Medium or Balanced | Increase for darker blacks, or reduce it if bright objects show distracting halos or shadow detail is crushed. |
Pimax Play labels can vary between software releases, but the principle is unchanged: use one direct OpenXR path and control the primary resolution in one place. A mistake we see constantly is combining raised Pimax render quality, SteamVR supersampling and increased MSFS render scaling. Those multipliers compound and can overwhelm even a top-end GPU.
Is 100% Crystal Super resolution worth using?
Use 100% only when the simulator remains GPU-stable in the most demanding flying you actually do. It may be practical in a light aircraft away from cities but fail badly with an airliner, detailed hub and heavy cloud. Owners of NVIDIA's fastest hardware can compare the trade-offs in our RTX 5090 VR tuning recommendations, while retaining the Crystal Super-specific resolution baseline above.
Which MSFS 2024 VR graphics settings should I use?
MSFS 2024 should prioritise readable instruments, stable clouds and consistent frame times rather than an indiscriminate Ultra preset.
| MSFS 2024 setting | Recommended baseline | Adjustment guidance |
|---|---|---|
| Anti-aliasing | DLSS Quality on an RTX GPU | Use DLAA or TAA for clearer glass-cockpit text if there is enough GPU headroom. Try DLSS Balanced before Performance when more speed is needed. |
| Render scaling | 100% | Leave this alone while tuning Pimax resolution. With TAA, 80–100% is a useful range. |
| Terrain Level of Detail | 100–150 | Lower it when the performance overlay reports a main-thread bottleneck, especially around cities and large airports. |
| Objects Level of Detail | 100–150 | Reduce it for complex terminals and dense scenery rather than lowering headset resolution. |
| Volumetric Clouds | High | Ultra is expensive in VR. Reduce to Medium during GPU-limited weather before sacrificing texture clarity. |
| Texture Resolution | High | Use Ultra only with comfortable VRAM headroom and no loading-related pauses. |
| Anisotropic filtering | 16x | Keep it high; runway and ground textures benefit without the cost of heavier effects. |
| Off-screen terrain pre-caching | High | Use Ultra when VRAM permits and scenery pop-in during head movement is visible. |
| Shadow maps and terrain shadows | Medium | Raise cockpit shadows only after resolution, clouds and frame timing are settled. |
| Ambient occlusion and reflections | Low or Medium | These are early candidates for reduction when GPU-limited. |
| Cockpit display refresh | Medium | Lower it if a glass-heavy airliner is main-thread limited. |
| Aircraft, airport and road traffic | Low or Medium | Reduce these around major hubs; they affect the CPU and can cause frame-time spikes. |
| Motion blur and depth of field | Off | They add little in a headset and can make instruments less comfortable to read. |
DLSS Quality is the practical starting point, but it can smear small digits, moving map labels and thin lines. DLAA gives the cleanest presentation when the GPU can afford it; TAA is the alternative when DLSS ghosting is more objectionable than its performance benefit.
How should I tune the Crystal Super for my PC?
Change settings according to the limiting component rather than lowering everything together.
- Choose a repeatable test: load the aircraft, airport, weather and time of day that represent your demanding normal flight.
- Disable Smart Smoothing: measure native performance first so generated frames do not hide the real bottleneck.
- Check the MSFS performance overlay: if GPU-limited, reduce headset resolution, clouds, shadows or the DLSS preset. If main-thread limited, reduce Terrain LOD, Objects LOD, traffic and cockpit display refresh.
- Change one layer at a time: use 5–10% resolution adjustments and retest from the same cockpit position.
- Add reprojection last: enable Smart Smoothing only after the underlying frame rate holds a stable half-refresh target.
Our GPU-versus-main-thread VR tuning workflow covers the wider diagnosis without duplicating those steps here.
Should I use 72 or 90 Hz and Smart Smoothing?
Use 90 Hz for the most responsive native image, but select 72 Hz if it is offered by your installed headset software and the lower target produces steadier frame times. A consistent lower refresh rate feels better than repeatedly missing 90 Hz.
Smart Smoothing works best when the real frame rate stays above half the headset refresh: 45 fps at 90 Hz or 36 fps at 72 Hz. If performance moves above and below that boundary, expect judder, doubled cockpit lettering or warping around propellers, rotor blades and wing edges. Lower resolution enough to hold the target before enabling smoothing.
Why are Crystal Super gauges blurry or doubled?
Blurry or doubled gauges usually come from reconstruction, reprojection or incorrect scaling rather than the headset panels.
- DLSS ghosting: switch from DLSS Quality to DLAA or TAA and accept the additional GPU load.
- Doubled text during head movement: disable Smart Smoothing to confirm that reprojection is responsible.
- A sharp area that misses your gaze: recalibrate eye tracking, check headset fit and test with dynamic foveated rendering disabled.
- The entire cockpit looks soft: confirm that MSFS render scaling has not been reduced and that SteamVR is not adding another resolution override.
- Only peripheral text is poor: move foveated rendering towards its quality setting instead of raising the complete headset resolution.
What causes stuttering after the image looks good?
Stuttering with acceptable average performance points to inconsistent frame times, runtime conflicts, CPU spikes or exhausted VRAM. Regular judder while turning your head suggests reprojection or an extra OpenXR layer; pauses while approaching detailed scenery more often indicate loading, traffic or memory pressure.
Use one OpenXR runtime, disable optional overlays while testing and restart both the headset software and simulator after major runtime or resolution changes. Our VR frame-time troubleshooting sequence covers persistent head-movement jitter. If pauses coincide with texture loading or memory saturation, apply the settings that reduce MSFS 2024 VRAM pressure first rather than making the whole headset image softer.