What are the best NVIDIA Control Panel settings for MSFS?
For Microsoft Flight Simulator 2020 and 2024, use a per-program NVIDIA profile: leave anti-aliasing and anisotropic filtering application-controlled, keep Power management mode at Normal, Shader Cache Size at Driver Default, Low Latency Mode off, and Preferred refresh rate at Highest available. Then configure frame limiting and V-Sync for your display.
These recommendations apply to the PC versions of Microsoft Flight Simulator; NVIDIA Control Panel settings do not apply on consoles. Driver settings provide a useful baseline, but render scaling, DLSS, TAA, clouds and terrain detail still need to be configured inside the simulator. Our detailed MSFS graphics settings breakdown covers those larger performance and image-quality choices.
Recommended NVIDIA Control Panel settings for MSFS
The following profile is our balanced starting point for image quality, smooth frame delivery and sensible power use.
| Setting | Recommended value | Why |
|---|---|---|
| Image Scaling | Off | Use the simulator's DLSS, render scaling or other built-in upscaler instead. Do not combine NVIDIA Image Scaling with DLSS without a specific reason. |
| Anisotropic filtering | Application-controlled | Set the desired filtering level inside MSFS. Forcing it in the driver can be ignored under some rendering paths. |
| Antialiasing mode | Application-controlled | MSFS uses temporal anti-aliasing or an upscaler selected in the simulator. |
| Antialiasing - FXAA | Off | Driver FXAA can soften cockpit text and does not fix temporal shimmer. |
| Antialiasing - Gamma correction | On | Leave this at its normal default. |
| MFAA | Off | MFAA is intended for compatible MSAA workloads and offers no useful baseline benefit here. |
| Low Latency Mode | Off | MSFS is frequently limited by its main thread, while DX12 controls its own render queue. Use NVIDIA Reflex inside the simulator when that option is available. |
| Max Frame Rate | Off initially | Add a cap only after choosing the correct V-Sync or G-SYNC arrangement for the display. |
| Monitor Technology | G-SYNC Compatible or G-SYNC, if supported | Select this only for a display on which variable refresh has been enabled and verified. |
| Power management mode | Normal or the driver default | Prefer maximum performance usually adds heat and power consumption without curing a CPU limit. |
| Preferred refresh rate | Highest available | Prevents the simulator from selecting an unnecessarily low display refresh rate. |
| Shader Cache Size | Driver Default | This is sufficient for most systems. Unlimited is reasonable when SSD space is plentiful and cache eviction is a demonstrated problem. |
| Texture filtering - Quality | Quality | High quality can reduce minor filtering optimisations, but the visual difference is usually smaller than the possible performance cost. |
| Texture filtering - Negative LOD bias | Allow; test Clamp for shimmer | Clamp can reduce texture crawling in some DX11 cases, but may be ignored under DX12 or soften detail. |
| Threaded optimisation | Auto | There is no advantage in forcing this legacy driver option for MSFS. |
| Triple buffering | Off | The Control Panel option is aimed primarily at OpenGL and is not the solution to MSFS frame pacing. |
| Virtual Reality pre-rendered frames | 1 or default | Leave queue management to the simulator, graphics API and OpenXR runtime unless testing proves otherwise. |
Leave settings not listed above at their defaults. NVIDIA changes some labels between driver generations, so a missing or renamed option is not necessarily a fault.
How do you create an NVIDIA profile for Microsoft Flight Simulator?
Create a separate program profile for each installed edition of Microsoft Flight Simulator rather than changing Global Settings.
- Close the simulator. Driver-profile changes are easiest to verify after a fresh launch.
- Open NVIDIA Control Panel. Select Manage 3D settings, followed by Program Settings.
- Select the simulator profile. If it is absent, launch MSFS once, close it and use Add to select the recently used application. Choose the simulator itself, not a launcher.
- Restore the profile defaults. This removes conflicting tweaks copied from old optimisation guides.
- Apply the settings. Start MSFS and test the same aircraft, airport, weather and camera view before judging a change.
Microsoft Store installations may keep their executable in a protected location. Use the existing profile or the recently used application list rather than changing permissions on protected Windows folders. On a laptop that launches MSFS on integrated graphics, select the high-performance GPU for the simulator in Windows Graphics settings as well.
Should V-Sync and G-SYNC be enabled for MSFS?
V-Sync and frame-cap settings must match the display: a G-SYNC monitor needs a different arrangement from a fixed-refresh television or monitor.
| Display setup | Control Panel | MSFS setting |
|---|---|---|
| G-SYNC or G-SYNC Compatible | Enable G-SYNC, set Vertical sync to On and cap the frame rate about 2-3 fps below maximum refresh | V-Sync Off |
| Fixed refresh, able to hold full refresh | Vertical sync application-controlled | V-Sync On |
| Fixed refresh, unable to hold full refresh | Use one frame limiter or a clean refresh-rate divisor | Use a fractional V-Sync option if the simulator provides one |
| Lowest latency, tearing acceptable | Vertical sync Off; optional sustainable frame cap | V-Sync Off |
A 60 Hz display that cannot sustain 60 fps often feels steadier at a properly paced 30 fps than while fluctuating between the two. On a high-refresh variable-refresh monitor, choose a cap that the system can sustain in demanding airports rather than one it reaches only during cruise.
Frame Generation complicates this slightly. On supported hardware it normally works with NVIDIA Reflex, which can manage the refresh ceiling when G-SYNC and V-Sync are configured correctly. Start with Max Frame Rate off in that situation; do not stack several limiters unless testing shows a pacing problem.
Should NVIDIA Low Latency Mode be On or Ultra?
Keep NVIDIA Low Latency Mode off as the baseline for Microsoft Flight Simulator, especially when using DX12 or NVIDIA Reflex.
The driver option mainly controls the render queue for DX11 applications. Under DX12, queue management belongs to the application, while MSFS can also be CPU-bound before the GPU queue becomes the problem. If your simulator build exposes NVIDIA Reflex Low Latency, use that in preference to forcing Ultra in the driver.
For a GPU-bound DX11 setup without Reflex, testing Low Latency Mode on may reduce input delay. Ultra can produce uneven delivery when the main thread is already struggling, so compare frame-time consistency rather than relying on the displayed average frame rate.
Can NVIDIA Control Panel fix jagged edges and shimmer?
No: driver-forced anti-aliasing is not an effective cure for MSFS jagged edges, glass-cockpit flicker or distant texture shimmer.
Use TAA, DLAA or DLSS inside the simulator, then adjust render scaling and sharpening there. Negative LOD bias set to Clamp is worth testing under DX11, but DX12 may ignore the override. Our guide to reducing jagged edges and aircraft shimmer explains which combinations improve clarity without blurring cockpit displays.
Which NVIDIA settings can reduce MSFS stutters?
No NVIDIA profile can cure every MSFS stutter because many pauses originate in the CPU main thread, scenery streaming, aircraft systems or exhausted VRAM.
Leave Shader Cache enabled and avoid clearing it routinely; the first flight after clearing or rebuilding a cache may stutter while shaders are compiled again. Prefer maximum performance is worth testing only when monitoring shows the GPU repeatedly dropping to low clock speeds during active flight. If it makes no measurable difference, return to Normal to reduce temperature and power draw.
A sustainable frame cap can improve pacing when frame rate repeatedly swings between CPU- and GPU-limited states. Our MSFS stutter and micro-pause troubleshooting steps explain how to identify the limiting component before changing more driver options.
Why are the NVIDIA settings not taking effect?
Most failed NVIDIA tweaks come from editing the wrong application profile or forcing an override that DX12 does not support.
- Wrong executable: the profile targets a launcher rather than the running simulator.
- Wrong edition: MSFS 2020 and MSFS 2024 have separate profiles when both are installed.
- Global changes: a global override affects other games and can conflict with the dedicated MSFS profile.
- DX12 limitation: legacy anti-aliasing, filtering and queue overrides may be ignored because the application controls them.
- Competing optimisation: applying automatic optimisation through NVIDIA software can rewrite the simulator's own graphics settings during comparisons.
- Driver reset: a clean driver installation can return profiles to their defaults.
- Laptop GPU selection: modern Windows versions can override the preferred graphics processor chosen in NVIDIA Control Panel.