STALKER 2 Cost of Hope Settings: Fix the Iron Forest and CNPP FPS Drops (Update 2.0)

Cost of Hope didn’t just add two zones to STALKER 2 – it shipped alongside Update 2.0, which swapped the game’s rendering engine from Unreal Engine 5.1 to 5.5.4. That’s why the settings that worked in Zaton or the Garbage don’t automatically carry over: Iron Forest and the Chornobyl Nuclear Power Plant each stress a different part of your PC, and a flat High preset tuned for the base game isn’t built for either one. If you’re still running the settings from our base-game STALKER 2 settings guide, expect at least one of them to need a second look once you load into the Cost of Hope zones.

Quick Start: The Settings That Actually Fix Cost of Hope’s FPS Problem

Iron Forest tanks your GPU with foliage density. The Chornobyl Nuclear Power Plant (CNPP) tanks your frame times with interior lighting, not foliage. Treating both zones with one generic settings profile is why performance still feels wrong even after you’ve already tuned the base game. Work through this list in order:

1. Confirm you’re actually on Update 2.0 with Cost of Hope installed (check the version number under Options > About) – every recommendation below assumes the Unreal Engine 5.5.4 build, not the original 5.1 release [1][7].
2. Leave the new ASYNC Compute toggle on – it ships enabled by default post-update, and switching it off costs frame time for no visual benefit [1].
3. NVIDIA RTX 40/50-series: enable Reflex “Boost” mode, which replaces the old flat Reflex On. AMD RX 9000-series: enable Anti-Lag 2 for the equivalent effect [1].
4. Set Foliage to Medium before you enter Iron Forest specifically – it’s the single setting with the largest measured swing in that zone.
5. Set Global Illumination/Lumen to Medium (not Off) inside the CNPP – the reworked indirect lighting is the DLC’s visual centerpiece there, and dropping it to Off looks worse without fixing the real bottleneck.
6. Clear your DirectX shader cache once after installing the update, before judging final performance – the DLC’s new assets have to compile shaders once regardless of your hardware [4].
7. Match your upscaling technology to your GPU generation rather than copying one blanket setting for every card (decision tree below).

Not every player needs the same priority order. Use whichever row below matches you:

Why Cost of Hope Changed the Performance Math

Update 2.0 is the biggest engine overhaul STALKER 2 has had since its November 2024 launch, moving from Unreal Engine 5.1 to 5.5.4 alongside the Cost of Hope release on August 20, 2026 [2][7]. The headline change is more indirect light bounce off surfaces – warmer, more physically grounded ambient lighting both outdoors and in interiors – plus reworked landscape and foliage rendering [1][7]. GSC’s own framing is that the game runs “slightly faster on both the graphics card and the processor” post-update [7], and independent before/after testing backs that up unevenly across scenario types: GPU-limited outdoor areas went from roughly 60 to 72 fps, populated towns from 50 to 65 fps with less stutter, and CPU-intensive areas from 48 to 54 fps [6].

That unevenness matters more than the average. A patch that mostly helps GPU-bound outdoor scenes and populated towns doesn’t automatically help every new area the DLC adds – it depends on which resource each zone actually taxes, which is why Iron Forest and the CNPP need separate treatment below rather than one shared “best settings” list.

Iron Forest: Foliage Is the Zone’s Real Bottleneck

Iron Forest is a fully explorable region built around dense woodland, unexplained electrical anomalies, and a heavy concentration of points of interest and mutant threats [3]. The Update 2.0 foliage rework increases vegetation density and visual fidelity throughout zones like this one [3], which is good for atmosphere and bad for your frame rate if you leave Foliage at Epic – each individual plant is typically rendered as a fully lit, wind-simulated mesh at higher quality tiers rather than a distant billboard – a standard trade-off behind most Foliage quality sliders in Unreal Engine titles.

Set Foliage to Medium, not Low, as your starting point. Outdoor, foliage-dense areas showed the biggest swing in GamersAndGeek’s before/after Update 2.0 testing – GPU-limited outdoor zones gained roughly 12 fps post-patch [6] – and Iron Forest is exactly that kind of terrain: wide-open forest with vegetation density throughout, not an isolated pocket of trees. Dropping Foliage all the way to Low recovers a little more headroom but strips enough visual density that ambush points and anomaly clusters get harder to read at a glance, which works against you in a zone this hazard-dense. Pair Foliage Medium with Hair at Medium too – Iron Forest’s mutant roster leans on fur-based creatures, and Hair carries its own 10-17% performance swing on mid-range hardware, per our base-game settings testing.

Chornobyl Nuclear Power Plant: Indoor Lighting Without the Frame-Time Spikes

The CNPP was historically inaccessible in STALKER 2 and is one of Cost of Hope’s two headline additions, gated behind story progression and built as a full interior hub with its own quest chains [2][3]. Where Iron Forest’s cost is foliage, the CNPP’s cost is indirect lighting – Update 2.0’s biggest visual change is exactly the kind of light-bounce-heavy rendering an industrial interior full of metal and concrete surfaces puts to work [7].

Run Global Illumination/Lumen at Medium rather than Epic inside the plant – Medium keeps the reworked indirect lighting that makes the interior read correctly without paying for the highest-fidelity light-bounce calculations the CNPP’s geometry demands. Keep Reflections and Shadows at High rather than Epic for the same reason: the visual gap between High and Epic on these two settings is minor, while the frame-time cost of pushing them to Epic isn’t. Leave Motion Blur off, as with every other zone – it adds nothing to readability in tight interior corridors and only costs clarity when you’re moving fast under fire.

