Free tools Windows power users keep installed
One-click scans. No signup required.
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
The best graphics settings are the ones that hold your chosen frame-rate target consistently in the busiest parts of the game while keeping the image clear enough for you. There is no universal “best” preset: performance changes with the RPG, patch, resolution, CPU, GPU, memory, driver, display and scene. Start by updating the game and driver, establish a repeatable test area, then change one demanding setting at a time—usually shadows, reflections or lighting—before adjusting render scale, textures, ray tracing and synchronization.
Use this guide to make deliberate trade-offs instead of dropping every option to Low. A smooth 60 frames per second (FPS) with readable detail is often preferable to a highly detailed preset that stutters during traversal or combat, but a 120-Hz display and a preference for competitive responsiveness may justify a different target.
What “smooth” should mean for your RPG
Smoothness is primarily about consistent frame delivery, not a single number shown by an overlay. A game that briefly reaches 100 FPS but repeatedly falls to 35 during city traversal can feel worse than one that stays near 60. Choose a target that matches your display and tolerance for latency, then tune for the difficult scenes rather than the quiet opening area.
Recommended Free Tools
Pick a realistic frame-rate target
- 60 FPS: A practical target for many single-player RPGs on 60-Hz displays. It leaves less headroom for sudden drops than a lower cap, so test dense towns, weather, combat and fast traversal.
- 90–120 FPS: Appropriate when you have a high-refresh display and value lower input latency. Reaching this range may require reduced effects or render scaling, especially at 2560×1440 or higher.
- 30–45 FPS: A defensible choice for cinematic play on hardware that cannot sustain 60. Consistency matters; an evenly paced 30 FPS can feel better than an unstable 45.
These are examples, not universal requirements. Set the target in the game’s own context and verify the minimums you actually encounter.
#1 Best Overall
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
Why the same preset behaves differently on different PCs
FPS reflects work shared by the graphics processor, processor and system memory. Resolution and visual effects usually load the GPU, while simulation, crowds, streaming and draw-call submission can load the CPU. Insufficient or heavily occupied RAM can cause hitching even when average FPS looks acceptable. A lower preset cannot solve every CPU, memory, storage or shader-compilation problem.
Prepare the system before changing image quality
Settings changes are meaningful only after basic software and system checks. Intel’s low-frame-rate guidance recommends checking game updates, graphics drivers and background activity before treating the preset as the cause.
- Record the baseline. Note the game and patch, operating system, CPU, GPU, installed RAM, output resolution, display refresh rate, current preset, upscaler or render-scale mode, ray tracing state and any frame cap. Save a screenshot of the graphics menu so you can reverse changes.
- Install the current game patch. Developers can change shader compilation, streaming and CPU workloads between patches. Re-test after an update instead of assuming an old result still applies.
- Install the appropriate graphics driver. Use the driver branch recommended for your GPU and restart if the installer requests it. A driver update can alter performance or introduce a game-specific profile, so compare in the same test area afterward.
- Close unnecessary background work. Browsers with many tabs, recording tools, launchers and synchronization utilities can consume CPU, memory or GPU time. Check Task Manager or your operating system’s equivalent while the game is running; unusually high background use is a diagnostic clue, not a graphics-setting problem.
- Use a repeatable test location. Choose a route that includes the traversal, combat, weather, crowd density or scenery where you notice slowdowns. Run the same route with the same camera movement for each comparison.
Run a controlled tuning pass
Change one variable at a time. If you alter shadows, anti-aliasing and resolution together, you cannot tell which compromise helped or which one damaged image quality.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
- Confirm the output mode. Select the display’s native resolution first if the game can sustain your target. Record whether the game is using exclusive fullscreen, borderless or windowed mode because behavior can differ with overlays and synchronization.
- Measure the baseline in the difficult area. Observe average FPS and, more importantly, visible dips, hitching and frame-time consistency. If the game provides a frame-time graph, use it; otherwise make the same pass several times and note repeatable drops.
- Lower shadows, reflections or lighting first. These options often represent expensive per-frame work. Move only one from Ultra to High or from High to Medium, repeat the route and inspect both motion and still image quality.
- Test other effects individually. If the target is still missed, try ambient occlusion, volumetric lighting, anti-aliasing, dynamic reflections or tessellation where those controls exist. Keep a short record of each change and its observed effect.
- Adjust render scale or an in-game upscaler. Reduce internal resolution in small steps, or select a supported quality mode, then inspect moving foliage, hair, text and distant geometry. Judge the result during actual play rather than from the menu preview.
- Tune texture quality separately. Textures primarily affect VRAM capacity and streaming. Lower them only when you see texture pop-in, delayed loading, hitching associated with VRAM pressure or a game-specific warning. Do not assume Ultra textures are harmful on every GPU, and do not assume Low is always faster.
- Test ray tracing last. Enable it only after the non-RT configuration meets your target, or leave it off when the effect would force unacceptable frame-time spikes. Compare the same scene with identical resolution and upscaling.
- Choose synchronization and a cap. After image-quality settings are stable, decide whether tearing, latency or uneven pacing is the bigger problem. Apply VSync or a frame-rate cap in a supported configuration and test again.
Which graphics settings usually matter most?
The labels and implementation differ by game. The table describes common trade-offs, not guaranteed FPS gains. A setting may be cheap in one engine and expensive in another, and a change that helps a GPU-limited scene may do little when the CPU is the bottleneck.
| Setting | What it changes | When to test it | Typical visual cost of lowering it |
|---|---|---|---|
| Shadow quality and distance | Resolution, filtering and the distance at which objects cast shadows | First group to test when GPU load is high | Less-defined or shorter shadows; shimmering may become more visible |
| Reflections | Screen-space, planar or other reflected scene detail | When water, windows or wet surfaces coincide with drops | Missing, noisier or lower-resolution reflections |
| Lighting and global illumination | Dynamic light interactions, bounce lighting and illumination detail | When scenes with many lights are slow | Flatter lighting or less accurate indirect light |
| Volumetric lighting or fog | Light shafts, fog and atmospheric scattering | When weather, interiors or god rays cause spikes | Less depth and fewer visible light beams |
| Ambient occlusion | Small contact shadows where surfaces meet | After the larger lighting controls | Objects can look less grounded |
| Anti-aliasing | Edge smoothing and temporal reconstruction | When render scale is already acceptable but GPU time remains high | More jagged edges, shimmer or ghosting depending on the mode |
| Tessellation or geometry detail | Surface subdivision and fine geometric features | When the game exposes it and distant detail is costly | Less rounded or detailed terrain and objects |
| Texture quality | Surface resolution and VRAM use | When VRAM pressure or streaming problems are evident | Blurrier surfaces; often little change to raw FPS if VRAM is sufficient |
| Render scale or upscaling | Internal rendering resolution before output | When you need a broad GPU workload reduction | Lower clarity, fine-detail loss or reconstruction artifacts |
| Ray tracing | Ray-based reflections, shadows or illumination | Last, after the target is met without it | Large workload increase in supported effects; visual benefit varies by scene |
Intel specifically identifies shadows, reflections and lighting as useful initial candidates and also lists anti-aliasing, dynamic reflections, ambient occlusion, volumetric lighting and render scaling among options to try. Treat that as a troubleshooting order, not a promise that one step produces a fixed percentage improvement.
Render scale and upscaling: the clarity–performance trade-off
Render scaling draws the 3D scene below the output resolution and then enlarges it. Because fewer pixels are shaded, a GPU-limited game may run faster, but text, foliage, distant edges and particle effects can look softer. The amount of blur or shimmer depends on the game’s reconstruction method, motion vectors and quality mode.
Rank #3
- 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
How to test a scale or upscaler
- Keep output resolution, camera route and effects unchanged.
- Compare the game’s native or 100% mode with the next supported quality step.
- Watch thin geometry, hair, foliage, fences, moving characters and UI text while turning the camera.
- Keep the lower scale only if the improvement in frame-time consistency outweighs the clarity loss at your normal viewing distance.
Supported upscalers and driver features vary by game and hardware. AMD describes Radeon Super Resolution as an in-driver upscaler, Boost as dynamic resolution adjustment in supported games, and Anti-Lag as a feature affecting input-to-display timing. Those are vendor descriptions, not guarantees that every RPG exposes the same controls or that enabling one will improve every system. Use the game’s documented option where possible, and verify the result in motion.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Textures are not the same as effects
Texture quality determines how detailed surfaces can appear when enough video memory is available. Lowering it may not materially raise FPS in a GPU-compute-limited scene, but it can prevent swapping and streaming stalls when VRAM is insufficient. Watch for textures that remain blurry, pop in late or load only after you stop moving; those symptoms point toward memory or streaming pressure.
NVIDIA’s Control graphics guide, published August 27, 2019, observed similar performance at Low, Medium and High texture resolution in its tested scenes, with a slight reduction at Ultra, and suggested moving from Ultra to High when textures took a long time to stream. That result belongs to Control, its scenes, hardware and settings; it is not a rule for open-world RPGs. Follow any VRAM guidance supplied by the RPG itself.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Ray tracing: optional detail with variable cost
Ray tracing can improve reflections, shadows or illumination, but its cost depends on resolution, the specific effect, hardware support and what is on screen. A busy reflective city street can behave very differently from a quiet forest. Test each RT effect separately if the game allows it, and compare with the same upscaling mode so that you are not attributing a resolution change to RT.
NVIDIA’s guide for Control explains that RT performance depends on screen resolution, RT hardware and scene content. It also notes that 2560×1440 contains 77% more pixels than 1920×1080; that is a pixel-count comparison, not a promise that FPS or rendering cost rises by exactly 77%. The guide’s measurements are specific to Control and should not be transferred to another RPG.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteIf enabling RT prevents your target, disable it or use a lower RT effect before sacrificing every other setting. Ray tracing is a visual preference, not a requirement for a smooth role-playing experience.
Best Value
- Next-Gen Intel Arc Graphics: Powered by Intel Arc A580 GPU with Intel Xe HPG microarchitecture, featuring 384 XMX engines for enhanced AI acceleration and content creation.
- High-Performance Memory: 8GB GDDR6 on a 256-bit interface running at 16 Gbps, delivering excellent bandwidth for 1440p gaming and creative workloads.
- Factory Overclocked: Engine clock set at 2000 MHz out of the box, providing optimized performance for smooth gameplay and multimedia tasks.
- Advanced Dual-Fan Cooling: Features a dual-fan design with striped axial fans and an ultra-fit heatpipe for efficient thermal management. 0dB Silent Cooling stops fans completely at low temperatures for silent operation.
- Durable Construction: Includes a stylish metal backplate for enhanced PCB rigidity and a premium aesthetic, backed by ASRock's Super Alloy components for long-term reliability.
VSync, frame caps and display behavior
VSync synchronizes presented frames with the monitor’s refresh cycle in supported configurations, which can reduce visible tearing. A frame-rate cap limits the maximum FPS and can reduce unnecessary GPU power, heat and fan noise when the cap is achievable. AMD describes Chill as a frame-rate regulation feature, Enhanced Sync as an alternative synchronization mode, and VSync as synchronization with monitor refresh; availability and behavior depend on the system, API and game.
These controls govern output timing and the maximum rate; they do not guarantee that shader compilation, asset streaming or CPU stalls disappear. If a cap is set above what the system can sustain, it will not prevent dips. If latency is your priority, compare capped and uncapped modes in the same route and choose the behavior that feels consistent on your display.
Find out whether the CPU or GPU is limiting you
Before buying hardware, identify the constrained component. A GPU that remains near full utilization while lowering effects or render scale raises FPS is a likely graphics limit. If GPU utilization falls while one or more CPU threads are saturated, lowering resolution may do little; crowds, simulation, draw calls or streaming may be the limit. High memory use, disk activity and repeated asset loading point to a broader system issue.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- GPU-limited pattern: Lowering shadows, reflections, lighting or render scale noticeably improves the difficult scene.
- CPU-limited pattern: Resolution and visual effects changes have little effect, while crowded areas or traversal remain slow.
- Memory or streaming pattern: Textures arrive late, the game hitches when entering new areas, or system memory and storage activity spike.
If updates, background-process checks and reasonable compromises still miss the target, Intel notes that a faster CPU or newer GPU may help. Choose an upgrade only after documenting the game, resolution, target, current hardware and confirmed bottleneck; a graphics card recommendation cannot be made responsibly without those details.
Practical decision paths
You want a stable 60 FPS at native resolution
- Keep native output resolution and disable RT temporarily.
- Reduce shadows, reflections or lighting one step and retest the difficult route.
- Adjust volumetrics, ambient occlusion and anti-aliasing only if needed.
- Use a modest render-scale reduction as a final GPU-side compromise, checking text and foliage for clarity loss.
- Apply a cap or VSync only after frame delivery is stable.
You have a high-refresh display and want lower latency
- Set a target your system can sustain in demanding scenes rather than chasing the menu’s maximum.
- Favor consistent frame times over Ultra textures or RT effects that create spikes.
- Test the game’s cap, VSync and any supported latency feature separately; record how input and tearing feel.
You see stutter but the FPS counter looks high
- Repeat the route after closing background programs and checking memory use.
- Confirm the game and driver are current.
- Watch for texture streaming, shader-compilation or CPU spikes rather than immediately lowering every visual option.
- Test a frame cap, then compare uncapped and synchronized output in the same scene.
Common mistakes and their fixes
| Mistake | Why it fails | Better approach |
|---|---|---|
| Choosing Ultra because it is the highest preset | Presets may spend performance on effects you barely notice and may not suit your hardware. | Use the target and repeatable test area to select each setting. |
| Lowering everything at once | You lose clarity without learning which option was responsible. | Change one control, repeat the route and record the result. |
| Judging an upscaler from a static menu | Motion reveals shimmer, ghosting and foliage loss that a still image hides. | Inspect moving gameplay, text and thin geometry. |
| Assuming a driver feature exists everywhere | Vendor options depend on GPU, API, game and configuration. | Verify the control is supported and test it in that RPG. |
| Blaming textures for every hitch | CPU work, RAM pressure, shaders and streaming can be responsible. | Check utilization, memory and asset-loading symptoms first. |
| Expecting VSync to cure all stutter | Synchronization cannot remove CPU stalls or loading pauses. | Treat it as an output and tearing decision after core tuning. |
A compact tuning checklist
- Write down hardware, patch, driver, resolution, refresh rate, preset, upscaling and RT state.
- Update the game and graphics driver.
- Close unnecessary background programs and inspect CPU and memory use.
- Choose a target based on your display and preference.
- Test a repeatable demanding route.
- Lower shadows, reflections or lighting one at a time.
- Continue with volumetrics, ambient occlusion, anti-aliasing or tessellation only as needed.
- Use render scaling or an upscaler when a GPU-wide reduction is necessary, and inspect clarity in motion.
- Adjust textures only for VRAM or streaming symptoms, using the game’s guidance.
- Leave ray tracing off or test it last if the target is not met.
- Choose VSync or a frame cap based on tearing, latency and pacing in your configuration.
- If compromises fail, determine whether the CPU, GPU or memory is limiting performance before considering an upgrade.
Make the trade-off deliberately
A smooth open-world RPG comes from matching settings to a measured target, not from copying a universal preset. Keep the options that visibly improve the world, reduce the expensive effects that do not, and validate every change in the same demanding gameplay. That method remains useful when a patch, driver, display or hardware upgrade changes the balance.
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.
