Use the best NVIDIA Control Panel settings for Prepar3D, with profile choices for smoother FPS, lower stutter, G-SYNC and laptop GPUs.
For Prepar3D, create an NVIDIA program profile and leave anti-aliasing, anisotropic filtering and V-Sync application-controlled. Set Power management mode to Prefer maximum performance, Preferred refresh rate to Highest available, Low Latency Mode to Off and Shader Cache Size to Driver Default. Add a frame cap only when it improves frame pacing.
How do I create a Prepar3D NVIDIA profile?
Use a program-specific profile so the settings affect Prepar3D without changing every other application.
- Close Prepar3D before changing its driver profile.
- Open NVIDIA Control Panel and select Manage 3D settings, followed by Program Settings.
- Add or select
Prepar3D.exe. If several Prepar3D versions are installed, confirm that the selected executable belongs to the version you actually use. - Apply the settings below, save the profile and restart Prepar3D.
Optimise the simulator before trying aggressive driver overrides. Our Prepar3D graphics-setting baseline explains which in-sim options have the largest visual and performance costs.
Best NVIDIA Control Panel settings for Prepar3D
This conservative profile avoids duplicated filtering, conflicting frame limiters and expensive driver-level effects.
| Setting | Recommended value | Reason |
|---|---|---|
| Image Scaling | Off | Enable only when deliberately rendering below the monitor's native resolution. |
| CUDA – GPUs | All | Prevents an unnecessary GPU restriction on multi-GPU systems. |
| DSR Factors | Off | Supersampling through DSR can add a very large GPU and VRAM load. |
| Anisotropic filtering | Application-controlled | Let Prepar3D handle runway and terrain texture filtering. |
| Antialiasing – FXAA | Off | Driver FXAA can soften cockpit text and instruments. |
| Antialiasing – Mode | Application-controlled | Modern Prepar3D renderers do not reliably benefit from forced driver anti-aliasing. |
| Antialiasing – Transparency | Off | Transparency supersampling can be costly around vegetation, fences and complex airports. |
| MFAA | Off | Its benefit is inconsistent with Prepar3D's own anti-aliasing pipeline. |
| Low Latency Mode | Off | Prepar3D is frequently CPU-limited, and restricting queued frames can introduce stutter. |
| Max Frame Rate | Off initially | Enable only if a deliberate cap produces steadier frame pacing. |
| Power management mode | Prefer maximum performance | Keeps the GPU from reducing clocks during variable simulator workloads. Use this in the Prepar3D profile rather than globally. |
| Preferred refresh rate | Highest available | Ensures Prepar3D uses the display's highest configured refresh rate. |
| Shader Cache Size | Driver Default | A larger value rarely fixes a CPU bottleneck and consumes additional storage. |
| Texture filtering – Quality | Quality | High performance may gain little while increasing texture shimmer. |
| Threaded optimisation | Auto | The driver can decide when its optimisation is applicable. |
| Triple buffering | Off | This control applies primarily to OpenGL; Prepar3D uses DirectX. |
| Vertical sync | Use the 3D application setting | This is the safest baseline unless configuring G-SYNC deliberately. |
Some controls may be absent or renamed depending on the GPU and driver. Avoid copying hidden compatibility flags from another simulator: Prepar3D v4 uses DirectX 11, while v5 and v6 use DirectX 12, so old profile tweaks may be ignored or cause artefacts.
Should Prepar3D use V-Sync, G-SYNC or a frame cap?
Choose one frame-control strategy and avoid running two competing limiters.
- Fixed-refresh monitor: leave NVIDIA V-Sync application-controlled and configure V-Sync inside Prepar3D. If the system cannot sustain the refresh rate, cap it at a stable rate rather than chasing a fluctuating maximum.
- G-SYNC monitor: enable G-SYNC for the display mode you use, set NVIDIA V-Sync to On, disable Prepar3D's V-Sync and cap the frame rate slightly below the monitor's maximum refresh rate.
- No synchronisation: set V-Sync to Off. A sustainable cap can still reduce heat, fan noise and frame-time swings.
If using NVIDIA Max Frame Rate, leave Prepar3D's own target unrestricted. Alternatively, use the simulator's limiter and leave the driver cap off. Test both approaches because the smoother option depends on whether the main thread or GPU is limiting performance.
Why should anti-aliasing remain application-controlled?
Forced NVIDIA anti-aliasing often does nothing in modern Prepar3D versions because the simulator controls its DirectX rendering pipeline.
Driver FXAA may blur instrument labels, while transparency supersampling can heavily penalise detailed airports and vegetation. Select MSAA or SSAA inside Prepar3D instead; SSAA gives cleaner edges but carries a much higher GPU cost. For broader tuning, follow our CPU-versus-GPU performance checks for Prepar3D.
When should I change the baseline settings?
Change a driver option only to solve a measured problem, then test the same aircraft, airport, weather and camera position.
- GPU usage is consistently saturated: lower Prepar3D resolution, anti-aliasing, shadows or reflections before selecting NVIDIA's High performance texture filtering.
- GPU clocks fall during flight: confirm that Prefer maximum performance is active in the correct executable profile and check power or temperature limits.
- Runways and distant scenery shimmer: keep Texture filtering on Quality and test Negative LOD bias set to Clamp, although DirectX 12 may not honour every driver override.
- Frame rate is high but uneven: introduce one frame cap at a sustainable value. A lower stable rate usually feels better than repeated swings.
A stronger GPU will not remove every Prepar3D bottleneck. Dense scenery and complex aircraft can be limited by the processor's main thread; our GPU, CPU and VRAM guidance for Prepar3D helps identify the relevant hardware limit.
What if the NVIDIA settings make Prepar3D worse?
Restore the Prepar3D program profile to its defaults, then reapply only Power management mode and Preferred refresh rate before testing again.
- Check the executable: a profile for an older Prepar3D installation will not affect another version.
- Remove duplicate limiters: disable either the NVIDIA frame cap or Prepar3D's target frame rate.
- Undo forced rendering options: restore anti-aliasing, filtering and V-Sync to application-controlled.
- Verify laptop GPU selection: on systems with integrated and NVIDIA graphics, assign
Prepar3D.exeto the high-performance NVIDIA GPU in Windows graphics settings. Modern Windows versions may override the older preferred-GPU control. - Reset after display failure: if Prepar3D opens to a blank display, use our driver and black-screen recovery checklist.
Change one option at a time. Applying a large collection of copied settings makes it impossible to identify which override caused stutter, blurred gauges or unstable frame pacing.