What are the best AMD Radeon settings for FSX?

For FSX and FSX: Steam Edition, use a per-game profile for fsx.exe, let the application control anti-aliasing and filtering, set Surface Format Optimization off, and disable Radeon Boost, Chill, Enhanced Sync, Anti-Lag and Radeon Super Resolution. Run at native resolution, then cap FSX at a frame rate it can sustain.

Recommended AMD Radeon settings for FSX

The best baseline is a conservative profile that preserves FSX image quality without applying modern features designed for faster, GPU-bound games. Radeon Software labels and available controls vary by graphics card and driver release, so leave an unlisted option at its default rather than trying to reproduce it elsewhere.

How should the FSX Radeon profile be configured?

Configure a profile for the actual fsx.exe being launched, not a desktop shortcut or general global profile.

1. Reset only the FSX game profile if it contains old overrides. A full Radeon factory reset is unnecessary and can remove unrelated display settings.
2. Add the correct executable to the Radeon games list. Boxed FSX and FSX: Steam Edition normally use the same fsx.exe name, although their installation locations differ.
3. Apply the baseline values from the table and keep global graphics controls at their defaults wherever possible.
4. Set up FSX itself at the monitor's native resolution, select Anisotropic filtering, enable the simulator's Anti-Aliasing option and begin with a 30 FPS target. Our FSX display-resolution and filtering setup explains the associated in-simulator choices.
5. Restart FSX after changing anti-aliasing, DirectX mode or display mode. Driver overrides are not always applied cleanly to a flight already in progress.
6. Test one change at a time using the same aircraft, airport, weather and view. Comparing a clear rural flight with a complex add-on airport proves very little.

A 30 FPS cap is a sensible first target because consistency matters more than a high number that collapses near major airports. Use 60 FPS only if FSX can sustain it in the demanding flights that matter to you, rather than merely reaching it over empty terrain.

Should AMD Surface Format Optimization be on or off for FSX?

Surface Format Optimization should be off for FSX because the small potential performance saving is rarely worth a format substitution in a legacy DirectX application.

When enabled, the driver may use an alternative surface or texture format where it judges the change acceptable. That can be transparent in many games, but FSX combines old rendering paths with aircraft, cloud, lighting and scenery add-ons written across many years.

If you test it on, examine cloud gradients, smoke, tree and fence transparency, night lighting, water and virtual-cockpit displays. Leave it off if you see banding, colour changes, bright edges or broken transparency. If reducing the display resolution does not improve FPS, this optimisation is especially unlikely to help because the simulator is probably CPU-limited.

Should FSX or Radeon Software control anti-aliasing?

FSX should control anti-aliasing first, with the Radeon profile set to Use application settings and Multisampling where that method is exposed.

Enable Anti-Aliasing in FSX, then inspect aircraft edges, taxiway markings and cockpit geometry. If they remain objectionably jagged, test a modest 2× or 4× driver override. Return to application control if cockpit text or transparent scenery disappears, clouds become markedly slower, or the override simply has no effect.

Morphological Anti-Aliasing is a poor fit because it post-processes the image and can blur the two-dimensional interface as well as the scene. For soft runway and terrain textures, a 16× anisotropic-filtering override is normally safer than forcing heavier anti-aliasing, although it cannot cure flickering trees, fences or aerials.

FSX normally uses DirectX 9, while its optional DX10 Preview follows a different rendering path and can respond differently to driver overrides. Do not enable DX10 Preview solely to make a Radeon option work; older aircraft and scenery may have compatibility problems in that mode.

Should image scaling or sharpening be used in FSX?

Run FSX at native resolution without driver scaling or sharpening unless a clear GPU bottleneck or genuinely soft image gives you a reason to change it.

Radeon Image Sharpening on or off?

Radeon Image Sharpening should be off initially, but a low amount can help when non-native resolution, GPU scaling or a soft display makes the picture look blurred.

Sharpening does not remove aliasing. Applied too strongly, it outlines gauge lettering, intensifies tree and building shimmer, and makes compression or texture noise more visible. Compare runway markings, distant roofs and small cockpit labels before deciding; use the lowest amount that corrects softness without creating bright halos.

Radeon Super Resolution on or off?

Radeon Super Resolution should be off at native resolution because RSR works by upscaling a lower-resolution frame, including FSX panels and instrument text.

Only test RSR if lowering FSX's resolution already produces a meaningful frame-rate increase. That result indicates a GPU bottleneck; if FPS remains unchanged, upscaling will not relieve the main CPU thread. Activation requirements vary with Radeon hardware, driver and presentation mode, but FSX generally must render below the display's native output in a supported full-screen arrangement.

Do not stack aggressive Radeon Image Sharpening on top of RSR's sharpening. The combination can make old scenery textures and thin cockpit lines look brittle even when the outside view appears clearer.

Radeon Boost on or off?

Radeon Boost should be off for FSX because it dynamically reduces rendering resolution during movement in supported games, exactly when readable instruments and stable scenery detail are needed.

FSX may not be supported at all; an absent Boost control for its profile is not an error. Even where the switch appears, Boost does not address a main-thread bottleneck and can make resolution changes visible during panning or cockpit movement.

