Install and configure DX10 Fixer for FSX or Steam Edition safely, with prerequisites, baseline settings, shader-cache fixes and rollback steps.
To install DX10 Fixer for FSX, update boxed FSX to SP2 or Acceleration, close the simulator, back up its active configuration, then run the Fixer installer against the folder containing fsx.exe. Install the supplied DX10 libraries, enable DirectX 10 Preview in FSX, restart, and test with default settings before adding other graphics tools.
These instructions cover Steve's DX10 Scenery Fixer in Microsoft Flight Simulator X and FSX: Steam Edition. Do not confuse it with older standalone shader packs, which are not interchangeable. If you do not already have the correct licensed package, check our explanation of DX10 Fixer availability and Steam Edition compatibility.
What does DX10 Fixer require?
DX10 Fixer requires an FSX installation that already supports the simulator's DirectX 10 Preview renderer.
- Boxed FSX: install Service Pack 2 or Acceleration. The original release and SP1 alone do not provide the required finished preview components.
- FSX: Steam Edition: do not install the boxed FSX service packs; Steam Edition already contains the relevant simulator updates.
- A working DX9 baseline: run FSX successfully at least once before installing the Fixer. This creates the active configuration and confirms that an unrelated add-on is not already breaking the simulator.
- Original shader files: restore any previous DX10 shader pack before installing the Fixer. Mixing shader modifications is a common cause of black aircraft, square effects and startup failures.
- The correct FSX folder: if boxed FSX and Steam Edition coexist, make sure the installer and controller both target the edition you actually use.
Install DX10 Fixer in FSX step by step
The safe installation order is to establish a clean FSX baseline, protect the active configuration, install the Fixer and only then enable DX10 Preview.
- Locate the active simulator. Find the installation folder that contains
fsx.exe. Do not selectAddon Scenery, the Documents folder or an old FSX installation left on another drive. - Close FSX completely. The simulator must not be running or minimised while its shaders and libraries are changed.
- Back up the configuration. Copy the active
fsx.cfgoutside its AppData folder. Use the Fixer's own backup or restore function as well if that option is included with your release. - Remove conflicting graphics modifications. Restore shader files changed by old DX10 patches and temporarily disable ReShade, ENB-style wrappers or other injectors. They can be reconsidered after the Fixer works by itself.
- Run the supplied installer. Point it to the folder containing
fsx.exe. Allow elevation if Windows blocks writes to a protected installation folder, but do not manually scatter files around the FSX directory. - Install or update the Fixer libraries. With FSX still closed, open the Fixer controller and use its library installation or update command. Button names vary between releases; the controller and libraries must come from the same package version.
- Enable DX10 Preview. Start FSX, open the display graphics settings and select Preview DirectX 10. Close FSX fully and launch it again so the renderer and shader cache are rebuilt correctly.
The first DX10 load can take longer while FSX compiles shaders. Our detailed DX10 setup and configuration notes provide extra background on backups and keeping separate DX9 and DX10 profiles.
How should DX10 Fixer be configured?
Begin with the Fixer's defaults and change one graphics feature at a time, because a heavily customised profile makes faults much harder to isolate.
| Setting | Safe starting point | Why |
|---|---|---|
| Preview DirectX 10 | Enabled | The Fixer affects the DX10 Preview renderer, not normal DX9 mode. |
| Anti-aliasing | Fixer default; graphics driver application-controlled | Competing FSX, Fixer and driver overrides can cause blur, shimmering or no anti-aliasing. |
| Bloom and optional effects | Off or default for the first test | This separates core shader operation from expensive or add-on-dependent effects. |
| Aircraft and scenery shadows | Default, then enable individually | Legacy models can expose shadow and material problems that stock aircraft do not. |
| Water and scenery complexity | Leave unchanged initially | Changing several demanding FSX settings at once disguises the source of lost performance. |
| Optional Fixer features | Defaults | Confirm the base installation before applying specialised shadow or effect options. |
Test first with a stock aircraft at a stock airport in clear daytime conditions. Once that works, test dusk, aircraft lights, rain and one add-on at a time. For the surrounding simulator options, use our FSX graphics-settings guidance for DX10, filtering and anti-aliasing.
How can I tell whether DX10 Fixer is working?
DX10 Fixer is working when DX10 Preview remains enabled, the controller reports the correct libraries for the active FSX installation, and a stock flight loads without missing materials, broken shadows or corrupted effects.
Frame rate alone is not proof. The Fixer repairs limitations and compatibility faults in FSX's preview renderer; it is not guaranteed to increase performance. A newly generated Shaders10 cache under the active FSX local-app-data profile also confirms that FSX has started its DX10 renderer.
Common DX10 Fixer installation problems
Most failures come from the wrong FSX path, mismatched Fixer files, stale compiled shaders or another graphics injector.
| Symptom | Likely cause | Action |
|---|---|---|
| Controller says the Fixer is not installed | Wrong FSX edition or insufficient write access | Confirm the selected folder contains the active fsx.exe, then rerun the installer with elevation if Windows denied access. |
| White, black or grey aircraft and scenery | Stale cache, missing libraries or incompatible add-on materials | Close FSX, reinstall or update the matching Fixer libraries, then rename the active Shaders10 cache and let FSX rebuild it. If only one add-on fails, test that add-on separately. |
| FSX crashes or reports “Could not load Direct3D device” | Damaged configuration, shader conflict or graphics injector | Restore the backed-up configuration or let FSX create a clean one, remove injectors and rebuild the cache. Follow our Direct3D device recovery steps for FSX if the simulator still will not open. |
| Severe shimmering or blurred edges | Conflicting anti-aliasing methods | Return the GPU driver to application-controlled, restore the Fixer's default AA choice and adjust only one control at a time. |
| Performance is lower than DX9 | High AA, shadows, bloom or water settings | Disable optional effects first, then reduce anti-aliasing and shadow demands. Compare using the same aircraft, airport, weather and view. |
When rebuilding shaders, rename or remove only the compiled Shaders10 cache in the active local-app-data profile. Do not delete the source ShadersHLSL folder from the FSX installation.
Can I switch FSX back to DX9?
You can return to DX9 by clearing Preview DirectX 10 in FSX's graphics settings and restarting the simulator; the Fixer normally does not need to be uninstalled merely to fly in DX9.
For complete removal, use the Fixer's restore or uninstall function before running the Windows uninstaller. Do not delete its folders manually, because that can leave patched shader files behind. Restore the original fsx.cfg if necessary and rebuild the appropriate shader cache after changing renderer.