PC ports can look great, but the best experience usually comes from a few deliberate choices rather than pushing every slider to the maximum. This guide walks you through a repeatable process to tune Nioh 3 for smoother frame times, clearer image quality, and stable performance across a wide range of hardware.

Before you change settings: set a baseline

  1. Update GPU drivers (NVIDIA/AMD/Intel) and reboot.
  2. Disable background overlays you don’t need (recording, chat overlays, performance overlays). These can add stutter or input latency.
  3. Confirm your display mode and refresh rate in Windows and in-game (e.g., 144 Hz monitors often default to 60 Hz in some setups).
  4. Pick a target: 60 fps stable, 90–120 fps, or “best visuals at 60.” Your target determines which settings you should prioritize.

Step 1: Get resolution and upscaling right

Resolution choices have the biggest impact on performance and clarity. Start here before touching advanced graphics.

  • Native resolution: Use your monitor’s native resolution as a starting point.
  • Upscaling (DLSS/FSR/XeSS): If available, enable it when you need extra fps. Use Quality mode first; move to Balanced if you’re still short of your target.
  • Render scale: If the game offers render scale separate from resolution, treat it as a performance lever. Dropping to 90–95% is often less noticeable than lowering the output resolution.
  • Sharpening: Add a small amount only after you settle on upscaling/render scale. Too much sharpening can produce halos and flicker.

Step 2: Choose the right frame pacing settings (V-Sync, cap, VRR)

Smoothness is not just “high fps”; it’s consistent frame times.

  • If you have VRR (G-Sync/FreeSync): enable VRR in the GPU control panel and set the game to fullscreen (or borderless if VRR works reliably there). Then cap fps a little below refresh (e.g., 141 on a 144 Hz panel) for steadier pacing.
  • If you don’t have VRR: consider V-Sync ON to prevent tearing, then set an fps cap that your system can maintain (60 is a safe starting point).
  • Avoid “uncapped” while tuning: uncapped fps makes it harder to identify which settings are actually causing spikes and stutter.

Step 3: Tackle the “big hitters” first

Not all settings are equal. These tend to deliver the best fps gains per quality lost.

Shadows

  • What to lower first: shadow quality/resolution and shadow distance.
  • Recommended approach: drop one tier at a time until outdoor areas stop hitching during camera turns or big effects.

Ambient Occlusion (AO)

  • Effect: adds contact shadows in corners and around objects.
  • Optimization tip: set AO to a medium tier for a good compromise; turning it off can make scenes look flat.

Volumetrics / Fog / Lighting effects

  • Effect: dramatic atmosphere, but often expensive in combat with lots of particles.
  • Optimization tip: lower volumetrics before lowering textures.

Reflections

  • Effect: shiny surfaces and water reflections.
  • Optimization tip: reduce reflection quality or switch to a cheaper reflection mode if available.

Step 4: Keep texture quality high (unless you’re VRAM-limited)

Textures usually impact VRAM more than raw GPU compute. If you have enough VRAM, keep textures high for a sharper world.

  • Signs you’re VRAM-limited: sudden hitching when turning quickly, texture pop-in, or performance getting worse the longer you play.
  • Fix: reduce texture quality one step and restart the game (some engines only fully apply texture streaming changes after a restart).

Step 5: Anti-aliasing and image stability

If the game offers multiple AA methods, prioritize stability and reduced shimmer during motion.

  • With upscaling: you often need less additional AA. Try a moderate AA preset first.
  • If you see shimmering: increase AA quality slightly or reduce sharpening.

Step 6: Fix stutter with sensible CPU-side settings

Stutter can come from the CPU, storage, or shader compilation.

  • Close CPU-heavy apps (browser tabs, background sync, streaming tools) while testing.
  • Install on an SSD if possible to reduce streaming hitches.
  • Run a short “shader warm-up” route: load a busy area, spin the camera, trigger a few effects, then restart the level/area to see if stutter improves after caching.

Recommended presets (quick starting points)

Use these as a first pass, then adjust based on your fps target.

Performance (competitive smoothness)

  • Upscaling: Balanced (or Quality if already near target)
  • Shadows: Low–Medium
  • AO: Low–Medium
  • Volumetrics: Low
  • Reflections: Low
  • Textures: Medium–High (based on VRAM)
  • FPS cap: set to a value you can hold in the busiest fights

Balanced (best default)

  • Upscaling: Quality (or off at native if you have headroom)
  • Shadows: Medium
  • AO: Medium
  • Volumetrics: Medium
  • Reflections: Medium
  • Textures: High if VRAM allows

High Visuals (cinematic 60 fps target)

  • Upscaling: Quality (often better than brute-forcing native with heavy settings)
  • Shadows: High (reduce only if frame time spikes)
  • AO: High
  • Volumetrics: High (drop to Medium if combat gets uneven)
  • Reflections: High
  • Textures: High/Ultra if VRAM is sufficient

A simple testing loop (so changes actually stick)

  1. Pick a repeatable test spot: a combat encounter with particles, a wide outdoor view, and a fast camera pan.
  2. Change one setting category at a time (e.g., shadows), then retest.
  3. Watch for 1% lows and frame time spikes, not only average fps.
  4. When you hit your target, stop. Extra headroom is worth more than barely-noticeable visual gains.

Troubleshooting checklist

  • Game feels choppy even at high fps: verify refresh rate, disable double V-Sync (don’t force it both in driver and in-game), and use a sensible fps cap.
  • Input feels delayed: try lowering or disabling V-Sync (prefer VRR + cap), and turn off extra post-processing if it adds latency.
  • Frequent hitching: lower shadows/volumetrics, check VRAM usage, move install to SSD, and reduce background tasks.
  • Image looks grainy or over-sharpened: reduce sharpening, move upscaling from Balanced to Quality, or increase render scale slightly.

Once you’ve done the steps above, you should have a stable baseline you can keep across patches and driver updates—only minor tweaks should be needed later.