Fix X-Plane 12 VR shimmering and shaking by diagnosing aliasing, tracking loss, reprojection, frame-time spikes and GPU instability.
X-Plane 12 VR shimmer usually comes from aliasing, low headset render resolution or aggressive sharpening, while a view that physically shakes points to tracking loss, reprojection or uneven frame times. Raise anti-aliasing or render resolution modestly, stabilise headset tracking, remove overlays, and reduce GPU-heavy settings until frame delivery is consistent.
Is it shimmer, judder or head-tracking shake?
Shimmer, judder and head-tracking shake are different faults and need different fixes. A mistake we see constantly is increasing anti-aliasing when the whole scene is moving because the headset has lost tracking; that only adds GPU load and can make the shaking worse.
| What you see | Likely cause | Useful test |
|---|---|---|
| Runway markings, fences and distant buildings sparkle or crawl | Aliasing, low render resolution, sharpening or upscaling | Turn your head slowly while watching one high-contrast edge |
| The cockpit and outside world shift despite your head being still | Headset tracking loss or an unstable tracking origin | Pause X-Plane and watch a fixed cockpit reference |
| Objects double, smear or wobble during head turns | Reprojection or missed frame deadlines | Check the VR runtime's frame-time display |
| Black frames, one-eye flashes or a crash | Driver, VRAM, plug-in or Vulkan instability | Test a default aircraft and inspect Log.txt |
How do I stop X-Plane 12 VR from shimmering or shaking?
Use this order so that one change does not hide another fault.
- Establish a clean baseline. Close X-Plane, disable third-party overlays and temporarily move third-party plug-in folders out of
Resources/plugins. Load a default aircraft at a simple default airport with uncomplicated weather. Return the headset runtime's per-application render scale to its baseline and temporarily disable dynamic resolution, extra sharpening and third-party foveated rendering. - Fix tracking before changing graphics. Clean the headset's tracking cameras or sensors, use even room lighting, remove strong reflections and direct sunlight, and make sure external tracking stations are secure and unobstructed where applicable. Re-centre the seated view. PC headsets should also be tested without an unpowered USB hub or questionable extension cable. Our X-Plane 12 VR setup and view-centring checklist covers the wider connection and calibration process.
- Create stable frame times. Temporarily lower anti-aliasing and headset render resolution. Reduce world-object density if the main CPU thread is overloaded; reduce clouds, shadows, reflections and render resolution when the GPU is late. Lower texture quality only when VRAM pressure is evident, because it does little for ordinary tracking shake. The detailed X-Plane 12 graphics trade-offs explain which settings affect clarity, GPU time and VRAM.
- Tune shimmer after the view is smooth. Increase X-Plane's anti-aliasing by one step, retest the same scene, and then raise the headset's per-application render resolution in small increments if performance allows. Do not raise both at once. Reduce driver or runtime sharpening if fine lines acquire bright, crawling outlines. Anisotropic filtering helps oblique runway and ground textures, but it does not cure geometry aliasing; our guide to fixing jagged and crawling edges covers that distinction in more detail.
- Test motion smoothing both ways. Reprojection can make a consistently low frame rate feel smoother, but it may produce doubled wings, distorted propellers and wobbling cockpit frames. If performance keeps crossing the reprojection threshold, lower the load or choose a lower headset refresh rate where supported rather than allowing repeated mode changes.
- Reset damaged settings only after testing the above. Back up and rename
Output/preferences, then let X-Plane create clean preferences. This resets graphics, views and control assignments, so recalibrate before copying anything back. If the fault began after a graphics-driver change, use the hardware vendor's stable recommended driver or return to the previously working one. Black frames, device-loss messages or crashes need the separate Vulkan GPU and device-loss checks.
Should motion smoothing be on or off in X-Plane 12?
Use motion smoothing when X-Plane can maintain the compositor's supported lower cadence consistently; turn it off when you can hold the headset's native refresh rate or when reprojection distortion is more distracting than judder. Switching repeatedly between native and reprojected modes feels worse than either stable state.
A frame-time graph is more useful than average frames per second. Brief CPU or GPU spikes can shake the view even when the displayed average appears acceptable.
Why does VR shimmer mostly at airports or at night?
Airports contain many thin, high-contrast details that become smaller than one headset pixel at a distance. Fences, light poles, roof edges, runway markings and night lighting therefore expose aliasing more readily than broad terrain.
Moderate anti-aliasing and a higher fixed render resolution reduce this, but they cannot remove every sub-pixel artefact. Scenery shadows can also crawl independently of geometry; reduce or disable those shadows if the shimmer follows shaded edges rather than the object itself.
How can I tell whether VR judder is CPU- or GPU-limited?
A large improvement after lowering render resolution or anti-aliasing indicates a GPU limit. If those changes barely help but reducing world objects, traffic, aircraft complexity or script-heavy plug-ins does, the main CPU thread is the likely bottleneck.
VRAM pressure behaves differently: texture loading pauses, sudden frame-time spikes, black frames and eventual device errors are stronger clues than a permanently low frame rate. Always repeat the test with a default aircraft, because aircraft-specific displays and embedded plug-ins can create judder even when the same airport is smooth in another cockpit.