How do I improve FPS in any flight simulator?

To improve FPS in any flight simulator, diagnose whether the limit is the CPU, GPU, VRAM, RAM or scenery delivery. Re-run one demanding flight, change one setting at a time, lower only settings tied to the bottleneck, disable suspect add-ons, then cap FPS at a rate the system can hold.

This is simulator-general advice for Microsoft Flight Simulator, X-Plane, Prepar3D, FSX, DCS and FlightGear. The same principles apply to Japanese-language flight sims (フライトシム), although menu labels and available settings vary by simulator, version and platform.

How to increase FPS: find the bottleneck first

The fastest way to improve flight sim FPS is to determine which component has the longest frame time before lowering any settings. Use the simulator's developer or performance display where available; our explanation of how to show FPS and interpret frame-time data covers the usual methods.

1. Build a repeatable test. Use the same aircraft, airport, runway, weather, traffic, cockpit view and time of day. Test where the real slowdown occurs, not over an empty rural area.
2. Remove the FPS cap temporarily. Disable V-Sync and other limiters during diagnosis so they do not conceal unused performance. Restore one limiter afterwards.
3. Reduce render resolution sharply. If FPS rises clearly, the GPU is probably limiting performance. If it barely changes, suspect the main CPU thread, traffic, aircraft systems or scenery draw calls.
4. Compare CPU and GPU frame times. The longer time determines the frame rate. Overall CPU utilisation can look low while one main simulation thread is saturated.
5. Test default content. Use a default aircraft and airport with third-party scenery, traffic injectors, weather utilities and cockpit tools disabled.
6. Change one option at a time. Record the result and restart when the simulator says a setting requires it. Moving every slider together prevents a useful comparison.

Which graphics settings improve flight simulator FPS most?

The settings that improve FPS most depend on whether the simulator is GPU-limited or CPU-limited. Lowering texture quality on a CPU-bound system, for example, can make the cockpit blurry without producing a useful performance gain.

Settings to lower when the GPU is limiting FPS

Render resolution is usually the strongest control when GPU frame time is higher than CPU frame time.

• Render scale and output resolution: reduce the number of pixels rendered per frame.
• Anti-aliasing and supersampling: avoid combining high in-simulator scaling with extra driver or VR-headset supersampling.
• Clouds, shadows and reflections: these become particularly expensive in poor weather and around complex airports.
• Ambient occlusion and post-processing: reduce these after resolution if cockpit clarity matters more.
• Texture resolution: lower it when VRAM is full or close to overflowing, rather than treating it as a universal FPS control.

Settings to lower when the CPU is limiting FPS

Traffic, scenery draw distance and complex aircraft systems are the usual targets when the main thread is slower than the GPU.

• Terrain and object level of detail: long draw distances increase the objects and draw calls the CPU must prepare.
• AI, road, airport and multiplayer traffic: moving vehicles require simulation, positioning, animation and rendering work.
• Autogen and scenery density: dense cities and detailed airports can overwhelm an otherwise capable CPU.
• Glass-cockpit refresh rates: multiple avionics displays can consume substantial main-thread time.
• Aircraft or mission complexity: a heavily scripted airliner or combat mission may remain CPU-bound at low graphics settings.

Our setting-by-setting breakdown of CPU, GPU and VRAM impact helps identify which controls to lower without flattening the entire preset. Older engines require different priorities: use the FSX-specific fixes for autogen, traffic, weather and add-ons instead of copying settings from a modern renderer.

What resolution should I use for better FPS?

Use the display's native resolution when the GPU can sustain your target frame rate; otherwise, keep the native output resolution and reduce render scale or enable the simulator's supported upscaler. This usually preserves menus and cockpit text better than lowering the display resolution itself.

Resolution has no universal answer based only on screen size. A 4K image contains four times as many pixels as 1080p, so a system that is comfortable at 1080p may become heavily GPU-limited at 4K. In VR, check both the simulator render scale and headset software scale; accidentally stacking supersampling in two places is a common cause of poor FPS.

Can I increase VRAM (como aumentar a VRAM)?

You cannot increase the physical VRAM fitted to a dedicated graphics card through software, a registry edit or a driver setting. The practical fixes are to reduce VRAM demand, replace the graphics hardware where possible, or use a system with a higher-capacity GPU.

• Lower texture resolution and remove unnecessary high-resolution scenery or aircraft texture packs.
• Reduce render resolution if the GPU is also short of processing performance.
• Close browsers, video tools and other applications using GPU memory.
• Avoid loading several overlapping scenery packages for the same area.
• Watch for VRAM usage that rises throughout a flight and never recovers, which can indicate an add-on or simulator fault.

Integrated graphics use shared system memory rather than dedicated VRAM. Increasing a firmware allocation may change the amount reported as reserved graphics memory, but it does not create additional memory bandwidth or turn system RAM into dedicated graphics memory. It can occasionally satisfy an application that checks the reported allocation poorly, but it is not an FPS upgrade.

Once dedicated VRAM is exhausted, assets may spill into shared memory and cause camera-turn stutters or severe frame-time spikes. Spare VRAM, however, does not automatically produce more FPS; it is capacity, not a measure of graphics-processing speed.