Radeon Enhanced Sync on or off?

Radeon Enhanced Sync should be off for a normal FSX profile because it is designed chiefly to reduce tearing when frame rates run above the monitor's refresh rate without using conventional VSync behaviour.

Enhanced Sync does not hold FSX at 30 or 60 FPS. At low or variable frame rates it can add another presentation variable without curing CPU stutter, and older applications may show irregular pacing or flicker. Consider it only when FSX consistently exceeds the display refresh rate, visible tearing remains, and ordinary VSync adds latency you can actually detect.

Should I use FreeSync, VSync, a three-frame cap and Anti-Lag?

With a FreeSync monitor, enable FreeSync, use ordinary VSync only as an upper boundary, cap two or three frames below the maximum only when FSX operates near that maximum, and leave Radeon Anti-Lag off.

• FSX locked at 30 FPS on a 60 Hz display: keep the FSX cap at 30, not 57. FreeSync helps only if 30 FPS falls within the monitor's variable-refresh operation or Low Framerate Compensation is available.
• FSX running near 60 FPS on a 60 Hz display: a 57 or 58 FPS cap can stop the frame rate repeatedly touching the FreeSync ceiling. Use ordinary VSync as the upper safety boundary if tearing appears above it.
• FSX running near 144 FPS on a 144 Hz display: the equivalent starting cap is about 141 or 142 FPS, although very few scenery-heavy FSX installations will sustain that target consistently.
• Frame rate below the FreeSync range: FreeSync cannot create missing frames. Without Low Framerate Compensation, judder or tearing may return below the monitor's lower limit.
• Brightness pulsing or menu flicker: disable FreeSync for FSX, where a per-game control is available, and compare ordinary fixed-refresh output.

The minus-three rule is not a general FSX performance recommendation. Its purpose is to keep a near-refresh-rate workload from hitting the top of the variable-refresh range. If FSX fluctuates between 35 and 55 FPS, a stable 30 or 40 FPS target will often look better than a nominal 57 FPS cap it cannot maintain.

Some Radeon releases identify Wait for Vertical Refresh as affecting OpenGL applications. Where the interface says that, it cannot be relied upon to force VSync in DirectX-based FSX. Use our FSX VSync and frame-pacing explanation to choose a method that applies to the simulator without stacking conflicting limits.

Radeon Anti-Lag reduces queued work in supported, GPU-limited situations; it does not raise frame rate. FSX controls also tolerate far more latency than a competitive action game, so Anti-Lag should remain off unless a repeatable GPU-limited input-delay problem gives you a reason to test it.

Frame Rate Target Control vs Radeon Chill

Choose Frame Rate Target Control over Radeon Chill when a driver-level FSX cap is necessary, but try the simulator's own Target frame rate control first.

The mistake we see repeatedly is enabling the FSX limiter, Frame Rate Target Control and Chill together. Multiple caps can compete, producing judder, delayed view movement and confusing frame-time spikes. Select one frame limiter and disable the others while evaluating it.

Frame Rate Target Control is not exposed on every Radeon generation or driver interface. If it is absent, there is no need to replace a stable driver merely to obtain it; FSX already provides a suitable static limiter.

Why are Radeon profile changes ignored by FSX?

Ignored settings usually indicate the wrong executable, an unsupported legacy DirectX override, or a display mode that does not meet the feature's activation conditions.

• Confirm that the profile points to the fsx.exe actually running, especially after moving or reinstalling FSX.
• Reset accumulated global overrides and apply changes only to the FSX profile.
• Restart FSX after changing anti-aliasing, synchronisation, display mode or scaling.
• On a laptop with integrated and discrete graphics, assign fsx.exe to the high-performance Radeon GPU through Windows graphics preferences.
• Remember that Radeon Super Resolution needs a lower render resolution and supported presentation mode; switching it on while FSX remains at native resolution achieves nothing.
• Do not assume Radeon Boost, Anti-Lag or another modern feature supports FSX merely because its name appears elsewhere in the driver.
• Temporarily remove overlays, post-processing injectors and forced compatibility options when diagnosing flicker, black screens or settings that appear ineffective.
• Test the default DirectX 9 mode separately from DX10 Preview because an override may apply differently, or not at all, between them.

Can Radeon settings fix low FPS and stutters?

Radeon settings cannot remove FSX's main CPU bottleneck, so a powerful graphics card may remain lightly loaded while one processor thread limits the flight.

A quick diagnostic is to lower FSX's resolution substantially without changing the aircraft or view. A large FPS increase indicates a GPU limit; little or no change points towards the processor, simulation load or scenery loading. Our explanation of why FSX remains CPU-bound on modern systems covers this behaviour in more detail.

Traffic, autogen, scenery complexity, water, cloud coverage and complex cockpit displays usually matter more than Texture Filtering Quality or Surface Format Optimization. If FSX cannot hold the selected cap, work through the simulator-side performance settings rather than turning on Boost, RSR or every Radeon performance optimisation.

For a confirmed GPU bottleneck, reduce forced anti-aliasing first, then test clouds, water and output resolution. RSR becomes a reasonable experiment only after a lower native render resolution has already demonstrated that the graphics card is the limiting component.