How do I configure NVIDIA Control Panel for X-Plane 12?
For X-Plane 12, create an NVIDIA Control Panel program profile for X-Plane.exe, leave antialiasing and anisotropic filtering application-controlled, keep shader caching enabled, and start with Normal power mode. Because X-Plane 12 uses Vulkan on Windows, many legacy OpenGL overrides do nothing; some can add stutter or visual faults.
How do I create the correct X-Plane 12 profile?
Create a per-program profile so the changes affect X-Plane 12 without altering every application on the computer. These instructions apply to Windows; Linux NVIDIA utilities use different controls, while macOS does not use NVIDIA Control Panel.
- Close X-Plane 12. Settings changed while the simulator is running may not take effect until it restarts.
- Open NVIDIA Control Panel. Select
Manage 3D settings, followed byProgram Settings. - Add the correct executable. Browse to
X-Plane.exein the X-Plane 12 installation folder. If several copies or demos are installed, verify that you have selected the executable you actually launch. - Apply the baseline settings below. Leave every unlisted option at its driver default.
- Select Apply and restart X-Plane 12. Test with the same aircraft, airport, weather and view before judging the result.
A mistake we see constantly is changing the Global Settings tab or attaching the profile to an old X-Plane installation. A program profile is safer and much easier to reset.
Which NVIDIA Control Panel settings should X-Plane 12 use?
The reliable baseline is to let X-Plane control rendering while the NVIDIA driver handles power, display synchronisation and shader caching.
| Setting | Recommended value | Reason |
|---|---|---|
| Power management mode | Normal or the default equivalent | Usually allows full performance under load without forcing maximum clocks constantly. Try Prefer maximum performance only if confirmed clock changes are causing hitches. |
| Shader Cache Size | Driver Default | Keeps Vulkan shader caching available. Do not disable it. Unlimited can reduce cache eviction across many games, but uses more storage and is not an automatic FPS improvement. |
| Antialiasing – Mode | Application-controlled | X-Plane's Vulkan renderer should control its own antialiasing. |
| Antialiasing – FXAA | Off | Driver FXAA can soften cockpit text and may not affect the Vulkan renderer as expected. |
| MFAA | Off | It is not a substitute for X-Plane's own antialiasing controls. |
| Anisotropic filtering | Application-controlled | Avoids conflicting with X-Plane's texture filtering. |
| Texture filtering – Quality | Quality | High performance modes may increase runway and terrain shimmering for little useful gain. |
| Low Latency Mode | Off | Vulkan applications manage frame submission themselves; forcing Ultra is not a reliable latency fix for X-Plane 12. |
| Max Frame Rate | Off initially | Add a cap only when you have chosen a specific frame-pacing strategy. |
| Vertical sync | Use the 3D application setting | Use X-Plane's setting unless configuring G-SYNC as described below. |
| Threaded optimisation | Auto | This is principally an OpenGL option and should not be forced for X-Plane 12's Vulkan renderer. |
| Triple buffering | Off | The NVIDIA option applies to OpenGL rather than normal Vulkan presentation. |
| Image Scaling | Off | Enable it only as part of a deliberate lower-resolution scaling setup; otherwise it can produce a softer image or an incorrectly scaled interface. |
| Vulkan/OpenGL present method | Auto, if shown | The driver should choose the appropriate presentation path. |
Some options appear only with particular GPUs, displays or driver branches. If a named option is absent, leave it alone rather than trying to expose it through unsupported configuration changes. Resolution, rendering scale, shadows and simulator antialiasing belong inside X-Plane; our X-Plane 12 graphics-quality guidance explains how those controls affect image clarity.
Do NVIDIA settings improve X-Plane 12 FPS?
NVIDIA profile changes rarely produce a large FPS increase by themselves, but they can prevent the wrong GPU, an unsuitable power policy or conflicting synchronisation settings from limiting performance.
If X-Plane is CPU-bound, lowering driver-level image settings will accomplish little. If it is GPU-bound, resolution, antialiasing, shadows and rendering effects inside the simulator matter far more. Use our CPU-versus-GPU performance checks for X-Plane 12 before reducing visual quality at random.
Prefer maximum performance is useful when the GPU repeatedly downclocks during a flight, but it is not the best universal setting. It increases power use and heat, which can make a thermally limited laptop slower. Start with Normal, monitor the result, and change it only when there is a repeatable problem.
How should V-Sync, G-SYNC and the FPS cap be set?
Use one coherent frame-pacing method rather than combining the X-Plane limiter, NVIDIA limiter and several V-Sync overrides.
| Display setup | Vertical sync | Frame cap |
|---|---|---|
| Fixed-refresh monitor | Application-controlled; enable V-Sync in X-Plane if tearing is objectionable | Off initially |
| G-SYNC or G-SYNC Compatible display | Enable G-SYNC, set NVIDIA Vertical sync to On, and disable X-Plane's V-Sync | Cap two or three FPS below the display's maximum refresh rate |
| Stable low-FPS target | Use the setting required by the display | Choose a rate the system can maintain in demanding weather and airports |
| Lowest latency with tearing accepted | Off | Off, unless a cap is needed to control heat or load |
For a fixed-refresh monitor, a sustainable divisor of the refresh rate can look smoother than fluctuating around an unreachable target—for example, 30 FPS on a 60 Hz display. If G-SYNC does not engage when X-Plane runs in a borderless window, check whether NVIDIA Control Panel is configured to use G-SYNC for both windowed and full-screen applications.
Why is X-Plane 12 still using integrated graphics?
Force X-Plane.exe to use the high-performance NVIDIA GPU through Windows graphics preferences as well as the NVIDIA profile.
- Add X-Plane to Windows graphics settings. Browse to the same
X-Plane.exeused for the NVIDIA profile. - Select the high-performance GPU. Windows may take precedence over the preferred-processor choice shown by NVIDIA Control Panel.
- Use mains power on a laptop. Battery and manufacturer power-saving modes can limit the discrete GPU even when it is selected correctly.
Activity on the integrated GPU does not necessarily mean it is rendering X-Plane; many laptops route the finished image through it. Check which GPU engine is attached to the running X-Plane process rather than relying only on overall GPU activity.
What should I do if the NVIDIA profile causes stutter or crashes?
Restore the X-Plane program profile to its defaults first, restart the computer, and test the simulator before reinstalling anything.
- No settings take effect: check that the profile points to the active X-Plane 12 executable rather than another installation.
- Stutter appeared after forcing maximum performance: return to Normal power mode and check for laptop heat or power limits.
- The first flight hitches after a driver change: the driver may be rebuilding its shader cache. Persistent stutter across repeated loads indicates another problem.
- Cockpit text looks blurred: turn off driver FXAA and Image Scaling, then use X-Plane's own antialiasing and rendering-resolution controls.
- X-Plane fails to open: reset the profile and work through our Vulkan, driver and start-up troubleshooting checks.
A clean, mostly default NVIDIA profile is the right starting point for X-Plane 12. Add only the power, synchronisation or frame-cap changes that solve a problem you can reproduce.