How do I improve FPS on a laptop?

A flight simulator laptop should be tested on mains power, in an appropriate performance mode, with the dedicated GPU selected and cooling unobstructed. Battery modes commonly restrict CPU and GPU power enough to cause low or unstable FPS.

1. Connect the original or suitably rated power supply. Some laptops cannot sustain full performance through an under-rated charger or dock.
2. Select the performance profile. Check both the operating system and the laptop manufacturer's control software where present.
3. Confirm which GPU is running the simulator. Assign the high-performance GPU through the operating system's graphics preference if hybrid graphics chooses incorrectly.
4. Check temperatures and clock behaviour. Falling clock speeds after several minutes point to thermal or power throttling rather than an in-simulator setting.
5. Reduce resolution before texture quality. Laptop displays can have high native resolutions that overload a modest mobile GPU even when VRAM is adequate.
6. Limit background work. Browser video, recording, cloud synchronisation and update processes can disturb the main thread and storage delivery.

Is an X9 Ultra fast enough for flight simulation?

The name X9 Ultra alone cannot predict flight simulator FPS because a product label does not identify the CPU, GPU, cooling or power limits that control performance. Check the exact model number, processor, graphics processor, RAM configuration and screen resolution rather than relying on words such as Ultra.

If the device uses integrated graphics, begin with 1080p or below, conservative scenery and traffic settings, and a modest frame-rate target. If it has a dedicated GPU, use the resolution test to establish whether that GPU or the CPU is the actual restriction.

On Xbox or PlayStation, hardware, drivers and VRAM allocation cannot be changed. Use any quality or performance mode offered by the simulator, reduce traffic or online scenery options where available, and remove add-ons associated with repeatable stutters.

What is good FPS for aviation and flight simulation?

A stable 30 FPS is usable for most aviation simulation, while stable 40 or 60 FPS provides smoother camera movement and control response when the hardware can sustain it. Consistent frame times matter more than a higher average that repeatedly collapses at airports or in heavy weather.

• 30 FPS: each frame lasts about 33.3 milliseconds; a sensible target for demanding aircraft or modest hardware.
• 40 FPS: each frame lasts 25 milliseconds; useful on compatible high-refresh or variable-refresh displays.
• 60 FPS: each frame lasts about 16.7 milliseconds; noticeably smoother but requires substantially more CPU and GPU headroom.

Set the cap slightly below the lowest rate the computer can maintain in your demanding test, not the highest rate seen in cruise. Use one limiting method rather than stacking simulator, driver and third-party caps; our guidance on choosing a sustainable FPS cap for the display explains fixed refresh, variable refresh and V-Sync choices.

Frame generation can increase displayed FPS, but it does not reduce the CPU work behind flight modelling, avionics or traffic. Establish stable native frame delivery first, because generated frames cannot repair severe base-frame stutter and may introduce artefacts during rapid camera movement.

Why do add-ons cause stutters?

Add-ons cause stutters when they introduce excessive objects, large textures, scripts, traffic, weather processing or overlapping scenery. A detailed airport may perform acceptably alone but fail when combined with a complex aircraft, live traffic and dense cloud cover.

Disable all third-party content and repeat the test with a default aircraft and airport. If performance recovers, restore add-ons in small batches, then test each item in the batch that brings the problem back. Common failures include duplicate airports, overlapping terrain, two traffic systems running together, outdated aircraft modules and utilities polling the simulator too frequently.

Performance that deteriorates over a long flight points more towards memory pressure, thermal throttling or an add-on fault than an ordinary graphics setting. Restarting may clear the symptom temporarily, but isolating the responsible component is the real fix.

When will a hardware upgrade increase FPS?

A hardware upgrade increases FPS only when it targets the measured bottleneck rather than the component with the most impressive specification.

• Upgrade the GPU when GPU frame time is consistently higher and reducing resolution produces a clear gain.
• Upgrade the CPU or platform when the main thread limits performance and reducing traffic, object distance or aircraft complexity helps more than lowering resolution.
• Add RAM when normal flights exhaust physical memory and cause paging. Extra unused RAM does not raise FPS.
• Choose more VRAM when detailed scenery, high-resolution textures or VR repeatedly exceed practical graphics-memory capacity.
• Use an SSD to shorten loading and reduce storage-related pauses. It rarely raises average FPS when the CPU or GPU is already the limit.

Which performance fixes should I avoid?

Avoid tweaks that change reported numbers without addressing CPU time, GPU time or memory pressure.

• Do not disable the operating system page file; memory pressure can then become a crash instead of a temporary slowdown.
• Do not delete shader caches routinely. Recompilation can create fresh stutters until the cache is rebuilt.
• Do not apply registry edits claiming to manufacture VRAM.
• Do not copy another simmer's complete preset without matching their resolution, aircraft, airport, weather and add-ons.
• Do not judge success by average FPS alone; watch the slowest frame times and repeatable pauses.
• Do not buy hardware before checking power modes, temperatures, clock speeds and background applications.

After tuning, validate the result at a detailed airport, in poor weather and during a longer flight. A configuration is successful only if it remains stable in the conditions you actually fly.