FIELD MANUAL / 10
Graphics & driver policies
Adjust only options supported by your GPU and driver. Common, NVIDIA, AMD and Intel groups expose different capabilities.
- Where to find it
- Advanced → Graphics; Game settings → Graphics overrides
- When it applies / restoration
- Some driver options apply during sessions; application GPU preferences persist and take effect on the next application launch.
Step by step
- Identify the GPU rendering the game and check driver support. Do not force unavailable options.
- Configure power-saving GPU preferences for background applications in Common, then restart the target application.
- Review vendor-specific latency, frame generation, upscaling or cache options and test one combination at a time.
- Disable an option after a failed write, visual fault or frame-time regression and inspect recovery/readback logs.
Vendor features are different
NVIDIA options include performance power settings, low latency, Smooth Motion, DLSS overrides and per-game ReBAR. AMD includes Anti-Lag, AFMF and RSR. Intel latency changes are attempted only on DX9/DX11 paths that report live-switch support.
A preference does not migrate a running process
Saving a Windows power-saving GPU preference does not move a running process. Automatic background preference registration is off by default; a saved setting does not prove the active process has left the discrete GPU.
Restoration, power limits and VRAM
Driver snapshots restore original values; ambiguous ownership is not forcibly overwritten. Power limits remain within vendor allowances and do not guarantee better performance. VRAM residency neither adds nor locks memory, and is unavailable in Handheld.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.