How do I fix shimmering or shaky VR in X-Plane 12?

To fix shimmering, flickering lines or shaky VR in X-Plane 12, first identify whether you are seeing distant-edge aliasing, Virtual Desktop compression artefacts, frame-time judder, tracking shake or rendering instability. Stabilise tracking and frame delivery first; then tune anti-aliasing, headset resolution, streaming bitrate and sharpening one setting at a time.

Is it shimmer, judder or head-tracking shake?

The appearance and timing of the fault usually reveal which part of the VR chain is failing. A mistake we see constantly is increasing anti-aliasing when the entire cockpit is moving because tracking or frame delivery is unstable; the extra GPU load can make that shake worse.

How do I stop X-Plane 12 VR from shimmering or shaking?

Fix tracking and frame delivery before increasing image quality. Use the same aircraft, airport, weather and viewing direction for every comparison so that one change does not hide another fault.

1. Establish a clean baseline. Load a default aircraft at a simple default airport with uncomplicated weather. Return the headset runtime's per-application render scale and, when applicable, Virtual Desktop's streaming quality, bitrate and codec selection to their default or automatic baselines. Disable dynamic resolution, extra sharpening, third-party foveated rendering and post-processing. Also disable conflicting OpenXR or SteamVR overlays, monitoring overlays and capture tools.
2. Remove add-on variables. Close X-Plane and temporarily move third-party plug-in folders out of Resources/plugins. Do not diagnose the fault with a complex aircraft whose displays or embedded plug-ins may be consuming the main CPU thread. Our VR setup, runtime and view-centring checklist covers the initial headset configuration.
3. Fix tracking before graphics. Clean the headset's tracking cameras or sensors, use even room lighting, remove strong reflections and direct sunlight, and ensure external tracking stations are secure and unobstructed where applicable. Re-centre the seated view. For a wired headset, bypass an unpowered USB hub, extension cable or questionable adaptor during testing.
4. Create stable frame times. Temporarily lower anti-aliasing and headset render resolution. Reduce world-object density, traffic and complex plug-ins when the main CPU thread is late; 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.
5. Tune shimmer only after the view is stable. Increase X-Plane's anti-aliasing by one step and retest the identical scene. If performance allows, restore headset render resolution in small increments. During diagnosis, change only one of these per test: headset render resolution, Virtual Desktop codec bitrate or X-Plane anti-aliasing. The X-Plane 12 graphics-setting trade-offs explain which controls affect clarity, GPU time and VRAM.
6. Test reprojection both ways. Motion smoothing can make a consistently low frame rate feel smoother, but it can also produce doubled wings, distorted propellers and wobbling cockpit frames. If performance repeatedly crosses the reprojection threshold, lower the rendering load or select a lower headset refresh rate where supported.
7. Reset preferences only after isolating the fault. Back up and rename Output/preferences, then let X-Plane generate clean preferences. This resets graphics, views and control assignments, so recalibrate before restoring individual files. If the problem began after a driver change, use the hardware vendor's stable recommended driver or return to the previously working version.

Using Virtual Desktop with X-Plane 12 VR

With Virtual Desktop, first determine whether the defect is encoded into the streamed image or rendered by X-Plane itself. Compression cannot be cured with anti-aliasing, while genuine geometry aliasing will not disappear simply because bitrate is raised.

Streaming artefacts often look like mosquito noise around runway lettering, blockiness in clouds, smeared ground detail or fine lines that pulse as the view moves. X-Plane aliasing stays attached to a fence, roof, runway marking or other geometric edge and normally responds to anti-aliasing or render resolution. If the defect is visible in the desktop mirror or an X-Plane capture, it is probably being produced before streaming, although compositor-only effects may not appear in the mirror.

1. Stabilise the Wi-Fi path. Connect the PC to the router or access point by Ethernet where possible. Keep the headset near the access point on a clean, supported 5 GHz or 6 GHz band, avoid mesh or wireless backhaul during diagnosis, and pause downloads, cloud synchronisation, video streaming and other competing traffic.
2. Start with default streaming settings. Use Virtual Desktop's automatic or default codec and a conservative bitrate rather than assuming the maximum is best. A more efficient codec may preserve fine detail at a lower bitrate, but only if the PC can encode it and the headset can decode it reliably. Compare codecs one at a time in the same scene.
3. Read the performance overlay. Networking spikes point towards Wi-Fi congestion or packet delivery problems. High Encoding time implicates the PC's video-encoding path; high Decoding time implicates headset workload. If Game or the runtime frame time is late, use the CPU-versus-GPU checks below rather than raising bitrate.
4. Separate judder from compression. A clean image that doubles or bends during head movement usually indicates reprojection, not poor Wi-Fi. Follow the motion-smoothing test below. If the whole image stalls while Networking rises, troubleshoot the stream before changing X-Plane's graphics.

