How do I fix broken or missing water textures in FSX?

To fix broken or missing water textures in FSX or FSX: Steam Edition, first identify whether the fault is global or regional. Disable DirectX 10 Preview, clear the shader cache and restore stock files for global faults. If only one coastline is affected, troubleshoot that area’s scenery layers, exclusions and terrain data instead.

Is this really a missing water texture?

The pattern of the fault usually reveals whether FSX has damaged water textures, a rendering problem or faulty local scenery. A mistake we see often is replacing global textures when the simulator has actually lost the terrain polygons that define where water belongs.

Very dark water under heavy cloud or at night can be normal in FSX. A sharply bounded black square, repeated blank tile or bright white sheet is not.

How do I restore the default FSX water textures?

The safest repair is to return FSX to its stock rendering state before installing any replacement texture package.

1. Back up your modifications. Copy any files you deliberately installed in FSX’s main Texture folder to a safe location. Do not add another water package while diagnosing the existing one.
2. Disable DirectX 10 Preview. Clear the Preview DirectX 10 option in the display settings, close FSX completely and launch it again. If your installation does not show this option, move to the next step.
3. Rebuild the shader cache. With FSX closed, open %LOCALAPPDATA%\Microsoft. In the active FSX profile—or FSX-SE on some side-by-side Steam installations—rename the Shaders and Shaders10 folders if present. FSX creates fresh caches when it next starts.
4. Restore stock files. In FSX: Steam Edition, open the simulator’s Steam properties and run the installed-file integrity check. For boxed FSX, use the original installer’s Repair option when available. Our stock-file recovery checks for FSX cover the repair choices and their limitations.
5. Run a controlled test. Load a default coastal airport in daylight with default scenery and ordinary weather. If the water is normal, restore add-ons one at a time until the fault returns.

Steam verification can overwrite modified default textures, but it does not necessarily remove extra files deposited by a third-party installer. Keep backups of intentional modifications and inspect the affected add-on if verification succeeds but the symptom remains.

If boxed FSX offers no Repair option, a clean reinstall is the reliable way to recover unknown stock files. Back up add-ons and configuration files first. For an Acceleration installation, preserve the correct base-simulator and Acceleration update sequence rather than mixing Acceleration with a separate SP2 installation.

What if water is missing around only one airport or coastline?

A fault confined to one region is usually caused by local scenery, scenery priority or missing terrain data—not FSX’s worldwide water textures.

1. Identify the exact area. Test inside and outside the affected region so you know whether the boundary matches an installed scenery package.
2. Disable the suspected scenery. Untick the newest or highest-priority entry covering that location in the Scenery Library, apply the change and restart FSX before retesting.
3. Inspect the installation. Confirm that the add-on’s scenery folder and any required texture folder were copied to the intended location.
4. Check overlapping products. If two add-ons supply coastlines, lakes or terrain vectors for the same area, correct their library priority or use only one set of conflicting files.
5. Repair missing library entries. If the scenery files exist but FSX is not loading them, follow our guidance for recovering disabled or misregistered Scenery Library entries.

When water has turned into land, changing ocean colours cannot fix it. Coastlines and water boundaries come from terrain scenery; use the checks for damaged terrain data, exclusions and coastline files instead.

What if it didn't work?

If the first repair did not work, confirm that you classified the symptom correctly and changed the FSX installation you actually launch.

• Check the installation path. Older texture installers may target the traditional boxed-FSX folder even when Steam Edition is installed elsewhere. Locate the active fsx.exe and verify that any manual repair was applied beneath that simulator root.
• Remove leftover add-on files. File verification restores recognised stock files but may leave unknown shader, effect or texture files behind. Reverse the most recent visual modification using its backup or uninstaller; do not delete unfamiliar files at random.
• Test a fresh configuration. Back up the active FSX.CFG under %APPDATA%\Microsoft\FSX, or %APPDATA%\Microsoft\FSX-SE where applicable, then rename it and launch FSX. This resets graphics and simulator preferences but does not remove installed aircraft or scenery.
• Reinstall only as a last resort. A clean reinstall is justified when stock water remains broken worldwide after shader, configuration and file-repair checks. Test the untouched simulator before copying any add-ons back.

Why is the water still black or white?

Persistent black or white water with intact stock files normally indicates a rendering or shader fault rather than a missing image. Keep DirectX 10 Preview disabled, remove third-party shader changes and temporarily lower Water Effects by one step. If that restores recognisable water, the effect-rendering path—not the underlying water texture—is the problem.

Should I install replacement water textures?

Install replacement water textures only after stock water works correctly. A replacement set can change colour, wave detail and shoreline appearance, but it cannot restore missing water polygons or cure a DirectX 10 shader problem.

• Back up every stock file the package will replace.
• Confirm that the package is for FSX or FSX: Steam Edition, not FS2004 or another simulator.
• Check that an older installer selected the active FSX root rather than an unused boxed-edition folder.
• Install one water set at a time; combining packages can leave mismatched colours, wave textures and shoreline transitions.

If a replacement installer reported success but nothing changed, the usual causes are the wrong destination folder, blocked file permissions or another package overwriting the same files. Resolve that installation problem rather than repeatedly merging more textures into the main Texture folder.