Fix jagged edges and shimmering in X-Plane 12 using anti-aliasing, native resolution, upscaling checks and GPU-friendly settings.
Jagged edges in X-Plane 12 are aliasing, usually caused by low anti-aliasing, reduced internal rendering resolution, or running the simulator below the monitor’s native resolution. Use native resolution, disable performance upscaling, then increase anti-aliasing gradually. Stop at the highest setting your GPU can sustain without unstable frame rates.
Fix X-Plane 12 jagged edges in five steps
- Identify the type of jagged edge. Stair-stepped aircraft outlines, window frames and runway markings indicate aliasing. Blocky moving shadows come from shadow maps, while a soft or pixelated whole image usually means the scene is being rendered below the display’s resolution.
- Use the monitor’s native resolution. Select the panel’s actual pixel resolution in X-Plane’s display controls. Anti-aliasing cannot fully restore detail lost when a lower-resolution image is enlarged to fit the screen.
- Remove reduced-resolution scaling. If your X-Plane build exposes an internal rendering-resolution or FSR control, set it to native, full resolution or
100%as applicable. The wording varies between releases. Performance upscaling raises frame rates but can make thin geometry, runway lines and distant buildings crawl or shimmer. - Increase anti-aliasing one level at a time. Start with
2x MSAAwhere available, test, and then try4x MSAA. Higher levels have rapidly diminishing returns and can impose a substantial GPU cost, especially at 4K or with complex weather. - Test the same view after every change. Use a demanding airport, daylight and a slowly moving external camera. Check both image stability and X-Plane’s CPU/GPU frame times. If the GPU becomes the limiting factor, reduce GPU-heavy cloud or shadow settings before sacrificing native rendering resolution; our GPU-focused X-Plane FPS tuning advice explains the trade-offs.
Which X-Plane 12 anti-aliasing setting should I use?
Use native rendering resolution first, then choose the least expensive anti-aliasing option that keeps aircraft and airport edges acceptably smooth. Available names can differ between X-Plane updates and hardware platforms, but the practical choices are usually these:
| Option | Choose it when | Main trade-off |
|---|---|---|
None | Diagnosing performance or using an exceptionally high-resolution display | Maximum frame rate, but obvious stair-stepping |
FXAA | GPU headroom is limited and a low-cost treatment is needed | Softens visible edges but may blur cockpit text and does little for distant shimmer |
2x MSAA | You want a sensible balance at native resolution | Cleaner geometry with a moderate GPU cost |
4x MSAA | The GPU has spare frame time and geometry edges remain distracting | Better edge quality, but a noticeably heavier load |
| Higher MSAA | Frame rate remains comfortably stable after testing | High cost for increasingly small visual gains |
A mistake we see constantly is reducing internal resolution to afford very high MSAA. Native resolution with moderate anti-aliasing normally looks cleaner than an upscaled low-resolution image with an expensive AA setting.
Why do some edges still shimmer with anti-aliasing enabled?
MSAA mainly smooths polygon boundaries; it cannot eliminate every source of temporal shimmer. Thin fences, vegetation, distant buildings, roof textures, painted lines and bright reflections can become smaller than a screen pixel, so they flicker as the camera moves.
- Texture shimmer: Use a suitable anisotropic-filtering level for surfaces viewed at shallow angles. This improves runway and terrain texture clarity but does not replace anti-aliasing.
- Shadow stair-stepping: Raise shadow quality only if the jagged area follows a moving shadow. Standard anti-aliasing has limited effect on shadow-map resolution.
- Excess sharpening: Disable or reduce driver-level and display sharpening while testing. Sharpening can exaggerate halos, runway-line flicker and distant building shimmer.
- Add-on-specific artefacts: Compare the location with a default aircraft and default scenery. If the problem occurs only with one add-on, its geometry, materials or level-of-detail transitions are probably responsible.
If the image is also blurry, grainy or poorly textured, work through our broader X-Plane image-quality checks rather than continuing to raise MSAA alone.
Can graphics-driver settings or Zink remove jagged edges?
Leave driver anti-aliasing set to application-controlled because forced overrides often have no useful effect on X-Plane 12’s Vulkan or Metal renderer. Driver sharpening can worsen the symptom, so return custom graphics-profile settings to neutral before comparing X-Plane options.
Zink does not improve X-Plane’s native anti-aliasing. It concerns how compatible OpenGL plug-ins are presented through Vulkan, so investigate Zink and plug-in rendering compatibility only when the jagged or corrupted image is confined to a plug-in-drawn panel, window or instrument.
What if the jagged edges appear only in VR?
VR edge quality depends heavily on the per-eye rendering resolution selected by the headset runtime, not just X-Plane’s desktop anti-aliasing control. Increase the runtime render scale cautiously, then balance it against MSAA because both are expensive. Our VR resolution and supersampling checks cover headset-specific blur, shimmering and performance limits.