See whether FSX DX10 Preview is worth enabling, what it changes visually, common add-on faults, and how to test it safely.
In FSX and FSX: Steam Edition, DX10 Preview is worth trying if you mainly use default or compatible add-ons, but it is not a universal graphics upgrade. It switches rendering from the mature DirectX 9 path to an unfinished DirectX 10 path, improving shadows, water and lighting while potentially breaking older aircraft, scenery, lights and anti-aliasing.
DX10 Preview was introduced with the SP2/Acceleration-era renderer. A boxed FSX installation therefore needs SP2 or Acceleration for the option to appear; FSX: Steam Edition already includes the relevant core updates. Steam Edition still uses the same fundamentally incomplete preview renderer.
What does DX10 Preview change in FSX?
DX10 Preview changes how FSX draws the scene, not the underlying scenery or texture detail. It does not add higher-resolution textures, denser autogen, new weather or physically based rendering.
| Graphics area | What DX10 Preview changes |
|---|---|
| Shadows and lighting | It can produce more convincing aircraft and virtual-cockpit self-shadowing where the model and graphics settings support it. Lighting and bloom are processed through different shaders. |
| Water | Reflections, highlights and shading can look cleaner or more pronounced, although the result depends heavily on the selected water setting and weather. |
| Textures and scenery detail | The same textures, mesh, autogen and level-of-detail settings are used. DX10 does not make low-resolution source material sharper. |
| Anti-aliasing | The DX10 path handles anti-aliasing differently. Driver profiles created for DX9 may cause jagged edges, excessive blur or no visible effect. |
| Add-on compatibility | Older aircraft, effects and scenery materials designed around DX9 or inherited from FS2004 may display incorrectly. |
The visual difference can be modest in a default daytime flight and much clearer around water, at dawn or dusk, or inside an aircraft that supports virtual-cockpit shadows. DX10 Preview does not make every scene objectively better.
Choose DX10 Preview or DX9
DX10 Preview suits an installation built around default content and add-ons known to support it. DirectX 9 remains the safer choice for a large legacy add-on collection.
- Try DX10 Preview if you want its shadow, water and lighting treatment and can test every aircraft and airport you regularly use.
- Stay with DX9 if a critical aircraft has broken glass, propellers, gauges or lights, or an important airport has flashing or missing ground textures.
- Use DX9 for ENB because FSX ENB configurations generally hook into the DX9 renderer; our explanation of FSX ENB installation and renderer requirements covers that dependency.
- Consider a DX10 correction utility if you prefer the DX10 appearance but encounter recognised Preview bugs. Our breakdown of the faults addressed by the DX10 Scenery Fixer explains its scope and limitations.
The setting is global rather than aircraft-specific. If one indispensable add-on only works properly in DX9, you must either correct that add-on or switch the whole simulator back to DX9 before using it.
Does DX10 Preview improve FSX frame rates?
DX10 Preview is not a guaranteed FPS upgrade. Some GPU and driver combinations handle its shaders more efficiently, while extra shadows, bloom or compatibility problems can erase that gain or make performance worse.
FSX also remains heavily limited by main-thread CPU performance, so changing the graphics API does not cure every stutter or low-frame-rate problem. Use the same aircraft, airport, weather, view and time of day for comparisons; for broader tuning, follow our FSX performance and FPS troubleshooting steps.
How do I enable and test DX10 Preview safely?
Enable DX10 Preview through FSX's display settings, then compare it against DX9 under controlled conditions before changing other graphics options.
- Record a DX9 baseline. Load a representative saved flight and note its appearance, frame rate and smoothness. Check daylight, dusk and night if lighting matters to you.
- Enable the renderer. Open the display or graphics customisation screen and tick
Preview DirectX 10. - Restart FSX. Closing and reopening the simulator ensures that the rendering path and shaders are reinitialised cleanly.
- Test default content first. Use a default aircraft at a stock airport. If that works, test your add-on aircraft, airport scenery, AI traffic and weather in turn.
- Inspect known trouble spots. Look closely at cockpit glass, propeller discs, gauges, runway markings, taxiways, aircraft shadows, navigation lights and night textures.
- Compare performance fairly. Keep traffic, weather, time, camera view and graphics sliders unchanged. The built-in display cycled with
Shift+Zcan show the frame rate.
To revert, untick Preview DirectX 10 and restart FSX. Switching renderers does not alter aircraft, scenery or saved-flight files.
Why do textures, lights or anti-aliasing break?
These faults usually occur because an older add-on relies on DirectX 9 materials, effects or rendering behaviour that DX10 Preview does not reproduce correctly.
- Black or missing surfaces, opaque propellers and faulty glass: test the same aircraft in DX9. If the fault disappears, its model or material definitions are not fully DX10-compatible.
- Flashing runways, taxiways or ground polygons: legacy scenery layering can conflict with the DX10 path. A dedicated fixer may help, but DX9 is the reliable fallback.
- Missing navigation, landing or cockpit lights: older effect files may need DX10-specific correction. Raising graphics sliders will not repair the effect.
- Jagged edges or blur: remove anti-aliasing overrides intended for DX9 and establish a clean baseline with FSX's own anti-aliasing option before creating any DX10-specific driver profile.
- Corruption after changing settings: close FSX and clear the generated
Shaders10cache in the simulator's local app-data profile. FSX rebuilds it at the next launch; do not delete the installed shader source files from the simulator directory.
Our recommendation
Enable FSX DX10 Preview as a reversible compatibility test, not as an automatic quality setting. Keep it if your essential add-ons render correctly and you prefer its shadows, water or lighting. For installations centred on older port-over aircraft, legacy scenery or ENB, DirectX 9 usually provides the more predictable result.