After the baseline is stable, increase bitrate only until extra detail no longer causes network, encoding or decoding spikes. Raising bitrate, headset resolution and X-Plane anti-aliasing together makes it impossible to identify which stage has exceeded its budget.

Flickering lines in X-Plane 12 VR

Lines locked to distant geometry usually indicate aliasing or shadow crawl; lines confined to one eye, crossing the display or appearing with black frames indicate a headset, runtime, link or GPU fault. Reprojection sits between these cases: it tends to bend or duplicate lines during head movement rather than make a fixed edge sparkle continuously.

1. Make the aircraft stationary. Use a default aircraft in daylight at a simple airport. Pause X-Plane and hold your head still. If a distant fence or roof edge continues to crawl while the cockpit remains fixed, investigate anti-aliasing, resolution and shadows.
2. Compare the headset with the desktop image. A line visible in both is likely coming from X-Plane, scenery, a plug-in or the rendering driver. A fault visible only inside the headset points more strongly towards the compositor, Virtual Desktop stream, wired link or headset display.
3. Move your head slowly. Lines that bend around cockpit frames, propellers or wings only during motion are characteristic reprojection artefacts. Test motion smoothing off briefly and check frame times; do not leave it disabled if the result is uncomfortable.
4. Remove streaming and overlay variables. If using Virtual Desktop, restore its default codec and bitrate and repeat the stable-network test above. Disable third-party post-processing and OpenXR or SteamVR overlays. For a wired connection, reseat the cable and try a direct, known-good port without an extension or unpowered hub.
5. Stop on one-eye flashes or device loss. Repeated one-eye flashes, coloured or full-width lines, black frames, runtime disconnections and device-loss errors are not normal aliasing. Exit X-Plane and troubleshoot the runtime, driver and physical connection before continuing. Restore stock GPU settings if it is overclocked or undervolted.

After a crash or device-loss event, copy Log.txt from the X-Plane folder before launching the simulator again, because a new session replaces the previous log. Look near the end for plug-in failures, memory pressure, Vulkan errors or a lost graphics device. Persistent black frames or device errors require the broader X-Plane 12 crash and driver 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 sustain the headset's native refresh rate or its visual distortion is worse than ordinary judder. Repeated switching between native and reprojected modes often 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 looks acceptable. Reprojection cannot repair tracking loss or a congested Virtual Desktop connection.

Why does VR shimmer mostly at airports or at night?

Airports and night scenes expose shimmer because they contain many thin, bright and high-contrast details that become smaller than one headset pixel at a distance. Fences, light poles, roof edges, runway markings and point-like lights therefore reveal aliasing more readily than broad terrain.

Moderate anti-aliasing and higher fixed render resolution reduce the effect but cannot remove every sub-pixel artefact. Anisotropic filtering improves oblique runway and ground textures; it does not cure geometry aliasing. If the shimmer follows shaded edges rather than the object itself, reduce scenery shadows as a test.

What if changing anti-aliasing or resolution changes nothing?

If anti-aliasing and render resolution make no visible difference, stop increasing them because the fault is probably not ordinary geometry aliasing. Check where the effect appears and what makes it change.

• Only in the headset: investigate Virtual Desktop compression, the wired link, runtime, compositor or headset display.
• Only while moving your head: inspect reprojection, tracking and frame-time spikes.
• Where two surfaces overlap: suspect z-fighting in scenery or an aircraft model.
• On textures rather than edges: suspect texture filtering, paging, sharpening or conflicting scenery.
• Along moving shadow boundaries: test with scenery shadows reduced or disabled.

For flicker reproduced on the desktop image, our texture flicker diagnostic separates aliasing from z-fighting, texture paging and conflicting surfaces.

How can I tell whether VR judder is CPU- or GPU-limited?

A large improvement after lowering headset resolution or anti-aliasing indicates a GPU limit; little change until world objects, traffic, aircraft complexity or script-heavy plug-ins are reduced points to the main CPU thread. Where X-Plane or the runtime exposes CPU and GPU frame times, the consistently higher value identifies the limiting side.

Virtual Desktop adds another stage. If X-Plane's game frame time is stable but Encoding rises, reduce GPU load, streaming resolution or codec complexity rather than cutting world objects. If Networking rises while game and encoding remain stable, the Wi-Fi path is the problem.

VRAM pressure behaves differently from a simple GPU limit. Texture-loading pauses, abrupt 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.