What are mipmaps, and should I enable them in a flight simulator?

Mipmaps are prefiltered, progressively smaller copies of a texture that a graphics engine uses as the textured surface occupies fewer screen pixels. In flight simulators, keep them enabled or engine-managed: they suppress distant runway and scenery shimmer, reduce moiré patterns and improve texture-cache efficiency, with modest extra storage.

This is general flight-simulator guidance rather than advice for one title. Microsoft Flight Simulator, X-Plane, Prepar3D and other engines may manage mipmaps automatically, so the absence of a dedicated setting usually means there is nothing to enable manually.

What are mipmaps and how do they work?

Mipmaps form a chain of successively reduced images derived from the original texture. A 1024 × 1024 texture might have a 512 × 512 level, then 256 × 256, continuing down to 1 × 1. The full-resolution image is commonly called level 0; higher-numbered levels are progressively smaller.

The renderer estimates how much screen space a textured surface occupies and samples an appropriate level. Without this prefiltered chain, a distant runway marking, roof or field may cover only a few screen pixels while containing thousands of alternating source texels. Those details then appear and disappear as the camera moves, producing sparkle, crawling edges and moiré patterns.

Trilinear filtering blends between adjacent mip levels so that the change is less visible. Anisotropic filtering preserves more detail when a surface is viewed at a shallow angle, which is especially relevant to runways and terrain extending towards the horizon. Our explanation of texture filtering and anisotropic filtering on distant detail covers that relationship.

A simulator setting labelled simply LOD often controls object detail or draw distance, not mipmaps. Do not assume it is a mipmap control unless its description specifically mentions texture LOD, mip levels or LOD bias.

Should I enable mipmaps in a flight simulator?

Yes, ordinary aircraft, terrain, runway and scenery textures should use mipmaps unless the simulator or add-on documentation explicitly requires otherwise.

• Use engine-managed mipmaps in simulators that do not expose a separate switch.
• Leave mipmaps enabled for exterior aircraft textures, buildings, vegetation, ground polygons and terrain.
• Disable them only as a temporary test when one legacy add-on is blurred, haloed or unstable. Restore the setting after identifying the fault.
• Do not disable them globally to sharpen one cockpit label. Gauges, displays and interface elements can follow different sampling rules from exterior 3D textures.

If default content looks stable but one aircraft or scenery package shimmers, the package may have missing or badly generated mip levels. A driver setting cannot reconstruct correct alpha coverage, edge padding or normal-map data from a defective asset.

What does shimmering mean in graphics?

Shimmering means fine detail appears to sparkle, crawl or flicker from frame to frame as the viewpoint moves. It is a form of temporal aliasing: the renderer cannot represent changing sub-pixel detail consistently.

Texture shimmer is common on distant runway markings, fences, roofs and detailed ground textures, and mipmaps are one of its main remedies. Not every shimmering artefact is caused by textures, however:

• Texture aliasing usually improves with correct mipmaps, trilinear filtering and anisotropic filtering.
• Geometry-edge aliasing may require anti-aliasing, a higher render scale or a different upscaling mode.
• Specular shimmer can come from overly strong normal maps or very sharp reflections.
• Alpha-cutout shimmer on trees, fences and grass often indicates poor alpha coverage in reduced mip levels.
• Z-fighting produces flickering where two surfaces occupy nearly the same position; mipmaps will not fix it.

Judge shimmer while taxiing or flying, not from a paused screenshot. Aggressive sharpening and negative LOD bias can look impressive in a still image while producing severe crawling in motion.

What is mipmap LOD offset?

Mipmap LOD offset, also called mipmap LOD bias, shifts the renderer towards a finer or coarser mip level than it would normally select. In the usual convention, a negative value sharpens textures and a positive value softens them.

A simplified way to express the calculation is selected LOD = calculated LOD + bias. Because level 0 is the full-sized texture, adding a positive bias moves towards higher-numbered, smaller images. Some utilities present this as a sharpness slider rather than a signed number, so read the control description before changing it.

Which mipmap LOD offset should I use?

Use a neutral offset and application-controlled driver settings first. Increase anisotropic filtering before applying a negative LOD bias; anisotropic filtering improves runway and terrain detail at shallow angles without indiscriminately forcing sharper mip levels everywhere.

A small negative offset can help a particular older renderer, but excessive values are a common cause of crawling taxiway lines and sparkling ground textures. Some graphics drivers can clamp negative LOD bias to reduce that problem. If a legacy simulator depends on driver overrides, our guide to suitable NVIDIA driver settings for older simulators explains the relevant texture-filtering controls.

A positive offset may calm an unstable texture, but it treats the symptom by making the image softer. Correctly generated mip levels are preferable when the affected add-on can be repaired.

