Enable anti-aliasing in FS2004, apply a graphics-driver override when needed, and fix jagged edges, shimmer and settings that will not stick.
To enable anti-aliasing in Microsoft Flight Simulator 2004 (FS9), open Settings, choose Display, select the Hardware tab, tick Anti-aliasing, and apply the change. If aircraft and building edges remain jagged, set a per-application anti-aliasing override for fs9.exe in the graphics driver rather than changing the global driver profile.
Enable anti-aliasing in FS2004
- Open the display settings. From the main screen, select Settings and then Display. During a flight, use Options, Settings and Display.
- Select the Hardware tab. The anti-aliasing option belongs to FS2004's hardware-rendering settings.
- Tick Anti-aliasing. Apply the change and return to the flight. Restart FS2004 if the new setting is not visible immediately.
- Use the correct resolution. In full-screen mode, select the monitor's native resolution where FS2004 offers it. Windowed mode uses the Windows desktop resolution.
- Check a genuine geometry edge. Look at a wing, tailplane or building against the sky. Runway textures, trees and fences can shimmer for different reasons and are not a reliable anti-aliasing test.
The built-in checkbox is the best starting point because it requires no driver-specific configuration. Resolution, filtering and texture settings also affect the result; our practical FS2004 graphics-settings baseline covers those companion settings.
Which FS2004 anti-aliasing setting should I use?
Start with FS2004's own anti-aliasing, then use a driver override only if the result is too weak or the checkbox has no visible effect.
| Method | Choose it when | Main drawback |
|---|---|---|
| FS2004 anti-aliasing | You want the simplest and most compatible option | Edge smoothing can be modest |
| Driver enhancement | The driver offers an option to enhance application-controlled anti-aliasing | Availability and wording vary by graphics driver |
| Driver override | FS2004's setting is ignored or remains too weak | Conflicting in-sim and driver settings can prevent it working |
| Supersampling | Transparent textures and distant objects still shimmer, and GPU performance is ample | Much heavier performance cost |
| Post-process AA such as FXAA | Conventional multisampling is unavailable | Can blur cockpit gauges and 2D panel text |
How do I force anti-aliasing through the graphics driver?
- Close FS2004. Driver-profile changes are more reliable when the simulator is not running.
- Create a per-application profile. Add the actual
fs9.exefrom the FS2004 installation folder. Do not force the setting globally, as that also changes other programs. - Choose a modest multisample setting. A 4x option is a sensible starting point where the driver provides one. Increase it only if there is a visible benefit.
- Set the correct control mode. For an Override mode, untick anti-aliasing inside FS2004 so the driver has sole control. For an Enhance mode, leave the FS2004 checkbox enabled.
- Test full-screen and windowed modes. Some modern driver combinations apply forced anti-aliasing to this older DirectX simulator in one mode but not the other.
Change one method at a time. Stacking internal anti-aliasing, a driver override and a post-process filter makes faults harder to identify and can soften the entire image.
Why does FS2004 still have jagged edges?
Persistent jagged edges usually mean the driver profile is not reaching fs9.exe, the simulator is rendering below the monitor's native resolution, or the visible problem is texture shimmer rather than polygon aliasing.
- Wrong executable profile: confirm that the graphics setting is attached to
fs9.exe, not an installer, launcher or unrelated shortcut. - Low rendering resolution: anti-aliasing cannot fully compensate for running FS2004 at a much lower resolution than the display.
- Windowed-mode limitation: test full-screen mode if a forced driver setting appears to be ignored.
- Graphics wrapper conflict: if an existing DirectX wrapper handles rendering, the normal driver override may not apply. Use one anti-aliasing authority rather than combining both.
- Transparent textures: trees, fences and some aircraft details use transparency. Ordinary multisampling may not smooth those edges; transparency supersampling can help where the driver offers it, but it is more demanding.
- Texture shimmer: crawling runway markings and distant ground textures require filtering and sensible mip-map settings, not simply stronger anti-aliasing.
Why will FS2004 not save the anti-aliasing setting?
FS2004 normally stores the display choice in its user configuration, but a read-only file, an abnormal shutdown or a configuration utility can restore the old value.
- Apply the setting and exit normally. A crash or forced termination can prevent FS2004 from writing its updated configuration.
- Check the configuration file. The usual location is
%APPDATA%\Microsoft\FS9\FS9.CFG. Make sure it is not marked read-only. - Check for configuration tools. Disable any utility or saved preset that rewrites display settings when FS2004 launches.
- Rebuild the file only as a last resort. Back up and rename
FS9.CFG, then start FS2004 so it creates a clean copy. This resets other customised settings as well.
Once anti-aliasing works, our guide to controlled FS9.cfg and graphics adjustments explains the visual changes that are useful beyond basic edge smoothing.
Does anisotropic filtering remove jagged edges?
Anisotropic filtering does not smooth aircraft silhouettes or building edges. It keeps runway, taxiway and terrain textures clearer when viewed at a shallow angle, while anti-aliasing handles polygon edges.
If the image looks sharp nearby but crawls or blurs in the distance, use trilinear or anisotropic filtering and review mip-map quality. Our comparison of anti-aliasing and anisotropic filtering shows which control addresses each visual fault.