Where can you still get Steve's DX10 Scenery Fixer for FSX?

Status checked 26 October 2026: Steve’s DX10 Scenery Fixer V5 is still sold for Microsoft Flight Simulator X through the developer-authorised simMarket product listing. Existing customers should sign in to the purchasing account and reopen the order to download it. Mirrors, archive uploads and second-hand keys are not legitimate new-download routes.

Where can you buy or re-download Steve’s DX10 Scenery Fixer?

New licences and replacement downloads should come from the authorised Steve’s FSX Analysis – DX10 Scenery Fixer V5 listing or the account that originally supplied your licence.

A copied installer does not establish a licence and may be an obsolete build intended for a different FSX edition. If the authorised listing later stops accepting orders, there is no fallback public download: mirrors do not become legitimate when new sales end. Our earlier technical account of the Fixer and its original purchasing arrangement is useful historical context, but old retail details should not override the route above.

What is the FSX DX10 Fixer, and what does it repair?

Steve’s DX10 Scenery Fixer is a commercial shader and compatibility utility for FSX’s unfinished DirectX 10 Preview renderer.

It addresses DX10-specific shader, material, transparency, lighting, shadow and scenery-rendering defects, including some problems encountered when older aircraft or scenery use legacy materials. It does not install a new graphics engine or make every FS2004-era add-on fully DX10 compatible.

Users who keep FSX in its normal DX9 mode generally do not need it. Our explanation of how DX10 Preview differs from FSX’s established DX9 renderer can help determine whether enabling it is worthwhile for your installation.

Required FSX version and Fixer release

Use the documented V5 release and all updates supplied through your licensed account; do not install an old pre-Steam build simply because its installer is available elsewhere.

The Fixer’s corrections operate only when Preview DirectX 10 is enabled. FSX Deluxe at its original release level or SP1 alone is not the correct boxed-FSX baseline.

How should you install DX10 Scenery Fixer safely?

A safe installation starts with a known FSX build, stock shaders and backups that let you return to the previous renderer configuration.

1. Confirm the simulator edition and path. Locate the FSX.exe that you actually launch. Check whether it belongs to boxed FSX or Steam Edition, particularly if both have been installed on the same PC.
2. Verify the boxed-FSX service level. Install SP2 or Acceleration before the Fixer. Steam Edition does not use the boxed service-pack installers.
3. Return to a clean shader baseline. Remove or reverse earlier shader replacements according to their own instructions. Stacking unrelated shader modifications makes both diagnosis and rollback unreliable.
4. Back up the configuration and shaders. Copy the active FSX.cfg and the simulator installation’s ShadersHLSL folder. Boxed FSX normally stores its configuration at %APPDATA%\Microsoft\FSX\FSX.cfg. A side-by-side Steam installation may instead use %APPDATA%\Microsoft\FSX-SE\fsx_se.cfg.
5. Identify the generated shader cache. It is normally under %LOCALAPPDATA%\Microsoft\FSX\Shaders10, or the corresponding FSX-SE folder in a side-by-side setup. Close FSX before renaming or removing this cache.
6. Install only the licensed V5 build. Follow the order and update instructions supplied with that release rather than mixing files from different versions. Our boxed-FSX and Steam Edition setup guidance covers the installation decisions in more detail.
7. Test stock content first. Enable DX10 Preview, restart FSX and load a default aircraft at a stock airport. Add third-party aircraft, scenery and other shader tools only after that test is stable.

Rollback procedure

Rollback means restoring the original shaders and configuration, rebuilding the shader cache and returning FSX to DX9 if instability remains.

1. Use the Fixer’s documented restore or uninstall process. Do this before manually overwriting files.
2. Restore your backups if required. Put back the original ShadersHLSL folder and FSX.cfg only when FSX is closed.
3. Rebuild the generated cache. Rename the active Shaders10 folder so FSX creates a clean one at the next launch. Keeping the renamed folder temporarily is safer than deleting it immediately.
4. Disable DX10 Preview. Restart FSX and test the same stock aircraft and airport in DX9.

How do you switch FSX back to DX9?

Clear Preview DirectX 10 in the Graphics settings and restart FSX; DX9 is the automatic fallback and does not require a separate installation.

1. Open Display settings. From the FSX opening screen, choose Settings > Customize under Display, then open the Graphics tab. From a running flight, use Options > Settings > Display.
2. Clear Preview DirectX 10. Select OK or apply the setting so FSX saves the change.
3. Exit FSX completely. Reopen it before judging the result.
4. Repeat a controlled test. Start with a default aircraft at a stock airport, then load the aircraft or scenery that originally failed.

If stock content and the affected add-on work in DX9 but fail in DX10, the fault is probably tied to DX10 Preview compatibility. If the same problem remains in both renderers, investigate the add-on rather than installing another shader patch.

Will Steve’s DX10 Fixer repair missing textures or broken add-ons?

No. The Fixer cannot replace absent files, repair a corrupt model or correct an installer that placed an aircraft or scenery package in the wrong folder.

A mistake we see constantly is treating every missing surface as a DX10 shader fault. Bad texture names, incomplete downloads, missing model files and installers aimed at the wrong FSX path remain broken after the Fixer is installed. DX9 plus a stock-content test is the quickest way to separate those add-on faults from a genuine DX10 Preview problem.