Learn which flight simulator graphics settings cost the most FPS and how to tune clouds, LOD, textures, filtering and traffic.
In a general flight simulator, resolution or render scale, volumetric clouds, shadows, reflections, anti-aliasing and terrain or object detail usually matter most. Keep anisotropic filtering high and textures as high as VRAM permits; then lower GPU-heavy settings or CPU-heavy traffic and level of detail according to the bottleneck.
This answer covers flight simulators generally rather than one named title. Setting names, slider ranges and the division of work between the CPU and GPU vary by simulator and rendering engine.
Which graphics settings have the largest FPS impact?
Resolution and render scale normally create the heaviest pure GPU load, while traffic and terrain or object detail can hurt more when the main simulation thread is the limit.
| Setting | What it changes | Main limit | Cost when raised |
|---|---|---|---|
| Resolution or render scale | Overall sharpness, cockpit text and distant detail | GPU | Very high |
| Anti-aliasing or upscaling | Jagged edges, shimmer and image stability | GPU | Medium to high; upscaling may recover FPS |
| Volumetric clouds | Cloud density, lighting, shape and weather depth | Usually GPU | High in dense or layered weather |
| Terrain, object LOD and autogen | Distant terrain, buildings, vegetation and airport objects | CPU main thread, with GPU and memory use | Medium to very high |
| Shadows and ambient occlusion | Cockpit depth, aircraft shading and ground contact | GPU and sometimes CPU | Medium to high |
| Reflections and mirrors | Water, canopy, cockpit and mirror reflections | GPU | Medium to high |
| AI and ground traffic | Aircraft, road vehicles, boats and airport activity | Usually CPU | High in busy areas or large missions |
| Texture quality | Surface detail on aircraft, scenery and instruments | VRAM or shared memory | Usually low until memory capacity is exceeded |
| Anisotropic filtering | Runway and terrain sharpness at shallow viewing angles | GPU | Usually low |
The order changes with the aircraft, airport, camera, weather and add-ons. A glass-cockpit airliner at a detailed hub can be CPU-limited, while an exterior view through heavy cloud may shift the same computer to a GPU limit.
Anti-aliasing needs a visual check rather than a blind preset choice. Aggressive temporal upscaling can soften instrument text and runway markings or leave trails behind moving objects. Frame generation raises the displayed frame rate, but it does not remove main-thread delays or improve the simulator's underlying control response.
For more detail on the image-quality side, see our explanation of resolution, anti-aliasing, textures and level-of-detail trade-offs.
What about anisotropic filtering and clouds?
Anisotropic filtering is usually cheap and should remain high, while cloud quality is often one of the first settings to reduce on a GPU-limited system.
What does anisotropic filtering do?
Anisotropic filtering keeps runway markings, taxiways and ground textures sharp as they recede towards the horizon. Start at 16x when that option exists; try 8x only on older or very restricted hardware.
Lowering it rarely produces the FPS gain people expect. A mistake we see constantly is sacrificing filtering or texture clarity before touching expensive clouds, reflections or render scale. Our deeper guide to FPS and texture filtering explains the distinction between filtering, texture resolution and frame rate.
How much do clouds matter?
Clouds can have a large GPU cost, especially with overcast, storms, multiple layers or long weather draw distances. Test them in demanding weather; a clear-sky benchmark will hide the setting's real impact.
High is often a better balance than the maximum preset. If reducing clouds produces no meaningful improvement, the simulator is probably CPU-limited or the particular engine uses a less demanding cloud system.
What are the exact settings?
There is no universal set of exact settings because simulators use different scales and computers with the same marketing name can contain different hardware.
If you arrived asking “what are his exact settings?”, there is no individual creator, benchmark rig or hidden profile behind this general answer. The following values are practical starting points, not claimed performance results.
| Setting | Balanced discrete-GPU PC | Modest or integrated-graphics laptop |
|---|---|---|
| Output resolution | Native display resolution | Native output with reduced render scale; use 1280×720 or 1600×900 if the simulator lacks render scaling |
| Render scale | 100%; reduce to 80–90% at a high pixel count | 70–85% |
| Anti-aliasing | Stable temporal option or quality-mode upscaling | Quality or balanced upscaling where available |
| Textures | High if they fit in VRAM | Medium; lower if memory pressure causes pauses or missing textures |
| Anisotropic filtering | 16x | 8x or 16x |
| Clouds | High | Low or medium |
| Shadows | Medium | Low |
| Reflections and mirrors | Low or medium | Low or off |
| Terrain and object LOD | Default or medium, then increase carefully | Low or medium |
| Traffic | Low or medium | Low or off |
| Frame-rate target | The lowest stable target suitable for the display, commonly 30, 40 or 60 FPS | Start with a stable 30 FPS cap |
Maximum presets are rarely the sensible starting point. Increase one setting at a time after testing the aircraft, airport and weather combination that you actually fly.
How do you find the real performance bottleneck?
A substantial FPS improvement after lowering render scale indicates a GPU limit; little or no change points towards the CPU, an FPS cap, memory pressure or another constraint.
- Create a repeatable test: use the same aircraft, airport, weather, cockpit view and traffic. Wait for scenery loading and shader activity to settle.
- Expose the base performance: temporarily disable frame generation and account for V-sync or an FPS limiter, which can conceal small improvements.
- Lower render scale sharply: try roughly 50–70% without changing anything else. A clear reduction in frame time means resolution, clouds, shadows and reflections are the best targets.
- Test the main thread: if resolution changes little, reduce traffic, terrain or object LOD, autogen density and long-distance shadows. Low total CPU utilisation does not rule out a CPU limit because one simulation thread can hold back the frame.
- Check memory symptoms: view changes that trigger pauses, late-loading textures or sudden frame-time spikes can indicate exhausted VRAM or shared memory. Scenery streaming and storage delays can cause similar symptoms, so do not diagnose memory from blur alone.
- Restore settings individually: change one category at a time and retest the same scene.
If that process does not identify the cause, use our flight simulator bottleneck and FPS checklist to check drivers, background software, storage, power modes and system limits.
Which settings should you lower first?
Lower settings according to the limiting component rather than moving every slider to medium.
- GPU-limited: reduce render scale first, followed by clouds, reflections, mirrors, shadow quality and expensive anti-aliasing. Preserve anisotropic filtering and textures where memory allows.
- CPU-limited: reduce AI traffic, ground vehicles, terrain or object LOD, autogen density and shadow draw distance. Lowering texture resolution or screen resolution may achieve nothing.
- VRAM-limited: reduce texture resolution and scenery detail, then retest with the most demanding aircraft and airport you use. Integrated graphics borrow system memory, so background applications can make this worse.
- VR-limited: prioritise consistent frame time. Per-eye resolution, clouds, mirrors and shadows are common first targets, but cockpit readability limits how far anti-aliasing or upscaling can be reduced.
If poor performance occurs only with one aircraft, airport or scenery package, test a default aircraft at a default location before damaging image quality everywhere. Complex add-ons can create separate CPU, GPU and memory loads; our guide to aircraft, airport, traffic and scenery add-on performance explains how to isolate them.
I have a Lenovo IdeaPad 3 — which settings should I use?
A Lenovo IdeaPad 3 model name is not enough to choose exact settings because the range includes different processors, integrated graphics and dedicated GPUs.
Check the exact CPU, GPU, installed memory and display resolution in Windows before choosing a profile. Task Manager's Performance view normally identifies the GPU and shows whether a separate dedicated GPU is present.
- Integrated Intel or AMD graphics: begin with the modest-laptop profile above. Target 30 FPS, keep clouds, shadows, reflections and traffic low, use medium textures, and leave anisotropic filtering at 8x or 16x.
- A separate dedicated GPU: begin with the balanced profile. Make sure the simulator is assigned to the high-performance GPU in Windows graphics preferences; menu wording varies between Windows releases.
- Performance falls after several minutes: suspect heat or power limits. Use the laptop on a hard surface with clear vents, connect its power adaptor and select the manufacturer's performance mode if one is provided.
- Stutters occur when turning the camera: reduce textures one step and close memory-heavy background applications. On integrated graphics, system RAM is also graphics memory.
Do not copy settings from another IdeaPad 3 without comparing the complete processor and GPU names. Two machines with the same family badge can perform very differently.
Is this for a PC game (juego en PC), console or mobile?
The full tuning method is mainly for a PC game because PC simulators normally expose the widest range of graphics controls.
- PC: use the GPU, CPU and memory diagnosis above. Resolution, render scale, traffic and LOD are usually the most useful controls.
- Console: select performance or quality modes if the simulator provides them, then adjust traffic or density options that remain exposed. Console editions may use fixed or dynamic settings that cannot be matched to a PC preset.
- Mobile: start with resolution scale, shadows, clouds, reflections and traffic. If performance begins well but deteriorates as the device warms, reduce the frame-rate cap and GPU-heavy effects rather than texture filtering alone.
Microsoft Flight Simulator 2024 is available on PC, Xbox Series X|S, PlayStation 5 and PS5 Pro. Microsoft Flight Simulator 2020 remains a PC and Xbox release. Their console controls should not be confused with the menus used by unrelated mobile flight simulators.
Do the priorities change between simulators and flying styles?
Yes — every engine distributes scenery, simulation, weather and rendering work differently.
Microsoft Flight Simulator can become main-thread limited by terrain or object LOD, traffic and detailed airports even while the GPU has spare capacity. Other simulators may react more strongly to anti-aliasing, mirrors, shadow maps, vegetation or mission complexity.
- Low-level VFR: favour terrain detail, vegetation, draw distance and anisotropic filtering.
- Airliner operations: protect cockpit readability, clouds and airport detail; reduce distant scenery and non-essential traffic first.
- Combat or formation flying: stable frame time and object visibility matter more than maximum reflections or cockpit shadows.
- VR: prioritise a repeatable frame time over the highest preset because missed frames are more distracting in a headset.
What about the rest (e o resto) of the settings?
Most remaining settings are secondary until a particular scene or simulator makes them expensive.
- Bloom, lens effects, motion blur and depth of field: choose these by visual preference. Disabling them may improve clarity, but the FPS gain is often smaller than reducing clouds or render scale.
- Water quality: matters most near coasts, lakes and reflective weather. Reflection quality is usually the expensive part.
- Vegetation and buildings: treat these as scenery or autogen controls, not decoration. Dense objects can load both the main thread and GPU.
- V-sync and frame caps: they control frame delivery and tearing rather than scene detail. A cap can make pacing steadier but can also hide the result of a settings test.
- Streaming and cache options: these affect download, storage and scenery delivery. They should not be used as substitutes for reducing an overloaded GPU or main thread.
Is there a video (gibt es dazu ein Video)?
No companion video is included with this answer.
A video can demonstrate menu locations for one simulator release, but copying its settings does not account for a different GPU, resolution, aircraft or airport. The repeatable render-scale test above remains the more reliable way to identify what your own system needs.