PC Graphics Settings: What to Lower First for Smoother Play

If a PC game feels rough, lower the settings that create expensive lighting, reflections, fog, and long-distance detail before destroying texture quality. That order usually gives you a better chance of gaining smoother frame delivery while keeping the image readable.

This is a practical testing sequence, not a promise that every engine reacts identically. Your bottleneck may be the GPU, CPU, video memory, storage, or shader compilation.

Set a target before changing anything

Choose the experience you want: a stable 60 FPS for a cinematic game, a frame rate inside your variable-refresh-rate range, or the highest consistent performance your competitive setup can sustain. A stable result with clean frame pacing often feels better than an average that swings wildly.

Use the game's built-in benchmark when it represents real play. Otherwise, repeat the same demanding route for 60 to 90 seconds. Record average FPS, low points, and visible stutter. Change one group of settings at a time so you know what helped.

1. Lower ray tracing first

Ray-traced reflections, global illumination, shadows, and path-traced modes can be among the most demanding options in a modern game. Move ray tracing down one level or disable it, then compare the same scene—especially water, glass, dense lighting, or moving objects.

If several ray-tracing controls are available, keep the effect you notice most and reduce the others.

2. Reduce shadows and volumetric effects

Shadow quality can increase resolution, draw distance, update frequency, and shadow-casting lights. Moving from Ultra to High or Medium often looks less dramatic than the name suggests. Volumetric fog, clouds, and lighting can also be costly in large outdoor scenes.

3. Cut reflections and ambient effects

Screen-space reflections, ambient occlusion, contact shadows, and high-quality water add depth but may cost performance in reflective or layered scenes. Lower reflections before textures. Medium ambient occlusion often keeps useful depth cues while reducing load.

4. Adjust view distance and crowds when the CPU struggles

If lowering resolution barely changes performance, the game may be limited elsewhere. View distance, object density, simulation quality, traffic, and crowds can increase CPU work and draw calls. Reduce them one step and retest a busy area.

Low GPU usage does not prove a CPU bottleneck by itself. Frame caps, menus, thermal limits, background work, and monitoring errors can also affect utilization.

5. Use upscaling carefully

DLSS, FSR, XeSS, and engine-specific temporal upscalers render internally at a lower resolution and reconstruct the final image. Start with Quality mode. Move to Balanced only if you still need performance, then inspect vegetation, hair, particles, and motion for artifacts.

AMD's current FSR documentation confirms that supported games expose upscaling modes in their graphics menus. Availability and behavior depend on the game and hardware.

6. Lower render scale before display resolution

If no good upscaler is available, try a small render-scale reduction while keeping the monitor at native display resolution. A move from 100% to 90% can be easier to accept than dropping straight to a lower display resolution.

7. Protect textures until video memory is the problem

Texture quality often changes memory use more than shader load. Keep it high if the game runs smoothly and video memory is sufficient. Lower it when you see repeated texture streaming, sharp hitches after camera turns, memory warnings, or severe instability.

Anisotropic filtering is usually worth keeping moderate or high because it clarifies angled surfaces. Older supersampling anti-aliasing modes can be expensive, while modern temporal options vary by engine.

8. Treat frame generation separately

Frame generation can increase displayed smoothness in supported games, but generated frames do not replace a healthy base frame rate. Competitive players should judge responsiveness as well as the FPS counter. Test during aiming, camera turns, menus, and rapid movement.

Latency features have specific requirements. AMD says Anti-Lag 2 requires integration in supported games, while Microsoft's DirectX guidance notes that Windows optimizations for windowed games can improve latency for compatible DirectX 10 and 11 titles.

Settings that rarely solve a major problem

• Motion blur, film grain, and chromatic aberration: change them for preference, but do not expect a large universal gain.
• HUD size and subtitles: accessibility choices are not performance tuning.
• Texture filtering alone: lowering it may harm clarity without fixing the bottleneck.
• Random driver overrides: per-game settings are easier to test and reverse.

A repeatable optimization order

1. Run a baseline at the current preset.
2. Lower ray tracing.
3. Lower shadows and volumetrics.
4. Lower reflections and ambient effects.
5. Test view distance, crowds, and simulation.
6. Enable Quality upscaling or reduce render scale slightly.
7. Lower textures only when video-memory pressure points to them.
8. Test frame generation and latency options separately.
9. Play at least 15 minutes in a demanding area before saving.

What smooth play actually looks like

Watch motion, not only average FPS. Frame-time spikes appear as hitches even when the average looks good. Cap frame rate when the system cannot hold a higher target consistently, and use variable refresh rate when your supported display and system are configured for it. Microsoft describes VRR as matching the display's refresh behavior to delivered frames.

Finish with a per-game profile and keep a note of old values. AMD's guidance recommends per-application profiles for customized behavior.

Sources and methodology

• AMD: Configure Radeon Settings for gaming
• AMD: FidelityFX Super Resolution
• AMD: Anti-Lag, Boost, and Chill
• Microsoft DirectX Developer Blog: Windows graphics settings

Settings are ordered as a practical diagnostic sequence, not a universal benchmark ranking. Feature image is an original AI-assisted Loadout Ledger illustration, not a gameplay screenshot. No sponsorship or affiliate relationship influenced this guide. Sources reviewed September 10, 2026.