KCD2 PC Performance FAQ — Best Settings, DLSS, and Stutter Fixes
Why KCD2 stutters in Kuttenberg
Kuttenberg is the densest urban environment in KCD2 — hundreds of NPC pathing routines, complex building geometry, and intricate cobblestone textures push the streaming engine hard. On mid-range cards (RTX 3060, 4060), the texture-streaming pool fills faster than it can swap, causing 50-150ms hitches every time you turn a corner or enter a new district.
Warhorse acknowledged this stutter publicly and shipped patch v1.0.4 with a 'streaming buffer increase' fix. The patch helped (about 60% reduction in stutters) but didn't fully resolve it on cards with under 8GB VRAM. The community workaround is two .ini tweaks that further increase the streaming pool — these are unofficial but safe (Warhorse hasn't marked them as cheats and they don't affect achievements).
Steam Deck OLED runs Kuttenberg poorly without these tweaks (~25fps with stutters). With the tweaks applied, Steam Deck hits 40-50fps with smoother frame pacing — the difference between 'unplayable' and 'comfortable.'
Recommended settings by GPU tier
| GPU | Resolution | Preset | DLSS / FSR mode | Target FPS | |
|---|---|---|---|---|---|
| RTX 4090 / 7900 XTX | RTX 4090 / 7900 XTX | 4K native | Ultra | DLSS Quality (4070+) / FSR Quality | 120fps |
| RTX 4070 / 6800 XT | RTX 4070 / 6800 XT | 1440p | Ultra | DLSS Quality | 120fps |
| RTX 4060 / 6700 XT | RTX 4060 / 6700 XT | 1080p | High | DLSS Balanced | 90fps |
| RTX 3060 / 6600 XT | RTX 3060 / 6600 XT | 1080p | Medium | DLSS Performance | 60fps |
| RTX 2060 / 5500 XT | RTX 2060 / 5500 XT | 1080p | Low-Medium | DLSS Ultra Performance | 60fps |
| Steam Deck OLED | Steam Deck OLED | 800p (1280×800) | Low-Medium | FSR Performance | 40-50fps |
| Steam Deck LCD | Steam Deck LCD | 720p (1280×720) | Low | FSR Performance | 30-40fps |
The two .ini tweaks that fix Kuttenberg stutter
Open the file %APPDATA%\KingdomCome2\Engine\engine.ini in any text editor (Notepad works). Add or modify the following two lines under the [SystemSettings] section:
Line 1: r.Streaming.PoolSize=4096 — this increases the texture-streaming pool from the default 1024MB to 4096MB. Recommended for GPUs with 8GB+ VRAM. For 6GB VRAM cards, use 2048 instead. For 12GB+ VRAM cards (RTX 4070+), use 8192.
Line 2: r.MipMapLODBias=-0.5 — this loads slightly lower mip levels initially, reducing texture streaming load. The visual quality difference is imperceptible during gameplay but the streaming load drops by ~30%.
Save the file. Restart KCD2. The Kuttenberg stutter should drop from frequent 50-150ms hitches to occasional 5-10ms blips. Steam Deck users see the largest improvement.
Settings impact ranking — biggest performance killers
| Setting | Performance cost | Visual benefit | Recommendation | |
|---|---|---|---|---|
| Volumetric Fog Ultra | Volumetric Fog Ultra | -15-20% fps | Subtle atmosphere | ALWAYS disable on mid/low-tier |
| Shadow Quality Ultra | Shadow Quality Ultra | -12-15% fps | Sharper distant shadows | Use High instead (90% of quality, 25% less cost) |
| Texture Streaming Ultra | Texture Streaming Ultra | -8-10% fps + VRAM use | Cleaner LOD transitions | Use High; combine with .ini pool tweak |
| Ray-Traced Reflections | Ray-Traced Reflections | -25-35% fps | Realistic water/glass | ONLY on RTX 4070+ at 1440p+ |
| Hair Strands | Hair Strands (TressFX) | -5-8% fps | Realistic Henry hair physics | Optional — looks great but costly |
| Foliage Density Ultra | Foliage Density Ultra | -3-5% fps | Denser grass / shrubs | Use High — visual delta minimal |
DLSS vs FSR vs XeSS — honest comparison
DLSS (NVIDIA-only) is the best upscaler for KCD2. At 'Quality' mode (renders at 67% of native), DLSS preserves nearly all texture detail and adds minimal ghosting on Henry's hair. Performance uplift: +25-35% fps depending on tier.
FSR 3.1 (AMD + cross-vendor) is the best non-NVIDIA option. FSR Quality is about 90% as good as DLSS Quality in visual fidelity — slight ghosting on fast-moving foliage and Henry's facial detail loses some sharpness. Performance uplift: +30-40% fps. Use FSR if you don't have an RTX card.
XeSS (Intel-developed, works on AMD/Intel/NVIDIA) is the third option. XeSS Quality lags DLSS by ~10% fidelity and FSR by ~5%. Performance uplift similar to FSR. Use XeSS only if you have an Intel Arc GPU.
All three upscalers benefit Kuttenberg performance more than open-world Trosky. In Kuttenberg the GPU is the bottleneck (lots of geometry); upscalers help. In open-world Trosky the CPU/streaming is the bottleneck; upscalers help less.
Upscaler quality and performance comparison
| Upscaler | Quality mode fidelity | Performance uplift | Best for | |
|---|---|---|---|---|
| DLSS Quality | DLSS Quality (NVIDIA) | 98% native | +25-35% fps | RTX 2060+ users |
| FSR Quality | FSR 3.1 Quality | 90% native | +30-40% fps | AMD / cross-vendor |
| XeSS Quality | XeSS Quality (Intel) | 85% native | +25-35% fps | Intel Arc users |
| Native | Native rendering (no upscaler) | 100% native | Baseline | Top-tier GPUs at lower res only |
Verdict: Use DLSS if you have an RTX card — it's the most balanced option. FSR is a strong second choice for non-NVIDIA users. XeSS is third-tier; only pick if you have Intel Arc. Native rendering is rarely the right call for KCD2 unless you have a 4090.
Steam Deck OLED settings — comfortable 45fps target
| Setting | Recommended value | |
|---|---|---|
| Resolution | Resolution | 800p (1280×800) native |
| Preset | Preset | Low-Medium custom (see below) |
| Texture Quality | Texture Quality | Medium |
| Shadow Quality | Shadow Quality | Low |
| Volumetric Fog | Volumetric Fog | Off |
| Anti-aliasing | Anti-aliasing | FSR Performance (renders 50% native) |
| Foliage Density | Foliage Density | Medium |
| Draw Distance | Draw Distance | Medium |
| .ini tweak | .ini tweak r.Streaming.PoolSize | 2048 (Steam Deck VRAM tier) |
| Expected FPS | Expected FPS in Kuttenberg | 40-45fps with smooth pacing |
Step-by-step performance optimisation workflow
- Update GPU drivers to the latest stable version (NVIDIA Game Ready or AMD Adrenalin). Day-zero patches are critical.
- Launch KCD2. Set resolution to your monitor's native (or 1440p if you have a 4K monitor and a 4060-tier card).
- Open Graphics Settings. Disable Volumetric Fog (or set to Off). Set Shadow Quality to High.
- Enable DLSS (or FSR for AMD) at Quality mode. Verify FPS improvement in Kuttenberg.
- Close KCD2. Open %APPDATA%\KingdomCome2\Engine\engine.ini in Notepad.
- Add the two tweaks: r.Streaming.PoolSize=4096 (or 2048 on 6GB VRAM, 8192 on 12GB+) and r.MipMapLODBias=-0.5.
- Save the file. Restart KCD2.
- Test Kuttenberg performance — stutters should drop dramatically. Adjust pool size up/down based on your VRAM headroom.
- If still stuttering: disable Ray-Traced Reflections. They add 25-35% GPU cost for minimal visual gain.
- Lock in your config. Use NVIDIA Control Panel or AMD Adrenalin to set a per-game power profile (Maximum Performance) for KCD2.
Common performance mistakes
- Running at Ultra preset because it's the default. Ultra is calibrated for screenshots; drop to High for 20-25% free fps.
- Not applying the .ini tweaks. The Kuttenberg stutter is unsolvable without them on mid-range cards.
- Using FSR Performance instead of FSR Quality. Performance mode renders at 33% native — texture clarity collapses. Always start with Quality.
- Enabling Ray Tracing on RTX 4060 or below. Performance cost outweighs visual gain on mid-tier cards.
- Trying to play at 4K on RTX 4060. Drop to 1440p with DLSS Quality for 90fps; vs 1080p native gives nearly identical clarity at higher framerate.
- Forgetting to set NVIDIA Control Panel to Maximum Performance for KCD2. Idle GPU clocks hurt during open-world transitions.
Frequently asked questions
What are the best KCD2 PC settings?
Depends on GPU tier. RTX 4070: Ultra @ 1440p/120fps with DLSS Quality. RTX 4060: High @ 1080p/90fps with DLSS Balanced. RTX 3060: Medium @ 1080p/60fps with DLSS Performance. Steam Deck OLED: Low-Medium @ 800p/40-50fps with FSR Performance. ALWAYS disable Volumetric Fog and Ray Tracing on mid-tier cards.
How do I fix the KCD2 Kuttenberg stutter?
Two .ini tweaks in %APPDATA%\KingdomCome2\Engine\engine.ini: (1) r.Streaming.PoolSize=4096 (2048 on 6GB VRAM, 8192 on 12GB+); (2) r.MipMapLODBias=-0.5. These increase the texture streaming pool and reduce streaming load, dropping Kuttenberg stutter from 50-150ms hitches to 5-10ms blips.
Is DLSS or FSR better in KCD2?
DLSS Quality is ~98% of native fidelity; FSR Quality is ~90%. DLSS is the better choice if you have an NVIDIA RTX card. FSR is the best non-NVIDIA option. XeSS is third-tier — only pick if you have an Intel Arc GPU. All three help Kuttenberg performance more than open-world Trosky.
Should I enable Ray Tracing?
Only on RTX 4070+ at 1440p+. Ray Tracing costs 25-35% fps for marginal visual gain. Combined with Frame Generation on RTX 4090, it's playable. On RTX 4060 or below, the performance hit isn't worth the visual improvement — disable RT and use the saved fps for other settings.
Why does KCD2 run badly on my Steam Deck?
Default settings + no .ini tweak = ~25fps in Kuttenberg with frequent stutters. Apply r.Streaming.PoolSize=2048 + r.MipMapLODBias=-0.5 to the .ini file (accessible via Steam Deck's developer mode). Set Volumetric Fog to Off, Shadow Quality to Low, FSR to Performance mode. Expected result: 40-45fps with smoother frame pacing.
Does Frame Generation work in KCD2?
Yes on RTX 4000 series — but it requires Ray-Traced Reflections to be enabled. On RTX 4060 this is a trap (RT alone costs 30% fps; Frame Gen restores most of it but adds latency). On RTX 4070+ the latency is masked by higher base framerate. Use Frame Gen only on RTX 4070+ at 1440p+.
What's the single biggest performance killer in KCD2?
Volumetric Fog at Ultra. Costs 15-20% fps for subtle atmospheric effect that most players don't notice. Always disable or drop to Medium. Second biggest killer: Shadow Quality Ultra (12-15% fps cost for minimal visual gain over High). Third: Ray-Traced Reflections (25-35% fps cost on cards below RTX 4070).
Sources & verification
Coloured pills follow our four-tier source policy.
Continue this guide path
- ›KCD2 Spoiler-Free FAQ — Length, Choices Carry-Over, Replay ValueHow long is KCD2, do KCD1 choices carry over, is it worth replaying? This spoiler-free FAQ answers the questions buyers ask before opening any review or walkthrough — covering length, accessibility, save imports, and replayability.
- ›Kingdom Come: Deliverance 2 Beginner Guide — Combat, Skills, and Your First DaysKCD2 throws you in with minimal hand-holding. This guide covers what to learn in your first hours, the skill priorities that compound fastest, and the survival basics the tutorial barely explains.
- ›KCD2 Hardcore Mode Guide — Negative Perks, No Map & Survival TipsHardcore Mode removes the map, the compass, and most of Henry's autopilot. This guide ranks negative perks by pain level, recommends a starting region, and lists the essentials for hour one.
- ›KCD2 DLC Roadmap FAQ — Brushes With Death, Legacy of the Forge, MysteriaWarhorse announced three KCD2 DLCs at launch and details have trickled out since. This FAQ collects every confirmed feature, release window, and price tier for Brushes With Death, Legacy of the Forge, and Mysteria.
- ›KCD2 Save System Explained — Savior Schnapps, Beds & Auto-Save RulesKCD2 won't autosave when you want it to and will autosave when you don't. This guide spells out every save trigger, what Savior Schnapps really costs, the hardcore-mode rules people misread, and console differences that change save behaviour.