Improve Aerosoft EDDF/EDDFX FPS in MSFS 2024 by removing scenery conflicts, reducing traffic, and tuning CPU, GPU and VRAM-heavy settings.
To improve performance at Aerosoft EDDF/EDDFX in Microsoft Flight Simulator 2024, remove duplicate Frankfurt scenery, cut AI and road traffic, lower Objects LOD and airport shadows, and watch VRAM use. Test in the same aircraft, weather and parking position; EDDF is often CPU-limited on the apron but VRAM-limited with complex airliners.
Fix EDDF performance in the right order
The quickest reliable gain comes from identifying the limiting component before reducing graphics quality indiscriminately.
- Create a repeatable test. Load the same gate, aircraft, weather preset and camera view each time. Let scenery and traffic finish loading before recording performance. Make one run in a simple default aircraft and another in your usual airliner.
- Identify the bottleneck. On PC, use the simulator's developer FPS display or a trusted hardware overlay. A MainThread limit points towards traffic, Objects LOD, airport services or aircraft systems; sustained maximum GPU use points towards resolution, clouds, shadows and reflections. Turn frame generation off while diagnosing because generated frames can conceal the underlying frame rate.
- Check for another Frankfurt airport. Disable any separate EDDF freeware, older payware conversion or alternative airport package. Do not delete individual Aerosoft product components merely because one contains EDDFX in its name; disable complete products through their supported manager. Follow our scenery-conflict isolation method if the duplicate is not obvious.
- Test with traffic at zero. Temporarily disable live or AI aircraft, parked ground aircraft, airport vehicles and road traffic. If performance improves, restore each category gradually. Aircraft traffic and detailed airliner models are usually the heaviest CPU load at a hub such as Frankfurt.
- Run a clean add-on test. Temporarily remove non-essential packages from the PC
Communityfolder or disable them through their manager. Traffic injectors, ground-service utilities, high-resolution liveries, city scenery and airport scripts should be tested separately. Console users must perform the equivalent test through the in-simulator content library. - Adjust settings for the measured limit. Do not lower render scale to fix a MainThread problem, and do not expect reduced traffic to solve a GPU running continuously at full load.
Which MSFS 2024 settings improve EDDF FPS most?
Traffic and Objects LOD usually give the largest CPU-side improvement at EDDF, while texture resolution, render scale, shadows and reflections matter most when the GPU or VRAM is full.
| Setting | Lower it when | Expected effect |
|---|---|---|
| AI, live and parked aircraft | MainThread-limited, especially at the terminal | Reduces aircraft systems, model draw calls and traffic processing |
| Airport vehicles and road traffic | FPS falls across the apron or while taxiing | Reduces CPU load from moving ground objects |
| Objects LOD | The main thread is limiting performance | Reduces the distance and detail at which terminal, city and airport objects are processed |
| Texture resolution | VRAM is nearly full, panning causes pauses or textures become blurry | Reduces texture memory pressure from the airport, aircraft and liveries |
| Render scale or anti-aliasing mode | The GPU is fully loaded without VRAM-related pauses | Reduces pixel-rendering cost but does little for a CPU bottleneck |
| Shadow maps, contact shadows and reflections | The GPU struggles around terminal interiors, glass and apron lighting | Reduces GPU work and some VRAM use |
| Terrain LOD | Performance drops mainly on approach over the Frankfurt area | Reduces distant terrain and city processing; it is less useful for a gate-only slowdown |
Change settings in small groups and keep visual features that are not contributing to the measured limit. Our explanation of how scenery controls divide their load between the CPU, GPU and VRAM provides a fuller tuning reference.
What should I disable around Frankfurt?
Keep one complete custom EDDF airport active, along with only the libraries that product requires.
The stock airport is normally suppressed by the custom scenery and should not be removed by deleting simulator files. A separate Frankfurt airport package is a genuine conflict; multiple folders belonging to one Aerosoft installation may simply be required components. Disable the complete product when testing rather than dismantling its folders.
Frankfurt city scenery, regional mesh and photogrammetry can remain installed if they do not replace the airport, but they may add load or overlap its boundary. Where package ordering is available, give the custom airport priority over overlapping city and regional scenery. Load order cannot make two complete EDDF airport products compatible.
If the scenery's supported installer or configuration utility offers optional static aircraft, terminal interiors, animated apron objects or landside detail, disable the features you do not use. Static aircraft are poor value when a traffic injector already supplies parked aeroplanes: both sets consume resources and may occupy the same stand.
Why does Aerosoft EDDF stutter on final or at the gate?
Stutters on final usually come from scenery streaming, traffic spawning or exhausted VRAM, while pauses when panning at the gate more strongly suggest texture swapping.
- Stutter during approach: test without city scenery and online traffic, confirm that the simulator has stable bandwidth, and reduce Terrain or Objects LOD if the main thread spikes as Frankfurt appears.
- Pauses while turning the cockpit camera: lower texture resolution, remove unnecessarily large liveries and test without detailed cabin options. Render scale helps only if the GPU itself is saturated.
- Regular pauses every few seconds: disable traffic injectors, ground-service tools and other utilities one at a time. A repeating interval usually indicates an add-on process rather than the airport geometry alone.
- Problems after an update: recreate the rolling cache once if it appears corrupted and verify the scenery through its supported installer. Clearing caches before every flight generally creates more loading work rather than fixing the cause.
The first visit after a simulator, scenery or graphics-driver update may be less smooth while data is rebuilt. Persistent spikes need systematic diagnosis; use our frame-time troubleshooting sequence to separate streaming, storage, add-on and VRAM problems.
Should I use DLSS or frame generation at EDDF?
Use DLSS or a lower render scale when EDDF is GPU-limited; use frame generation only after the underlying frame rate is stable.
A quality-biased upscaling mode can recover GPU headroom, although cockpit displays may look softer than with native rendering or TAA. Frame generation can make camera movement appear smoother on supported hardware, but it does not reduce MainThread load, traffic processing or scenery-loading stalls. Diagnose performance with it disabled, then enable it for normal flying if the controls remain responsive and visual artefacts are acceptable.
Is the airport or aircraft causing the low FPS?
A same-gate comparison between a simple default aircraft and your usual airliner will show whether EDDF or the aircraft is the larger load.
If both perform poorly with traffic disabled, concentrate on the airport, overlapping scenery and Objects LOD. If only the complex airliner struggles, reduce any available cockpit-display refresh setting, test without detailed cabin features and high-resolution liveries, and check aircraft-specific utilities. Once the baseline is smooth, restore traffic and add-ons individually so the exact cost of each one remains visible.