See what anti-aliasing, mipmapping and mipmap LOD bias do, when to keep mipmapping on, and how to fix blurry or shimmering flight sim textures.
In flight simulators, anti-aliasing smooths jagged geometry and stabilises thin edges, while mipmapping uses progressively smaller texture copies as objects recede. Keep mipmapping on in almost every 3D sim; use anti-aliasing for stair-steps and edge shimmer, and anisotropic filtering for blurry runways or terrain viewed at shallow angles.
This is general guidance for PC, console and mobile flight simulators. Older engines may expose separate switches or sliders, while newer renderers often manage mipmaps internally and offer anti-aliasing through named modes or broad quality presets.
How do anti-aliasing and mipmapping differ?
Anti-aliasing works mainly on sampled image edges, whereas mipmapping controls how much texture detail is used at different distances.
| Technique | Main job | Use it to address |
|---|---|---|
| Anti-aliasing | Smooths or stabilises edges in the rendered image | Jagged wings, crawling cockpit lines, shimmering aerials and unstable building edges |
| Mipmapping | Selects smaller texture copies as surfaces recede | Sparkling terrain, noisy runway markings and flickering distant liveries |
| Anisotropic filtering | Preserves mipmapped detail on angled surfaces | Runways, taxiways and terrain becoming blurry towards the horizon |
The distinction is easiest to see in motion. A jagged aircraft silhouette points to anti-aliasing; texture detail that sparkles as you taxi points to mipmaps or LOD bias; a runway that is sharp beneath the aircraft but blurred farther ahead points to anisotropic filtering.
What does anti-aliasing do?
Anti-aliasing reduces stair-step edges and frame-to-frame shimmer caused by representing diagonal lines, curves and fine geometry with a limited pixel grid.
- MSAA samples polygon edges multiple times and can retain a crisp image. It may not treat transparent textures, shader detail or all artefacts produced by a deferred renderer.
- TAA combines information from successive frames. It is effective against movement shimmer, but a weak implementation can soften cockpit displays or leave trails behind moving objects.
- DLAA or another native-resolution temporal mode uses temporal reconstruction without intentionally lowering the internal resolution. Availability depends on the simulator, graphics hardware and renderer.
- FXAA is an inexpensive post-processing method. It smooths visible edges but can blur fine instrument lettering because it cannot reliably distinguish text from an unwanted edge.
- Supersampling or increased render scale renders more pixels before reducing the image to the display resolution. It improves geometry and fine texture stability at a substantial GPU cost.
No single option is best in every simulator. Choose temporal anti-aliasing when shimmer during camera movement is the main problem; choose a well-supported MSAA mode when crisp cockpit detail matters and the renderer suits it. Our step-by-step anti-aliasing and shimmer guide covers those choices in more depth.
Anti-aliasing cannot restore detail lost to a low display resolution, aggressive dynamic resolution or a low internal render scale. Temporal upscaling may include anti-aliasing, but the reconstructed result can still look softer than native rendering.
What does mipmapping do, and should it be on or off?
Mipmapping should normally be on because it prevents a large, detailed texture from being squeezed unstably into a few distant pixels.
A mipmapped texture contains a chain of progressively smaller copies. The renderer chooses between them according to the texture's projected size, then blends or filters the result. Without suitable mip levels, runway paint, roof tiles, terrain and aircraft markings can produce moiré patterns, sparkle and crawling noise.
The original full-resolution texture remains available nearby, so enabling mipmaps is not the same as lowering maximum texture resolution. A conventional complete mip chain adds roughly one-third to the base texture's storage when every level uses the same format, although the simulator's streaming system decides which levels remain in graphics memory.
Leave mipmapping enabled or set to application-controlled. Exceptions such as two-dimensional menus, HUD elements and specially rendered cockpit displays are normally handled by the asset creator or engine rather than by disabling mipmaps globally. See our full explanation of when flight-sim mipmaps should be enabled for the asset-level caveats.
What is mipmap LOD bias?
Mipmap LOD bias shifts the renderer's choice towards a sharper or blurrier mip level than it would normally select.
| LOD bias | What it usually does | Likely result |
|---|---|---|
| Negative | Keeps a higher-resolution mip visible farther away | Sharper detail, but increased texture shimmer and aliasing |
| Zero or default | Uses the renderer's intended mip selection | The safest balance of clarity and stability |
| Positive | Selects smaller mip levels sooner | More blur, but less distant texture noise |
The sign convention above is standard, but a simulator may present the same control as a quality slider with different wording. A negative mipmap bias does not create new detail; it merely requests a larger existing mip level. Excessive negative values often look impressive in a still image and much worse during taxi or a camera pan.
Should texture filtering negative LOD bias be on or off?
Keep negative LOD bias off or clamped unless the simulator explicitly requires it for its anti-aliasing or upscaling method.
A driver control may call the choices Allow and Clamp rather than on and off. Clamping helps prevent applications from choosing overly sharp mip levels, but modern rendering APIs and shader-based texture sampling may ignore a driver override. The simulator's own setting is therefore preferable.
Some temporal upscalers use a controlled negative bias to compensate for their lower internal rendering resolution. Let a modern simulator manage that itself. Forcing an additional negative value through the graphics driver can produce the very runway and terrain shimmer that mipmapping is meant to prevent.
How do you control blurry textures without creating shimmer?
Fix blurry textures by identifying whether the softness comes from output resolution, texture streaming, mip selection, angled filtering or the anti-aliasing method before changing LOD bias.
- Check the whole image. If cockpit text, aircraft edges and scenery are all soft, use the display's native resolution and a native-equivalent render scale, often labelled 100%. Check for dynamic resolution or an upscaling quality mode before blaming mipmaps.
- Watch the texture at close range. A surface that starts blurry and turns sharp after a pause suggests texture streaming or graphics-memory pressure. A texture that remains low-resolution when close may be limited by the texture-quality setting, its source file or the add-on itself.
- Examine the viewing angle. If the ground is sharp directly below but blurry farther ahead, raise anisotropic filtering. It works with mipmaps rather than replacing them; our guide to texture filtering, anisotropic filtering and their performance cost explains the practical trade-offs.
- Restore the default mipmap LOD bias. Use zero, neutral or application-controlled as the baseline. Move towards a sharper setting only in small increments and judge the result while the aircraft or camera is moving.
- Compare anti-aliasing modes. TAA and temporal upscalers may soften glass-cockpit text or leave ghosting. MSAA or a native temporal mode can be clearer when supported, while FXAA commonly softens the whole frame.
- Test matching conditions. Use the same aircraft, airport, weather, camera and movement. Our focused checklist for blurry mipmapped textures covers persistent streaming, filtering and add-on problems.
If only one livery, aircraft or scenery package is affected while default content is stable, suspect the asset. It may have missing mip levels, an incomplete chain, unsuitable texture compression or a low-resolution source image. Global sharpening cannot properly repair those faults.
Why can shimmer remain after enabling both?
Persistent shimmer usually comes from detail that ordinary edge anti-aliasing and texture mipmaps do not fully cover.
- Transparent or cut-out textures, including fences, trees and some aerials, may need temporal anti-aliasing or a dedicated transparency treatment.
- Specular highlights and shader detail can flash even when the underlying texture has a correct mip chain.
- Thin geometry and undersampled shadows may require a higher render scale, better temporal treatment or improved shadow settings.
- Sharpening filters can reintroduce halos and pixel-level noise after anti-aliasing has stabilised the image.
- Missing add-on mipmaps cause distant detail to flicker regardless of the simulator's global mipmap setting.
Judge the result during taxi, a low pass and an external-camera pan. Still screenshots hide temporal crawling and can make an aggressive negative mipmap bias appear better than it is.
Is “anti-blur” or “no blur” the same as anti-aliasing?
No: anti-blur and no blur are not standard synonyms for anti-aliasing, and anti-aliasing can itself make an image look slightly softer.
Motion blur, depth-of-field blur, temporal softness, low render resolution and deliberately blurred source media are separate problems. Disable motion blur or depth of field through their own controls when available; use render scale and anti-aliasing choices for general 3D softness. No graphics setting can reconstruct detail that was absent from the source.
Search phrases such as HOT 51 anti blur or HOT 51 no blur do not identify a standard flight-simulator rendering control. If HOT 51 is an app or service displaying compressed or intentionally blurred media, mipmapping and flight-sim anti-aliasing settings will not remove that blur.
What does Airline Commander mode change?
The phrase Airline Commander mode does not describe a standard anti-aliasing or mipmap mode shared by flight simulators.
Mobile simulators such as Airline Commander may hide these individual controls and manage them through the renderer, device profile or a broader performance and quality preset. If a build exposes only broad presets, a quality-oriented mode may increase resolution or texture detail, but its exact components can vary by app version and device. Do not assume it disables mipmaps or selects a particular anti-aliasing technique.
On mobile hardware, thermal or power management can also reduce rendering resolution during a session. If the entire image becomes softer rather than only distant textures, dynamic resolution is a more likely cause than mipmap LOD bias.
Does anti-aliasing fix shimmer on distant horizons?
Anti-aliasing can stabilise a distant skyline, but ground texture noise near the horizon usually needs correct mipmaps, sensible LOD bias and anisotropic filtering.
If the skyline itself is jagged, increase anti-aliasing or render resolution. If terrain patterns sparkle, leave mipmapping on and remove any aggressive negative bias. If the terrain merely loses detail at a shallow angle, increase anisotropic filtering instead.
The same distinction applies to a renderer or add-on named Distant Horizons outside a flight simulator. Use an anti-aliasing method supported by its host application and renderer; forcing a legacy driver override may have no effect. Exact compatibility is application- and version-specific, but anti-aliasing still cannot replace texture mipmaps.
What is a safe graphics baseline?
A safe baseline is native output resolution, application-controlled mipmapping, neutral LOD bias and a simulator-supported anti-aliasing mode.
- Use the display's native resolution and a native-equivalent render scale.
- Choose TAA when movement shimmer is the main problem, or a crisper supported mode when cockpit clarity takes priority.
- Keep mipmapping enabled or automatic.
- Set mipmap LOD bias to zero, neutral or application-controlled.
- Use a high anisotropic filtering level if runway and terrain detail blurs at shallow angles.
- Set texture quality high enough for the source assets, but within available graphics memory to avoid delayed loading and stutter.
- Leave driver overrides application-controlled unless the simulator's documentation calls for a specific setting.
Change one control at a time. The target is not maximum sharpness in a parked screenshot, but a stable image in motion with readable instruments, clean aircraft edges and terrain that does not crawl towards the horizon.