What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For most games, start at 1920×1080 with the High preset, DLSS Super Resolution on Quality, ray tracing off or limited, NVIDIA Reflex on, and a frame cap that matches your monitor. Add Multi Frame Generation only after the game already delivers a sufficiently high, responsive base frame rate. This combination usually gives the RTX 5060 a better balance of image quality, frame-time consistency and latency than blindly selecting Ultra.
The RTX 5060 can produce much higher displayed frame rates in supported titles, but a frame counter alone is not the goal. Native or reconstructed base frames determine input response; generated frames mainly add visual smoothness. Tune for the refresh rate and type of game you actually play.
Recommended RTX 5060 settings at 1080p
Use this as a starting profile, then adjust individual options after testing a repeatable scene in each game.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Setting | Starting value | When to change it |
|---|---|---|
| Resolution | 1920×1080 | Keep native unless you deliberately target a lower internal resolution. |
| Graphics preset | High | Raise specific textures or effects only after frame times are stable. |
| DLSS Super Resolution | Quality | Use Balanced when the GPU cannot hold your target and image quality remains acceptable. |
| Frame generation | Off initially | Enable Multi Frame Generation in supported single-player games after checking base FPS and latency. |
| NVIDIA Reflex | On | Especially useful when frame generation is enabled. |
| Ray tracing | Off or selective | Enable only effects that visibly improve the scene; reduce RT before abandoning the whole raster preset. |
| Dynamic resolution | Off initially | Use it when maintaining a fixed target matters more than consistent image detail. |
| Frame cap | 60 FPS for 60 Hz; slightly below refresh on VRR | Set the cap to your display goal rather than chasing an uncapped peak. |
NVIDIA has demonstrated RTX 5060 systems at 1080p with maximum settings, DLSS Super Resolution and Multi Frame Generation, and says the card can exceed 100 FPS at 1080p in supported demanding games under its stated test conditions. Those are showcase results, not a universal promise for every game. Independent testing is title-specific: TechRadar reported more than 200 FPS in Doom: The Dark Ages at 1080p Ultra Nightmare with DLSS 4 and Multi Frame Generation on its test system. Your processor, game patch, driver, memory and selected effects can produce very different results.
#1 Best Overall
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Why High is usually better than Ultra
Ultra presets often spend a disproportionate amount of GPU time on effects that are difficult to notice during play: very dense shadows, distant foliage, volumetric fog, reflections and crowd simulation. At 1080p, those costs can reduce frame-time consistency without delivering a proportional improvement over High.
High also leaves headroom for selectively increasing texture quality or a favored effect. This is preferable to choosing Ultra, discovering stutter, and then lowering several settings at once without knowing which one caused the problem. Make one change at a time and watch average FPS, the lowest repeated frame times and subjective smoothness.
Textures and VRAM
Texture quality is often one of the least expensive ways to improve appearance when the RTX 5060 has enough video memory. It can become expensive when a game loads a high-resolution texture pack or when the VRAM meter approaches its limit. A full VRAM allocation does not always mean failure, but warnings, hitching when turning the camera and delayed texture streaming are signs to lower texture resolution or remove the optional pack.
Shadows, volumetrics and reflections
These settings commonly affect frame time more than small geometry or post-processing options. If the High preset is close to your target, reduce volumetric fog or clouds, then shadows and reflections before lowering the entire preset. The exact order varies by engine, so verify each change in the same demanding scene.
DLSS Quality, Balanced or Performance?
DLSS Super Resolution renders internally below 1920×1080 and reconstructs the output. Quality generally preserves the clearest fine detail and is the correct first choice for an RTX 5060 at 1080p. At this output resolution, switching too quickly to a more aggressive mode can make thin wires, foliage, distant text and motion detail look unstable.
Use DLSS Quality when
- The game is near your desired frame rate but needs modest GPU headroom.
- You play a visually detailed single-player title and notice shimmering or softness easily.
- You can maintain your monitor target without lowering other settings.
Move to DLSS Balanced when
- The GPU is fully loaded and Quality cannot maintain your chosen cap.
- You have already reduced expensive ray-traced or volumetric effects.
- The image remains acceptable in motion, not only in a paused screenshot.
Reserve Performance for exceptional cases
Performance can help a very demanding ray-traced game reach a practical target, but its lower internal resolution is more obvious at 1080p. Use it only after deciding that smoother motion is more important than fine image detail. If the processor is the bottleneck, changing DLSS mode may do little because the GPU was not waiting on rendering work.
Native rendering versus DLSS at 1080p
Native 1920×1080 rendering gives the game the full output resolution, but it can leave less GPU headroom for demanding effects. DLSS Quality lowers the internal workload and reconstructs the final image. The best choice depends on the target: native can be sensible in a lightweight competitive game that already exceeds the display refresh, while Quality is usually preferable when a demanding title needs extra headroom.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesCompare both modes while moving, not from a static screenshot. Look at foliage, fences, hair, distant signage and particle effects. A mode that looks sharp in a paused frame may shimmer during a camera pan. Conversely, a modest amount of reconstruction softness may be less distracting than inconsistent frame times. If native rendering already holds the cap with acceptable latency, there is no requirement to enable DLSS.
Frame generation: smoother motion, not free latency
DLSS Multi Frame Generation uses AI to insert additional frames on GeForce RTX 50-series GPUs. The displayed FPS counter can rise substantially, but generated frames do not replace the work required to render game frames or remove a CPU limit. Input latency is tied more closely to the base rendered frame rate and the game’s input pipeline than to the number shown after interpolation.
When to enable Multi Frame Generation
- The game supports it and is primarily single-player or otherwise tolerant of a little additional latency.
- Base rendered FPS is already reasonably high and stable before generation.
- Reflex is available and enabled.
- You have checked for obvious ghosting, HUD artifacts or uneven pacing in your usual camera movements.
When to leave it off
- Competitive shooters or other latency-sensitive games where immediate response matters more than cinematic smoothness.
- A title whose native or DLSS-rendered base FPS is low or erratic.
- Scenes where generated frames produce distracting artifacts.
Test with the same route through a demanding area, not only an empty room. Compare aiming, rapid camera turns and frame-time behavior. If the game feels delayed despite a high displayed counter, disable generation or raise base FPS by reducing expensive settings.
Ray tracing without sacrificing smoothness
Ray tracing can transform reflections, shadows or global illumination, but the cost differs greatly by effect and engine. Start with raster High settings and RT disabled. Then enable only the effect that materially improves the scenes you care about.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Enable one RT effect, such as reflections or shadows, while leaving other RT options off.
- Replay the same demanding scene and check frame-time consistency, not just the average.
- If the target is missed, lower that RT effect first, then volumetric fog or reflections.
- Use DLSS Balanced only if Quality cannot hold the target after those changes.
- Add frame generation only after the base result feels responsive.
This approach preserves most of the High raster image while controlling the largest RT cost. A game’s built-in labels are not standardized: “medium” RT in one engine can cost more than “high” in another.
Raster performance versus RT image quality
Ray-traced lighting is not automatically the best use of every frame. In a fast game, a stable raster High image may look better in motion than a sharper-looking RT preset that repeatedly drops frames. If reflections are the only RT feature you value, enable reflections and leave RT shadows or global illumination disabled. If the scene barely changes when an effect is toggled, spend that performance budget elsewhere.
Presets for common 1080p goals
| Goal | Suggested settings | Trade-off |
|---|---|---|
| Competitive shooters | High/Medium mix, RT off, DLSS Quality or native when comfortably fast, Reflex on, conservative cap | Lowest latency over maximum detail |
| General 60–90 FPS play | High, DLSS Quality, limited RT, cap to the display | Balanced image quality and consistency |
| High-refresh single-player | High, DLSS Quality, selective RT, Multi Frame Generation when supported, Reflex on | Smoother displayed motion with possible generated-frame latency or artifacts |
| Very demanding RT title | High raster settings, reduced RT, DLSS Balanced if needed, frame generation optional | Preserves lighting effects while controlling frame time |
Match the profile to the display rather than to an arbitrary benchmark number. A 60 Hz monitor cannot show every frame from a 200 FPS counter, while a 144 Hz VRR panel benefits from a stable result near its refresh range. High-refresh single-player games can trade some latency for smoother camera motion; esports titles generally should not.
Set the frame cap correctly
For a 60 Hz fixed-refresh display, cap at 60 FPS if the game can hold it. On a variable-refresh-rate display, cap slightly below the panel’s maximum refresh so the game remains inside the adaptive-sync range; the exact value depends on the monitor and driver behavior. A stable 90 FPS cap is usually preferable to an uncapped result that swings between 70 and 130 FPS.
Use the game’s limiter when it provides a reliable result. Otherwise, the driver-level limiter can enforce a consistent ceiling. Keep V-Sync, adaptive sync and the cap configured deliberately rather than enabling every option simultaneously and assuming they cooperate.
Hardware and software checks before tuning
Confirm that the monitor is actually set to its intended refresh rate in the operating-system display panel. A high-refresh screen left at 60 Hz changes the useful target and can make a perfectly good frame rate appear wasted. On a laptop, connect power, select the performance graphics mode if available and verify that the game is assigned to the discrete GPU rather than integrated graphics.
Install a current stable NVIDIA driver and restart when requested. Let a title complete shader compilation after a driver or game update before judging traversal stutter. Close unnecessary overlays and background capture tools while testing, because they can alter CPU load and frame pacing. Keep the same resolution, cap and test route when comparing settings.
Step-by-step tuning procedure
- Confirm the correct GPU. In the game’s video menu and your operating-system graphics settings, verify that the discrete RTX 5060 is selected. A laptop may otherwise launch on integrated graphics.
- Update the graphics driver. Install a current stable driver, restart if requested, and retest before changing a dozen options.
- Apply the baseline. Select 1920×1080, High, DLSS Quality, RT off or limited, Reflex on and an appropriate cap.
- Choose a repeatable test. Use the same level, save, benchmark run or busy multiplayer route. Record average FPS and whether camera movement stutters.
- Identify the limit. Near-100% GPU utilization usually indicates a graphics limit; a busy CPU thread with lower GPU usage suggests a processor or simulation limit.
- Change one setting. Reduce RT, volumetrics, reflections, shadows or crowd density in that order when GPU-limited. Keep textures higher unless VRAM symptoms appear.
- Recheck VRAM. If the game warns or stutters, lower texture resolution or remove high-resolution packs.
- Try DLSS Balanced. Do this only after the major expensive effects are controlled and only if Quality misses the target.
- Test frame generation. Enable it for supported single-player games when base FPS is already stable; compare responsiveness and artifacts.
- Lock the result. Set the cap to the monitor goal and keep the profile as your per-game baseline.
Do not change the preset, DLSS mode, RT, cap and driver all at once. Isolating changes tells you whether a gain came from reducing GPU work, removing a CPU bottleneck or simply hiding an unstable peak behind frame generation.
Rank #2
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
Troubleshooting common problems
High FPS but the game still feels sluggish
Check the base rendered FPS with frame generation disabled, then enable Reflex and retest. A high post-generation counter can hide low base FPS or CPU latency. Lowering the cap slightly can also prevent large frame-time swings.
Stutter when entering new areas
Watch for VRAM warnings, shader compilation pauses and asset-streaming behavior. Reduce texture resolution or optional texture packs if memory is full. Allow the game to finish any shader compilation process before judging the final result, and avoid changing drivers and settings repeatedly during that process.
DLSS looks blurry or shimmers
Return to Quality, disable excessive sharpening, and check whether the game’s anti-aliasing or film-grain controls interact with reconstruction. If the title offers a newer DLSS model, test it in motion rather than relying on a still image.
Ray tracing causes sudden drops
Disable the most expensive RT effect first, usually reflections or global illumination, then reduce volumetrics. Keep the raster preset at High instead of lowering every setting equally.
The GPU is not fully utilized
A CPU, frame cap, background process or engine limit may be responsible. Confirm the cap is not active, close unnecessary overlays, and compare a less crowded scene. DLSS changes will not solve a processor-bound frame rate.
Dynamic resolution keeps changing the image
Dynamic resolution is useful when a fixed performance target matters more than fixed detail. If visible resolution shifts distract you, turn it off and use a fixed DLSS mode with a lower cap or reduced RT settings instead. If the game cannot hold its target even after sensible reductions, dynamic resolution may be the least objectionable compromise.
How to judge smoothness accurately
Average FPS is useful for a headline number, but frame-time consistency determines whether camera movement feels smooth. Test a repeatable scene for several minutes, include traversal and combat where possible, and note the lowest recurring frame-time spikes. Compare settings with the same cap and resolution. A lower but stable 60 FPS can feel better than an uncapped result with frequent hitching.
Evaluate three separate measurements:
- Base rendered FPS: the frames the game actually renders and the main determinant of response.
- Displayed FPS: the counter after DLSS Multi Frame Generation, useful for perceived motion but not equivalent to native rendering.
- Input latency: how quickly an action appears on screen, affected by CPU load, render queue, Reflex, frame pacing and the game itself.
Keep a short note for each title: resolution, preset, DLSS mode, RT effects, frame-generation state, cap and the scene tested. This prevents chasing a setting that helped one game but harms another.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What the RTX 5060 can and cannot guarantee
The card supports DLSS 4, ray tracing, neural rendering and Reflex. NVIDIA’s published claim of over 100 FPS at 1080p in the most graphically advanced games applies to its stated test conditions and supported features. The result should not be treated as a cross-game average. Engines, patches, CPUs, memory configurations and RT implementations vary too much for one universal FPS number.
Likewise, a demonstration above 200 FPS in Doom: The Dark Ages with DLSS 4 and Multi Frame Generation shows what a specific title and test system can achieve, not what every RTX 5060 owner will see. Use the baseline profile, then tune toward your display’s target and your tolerance for latency, reconstruction artifacts and RT detail.
Frequently Asked Questions
What are the best RTX 5060 settings for 1080p?
Use 1920×1080, the High preset, DLSS Quality, RT off or selective, Reflex on and a frame cap matched to your monitor. Raise individual textures or effects only after frame times are stable.
Should I use DLSS Quality or Balanced at 1080p?
Start with Quality because it preserves more fine detail at 1080p. Move to Balanced only when the GPU cannot hold your target after reducing expensive RT, volumetric and reflection settings, and only if the moving image remains acceptable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is Multi Frame Generation worth using at 1080p?
It can improve perceived smoothness in supported single-player games when base FPS is already high and stable. It does not remove CPU limits or make latency identical to native rendering, so competitive players should generally prioritize native or DLSS-rendered FPS and responsiveness.
Can the RTX 5060 run Ultra settings with ray tracing?
It can in some titles, especially with DLSS and frame generation, but there is no universal Ultra guarantee. High raster settings with selective RT usually deliver more consistent frame times; reduce the most expensive RT effect before lowering every setting.
Why does my FPS stay low after enabling DLSS?
You may be CPU-limited, capped by the display, limited by a game-engine thread or running on integrated graphics. Check GPU utilization, the active GPU, the frame cap and CPU load before switching to a more aggressive DLSS mode.
What should I lower first when performance drops?
Confirm drivers and the discrete GPU, then reduce ray-traced effects, volumetric fog or clouds, reflections, shadows and crowd density. Check VRAM before lowering textures; reduce texture resolution or remove high-resolution packs when warnings or streaming hitching appear.
What frame cap should I use?
Use 60 FPS for a 60 Hz fixed-refresh display. With VRR, cap slightly below the panel’s maximum refresh so the game stays within the adaptive-sync range. A stable cap is preferable to an uncapped result with large swings.
Does a high displayed FPS number mean low latency?
No. Separate base rendered FPS, displayed FPS after frame generation and input latency. Generated frames can make motion look smoother while response remains closer to the base frame rate and is affected by CPU load, Reflex and frame pacing.
The Bottom Line
For smooth 1080p RTX 5060 gaming, begin with High, DLSS Quality, limited ray tracing, Reflex and a display-matched frame cap. Reduce RT and other heavy effects before sacrificing the whole preset. Use Balanced only when Quality misses the target, and enable Multi Frame Generation only when a stable, responsive base frame rate already exists.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