One distinction worth making explicit: if your frame rate holds steady but the game freezes for a fraction of a second the moment you walk into a new room, that isn’t a Global Illumination problem – it’s shader compilation stutter, and it needs a different fix entirely (below), not a lower graphics preset.

New Settings Menu Options: Which Ones You Should Actually Enable

Update 2.0 added four settings that didn’t exist before Cost of Hope, and which ones help you depends entirely on your hardware generation [1]:

• ASYNC Compute – a new toggle, on by default. Leave it on unless you’re actively troubleshooting a driver crash; there’s no frame-time benefit to disabling it.
• NVIDIA Reflex “Boost” – replaces the old binary Reflex On/Off for RTX 40 and 50-series cards, trimming render-queue latency further than plain Reflex did. Older RTX 20/30-series cards still only get the standard Reflex On option.
• Official FSR 4 support – now selectable in-game rather than requiring a driver-level override, but it only runs on AMD’s RX 9000-series hardware. RX 7000/6000-series owners should stay on FSR 3.1 Quality with Frame Generation; FSR 4 isn’t available on that silicon regardless of what the menu shows.
• AMD Anti-Lag 2 – AMD’s equivalent to Reflex, now supported, meaning both vendors finally have their strongest latency-reduction option available in this game.

As a decision tree: RTX 40/50-series owners should pair DLSS Quality with Reflex Boost. RX 9000-series owners should pair FSR 4 with Anti-Lag 2. Everyone on older hardware from either vendor keeps the same upscaling stack the base-game settings guide already recommends. For the system-level side of performance – background processes, power plans, and driver settings that affect every game, not just this one – see our full PC optimization guide.

Fixing Shader Compilation Stutter After Installing Cost of Hope

Every new area the DLC adds means new shaders your GPU has never compiled before, and STALKER 2 compiles many of them the first time you physically walk into the room that uses them rather than during the loading screen – that’s the freeze described above, and it’s a one-time tax per area, not a sign your settings are wrong [4].

Start by clearing your DirectX shader cache through Windows Settings > System > Storage > Temporary Files, then let the game rebuild it from scratch [4]. STALKER 2 also keeps its own pipeline cache as .upipelinecache files under %localappdata%\Stalker2\Saved, and Steam maintains a separate cache at steamapps\shadercache\1643320 – clearing both alongside the Windows-level cache gives the update a genuinely clean slate rather than partially rebuilding on top of pre-DLC shader data [4]. If you’re on an NVIDIA card, raise Shader Cache Size to 10GB or Unlimited under NVIDIA Control Panel > Manage 3D Settings before you start – the default size is tight enough that STALKER 2’s shader count can force repeated recompiles even after the initial one-time hit [4]. Cap your frame rate to 60 fps while you diagnose stutter, and change one setting at a time rather than several at once – that’s the only way to tell whether a specific spike is shader-related or a genuine settings problem [4].

Frequently Asked Questions

Should I set Foliage all the way to Low in Iron Forest for maximum FPS?

No. Medium already recovers most of the available frame-time headroom, and dropping further to Low strips enough visual density that ambush points and anomaly clusters get genuinely harder to spot in a zone built around dense cover – you’d be trading a small remaining fps gain for a real tactical disadvantage. Only drop to Low if you’re still under 40 fps at Medium and need every frame you can get.

Does Cost of Hope raise STALKER 2’s official system requirements?

Not officially – the published recommended spec is still a GeForce RTX 4070 with 32GB of RAM [8]. What’s changed is that the CNPP’s lighting cost and Iron Forest’s foliage density now ask that same hardware to work harder to hold the frame rate it managed in the base game’s zones, which is exactly why the zone-specific settings above matter more with this DLC installed than they did before it.

My average FPS counter looks fine in the CNPP, so why does it still feel stuttery?

Because an average hides frame-time spikes. The freeze you feel walking into a new room is a one-time shader compilation cost for that specific room, not a sustained rendering load – your FPS counter recovers immediately after, which is why the number looks normal on average. That needs the shader-cache fix above, not a lower graphics preset; lowering settings doesn’t touch a one-time compile stutter at all.

Verified against STALKER 2 Update 2.0 and the Cost of Hope DLC (released August 20, 2026, Unreal Engine 5.5.4). Settings and benchmark figures may shift with future patches – check your in-game version under Options > About before assuming these values still apply.

Sources

1. TheFPSReview. S.T.A.L.K.E.R. 2: Heart of Chornobyl Update 2.0 Performance – Unreal Engine 5.5.4
2. Gagadget. STALKER 2’s Cost of Hope DLC Is Out Now – Here’s What’s New
3. KeenGamer. STALKER 2: Cost of Hope DLC Review – A Strong Return to Chornobyl
4. PixelNitro. How to Fix Shader Compilation Stutter in STALKER 2 Patch 2.0 (Cost of Hope DLC Guide)
5. TheFrameCoach. Best S.T.A.L.K.E.R. 2 Settings for AMD RX 9070 XT (2026)
6. GamersAndGeek. Stalker 2 Optimization Guide
7. Heise Online. Stalker 2: Update 2.0 Brings New Engine and Revised Graphics
8. Notebookcheck. Stalker 2 PC System Requirements Revealed: 32GB RAM, 160GB Storage, and a GeForce RTX 4070 Recommended

Michael R.

I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.