Why do mipmaps sometimes make textures blurry?

Mipmaps look too blurry when the renderer selects a level that is too coarse or when the reduced images were generated badly. Low anisotropic filtering, positive LOD bias, reduced texture quality, VRAM pressure and delayed texture streaming can all produce similar symptoms.

1. Establish the scope. Compare default aircraft and scenery with the affected add-on. One defective package points to its texture assets; widespread blur points to a simulator, driver or performance setting.
2. Reset LOD and driver overrides. Return mipmap bias, filtering and sharpening controls to neutral or application-controlled values.
3. Check source texture quality. A low global texture-resolution setting limits close-range detail before mip selection is considered.
4. Use trilinear and anisotropic filtering. This reduces visible transitions and improves surfaces viewed towards the horizon.
5. Check memory pressure and streaming. An engine may retain coarse mip levels while higher-resolution data is being loaded or when the texture budget is exceeded.
6. Separate texture blur from whole-frame blur. If cockpit text, aircraft edges and menus are also soft, investigate render scale, dynamic resolution or upscaling rather than mipmaps.
7. Test in motion. Choose the setting that remains stable while taxiing and turning, not the one that looks sharpest in a single frame.

For a focused diagnosis of an aircraft, runway or scenery package that becomes excessively soft, use our mipmapped-texture troubleshooting checklist.

What goes wrong when creators generate mipmaps?

Most add-on mipmap faults originate in the asset pipeline rather than the simulator's graphics menu.

• Colour space: base-colour textures should be identified and filtered as colour data, while normal, roughness and metallic maps require linear data handling.
• Normal maps: reduced levels need suitable filtering and normalisation; treating them exactly like ordinary colour images can weaken or distort surface lighting.
• Transparent edges: trees, fences, propeller discs and lettering need sensible RGB colours beyond the visible alpha edge. Otherwise reduced levels can acquire dark or pale halos.
• Alpha coverage: thin alpha-tested details can disappear as the texture shrinks unless the mip-generation process preserves coverage.
• Texture atlases: each island needs enough padded border to prevent neighbouring colours bleeding into smaller mip levels.
• Compression order: generate the chain from a clean master using an appropriate filter, then apply the final texture compression. Reprocessing an already damaged source preserves its artefacts.

Should 3D models for AR previews on a website use mipmaps?

Yes, web-based AR preview models should normally use mipmapped minification for their 3D material textures. AR users inspect objects at changing distances and angles, so an unmipmapped texture that looks acceptable close up may shimmer badly as the model becomes smaller on screen.

GLB and glTF are common delivery choices for web 3D, but a standard PNG or JPEG texture normally contains only its main image rather than a complete mip chain. The browser renderer may generate the chain when uploading the texture, while a supported texture container such as KTX2 can carry precomputed levels. Confirm what the chosen exporter and viewer actually do rather than relying on a checkbox name.

• Use mipmaps for base colour, normal, metallic-roughness and emissive textures on the model.
• Request trilinear minification and use anisotropic filtering where the viewer supports it.
• Prepare alpha textures carefully so hair cards, labels and perforated surfaces do not vanish or develop fringes at a distance.
• Add padding around texture-atlas islands because progressively smaller levels increase the risk of colour bleeding.
• Use power-of-two texture dimensions when an older WebGL 1 fallback must support mipmapping. WebGL 2 removes the older non-power-of-two sampling restriction, but the complete delivery path still needs testing.
• Do not use mipmaps as a substitute for optimisation. Model complexity, source texture resolution, material count and download size still determine how quickly an AR preview loads and runs.

Screen-space page controls and interface text are separate from the model's 3D material textures and do not need the same treatment. If lettering painted onto the model becomes unreadable in its reduced levels, increase its texel density, use a separate material or present it as an overlay rather than disabling mipmaps for the whole object.

Do mipmaps improve frame rate or use more VRAM?

Mipmaps use additional storage but can improve texture-cache behaviour and reduce bandwidth when surfaces are distant. They do not guarantee a higher frame rate; their most dependable benefit is a more stable image.

A complete two-dimensional mip chain occupies roughly one-third more space than the original level alone. This follows from adding quarter-sized levels: 1 + 1/4 + 1/16 + ..., which approaches 4/3. Compression blocks, tiny final levels and engine packaging can change the exact figure.

The whole chain is not necessarily resident in graphics memory at once. Streaming engines can load only the mip levels needed for the scene and available texture budget. In most flight simulators, clouds, shadows, reflections, traffic and render resolution have a larger direct frame-rate cost, so disabling mipmaps is rarely a sensible performance measure.