Start with the symptom table, then use the reversible comparison sequence to record a useful result.
Which slowdown are you seeing?
The release still notes that first use of a power in a new area can briefly stutter even with Fast screen effects. Do not interpret one smooth pass as a universal fix, or one first-use pause as proof that the GPU cannot sustain the rest of the scene.
Timing is more useful than an FPS average alone
On a narrow screen, scroll the table horizontally to read every column.
| Observed symptom | Relevant distinction | Next check |
|---|---|---|
| Brief stutters entering a new area or using a new effect | Saved pipelines may be compiling/loading | Check the Loading shader cache indicator and compare a repeat visit |
| Low FPS throughout a repeatable scene | Not explained merely by a transient first-use pause | Record hardware, driver, resolution and engine/presentation settings |
| Large slowdown while Rage or certain weapons are active | 2.4.0 fixes a texture-cache reuse problem in this effect path | Check release tag and Fast screen effects |
| Delay changes when the performance overlay is visible | 2.4.0 lists overlay input lag as unresolved | Compare the same scene with that overlay disabled |
Sources: Project README · What works · 2.4.0 release · 16 October 2026 UTC
Compare reversible changes under the same conditions
Record a baseline
Note the runtime tag, OS, CPU, GPU, driver, game title/build, scene, resolution, engine rate, presentation cap and cache state. Keep the original values so you can restore them.
Check background shader work
Watch whether stutters subside as shader work progresses. Compare first and repeat visits separately. Do not repeatedly delete the cache: a rebuilt cache changes the next test’s conditions.
Check an inherited readback workaround
If Deferred GPU readbacks was disabled for the old yellow/white-texture issue, restore it for comparison on 2.3.0 or later and restart. Revert if your own symptom worsens; the release’s heavy-scene claim is not a measured gain for your PC.
Test the matching effect option
For the powers slowdown on 2.4.0+, keep Fast screen effects enabled unless the effect itself becomes distorted. Turn it off for the same scene if it looks wrong, then report the visual/performance trade-off.
Change one load-related option
Compare a lower offered render resolution or the documented Stream buffer memory choices one at a time, restarting when required. Restore the prior value if there is no useful improvement.
Sources: Project README · Settings · 2.3.0 release · 15 October 2026 UTC · 2.4.0 release · 16 October 2026 UTC · Project README · What works
When to treat it as a bug report
2.4.0’s effect fix was checked by hmathsan on an RTX 5070 and FelipePrado0 on an RX 6700 XT under Windows 11. The project did not report Intel gameplay validation for that change. Its separate historical 144-FPS average on an RX 6700 XT/5600X/32-GB system does not predict a specific laptop’s result.
A reproducible scene or effect that remains slow after the matching release fix deserves a report with the before/after conditions and last_run.log. If the game is actually stuck at an area transition, follow loading-hang diagnostics instead of treating a moving FPS counter as proof that loading is healthy.
The shader cache can reportedly grow beyond 20 GB. Keep sufficient free storage and preserve useful logs before changing data. A cache deletion is not a standing performance recommendation. The settings guide explains the memory and presentation controls without promising a single best preset.
Sources: 2.4.0 release · 16 October 2026 UTC · Project README · Performance and compatibility
Sources and method
Prepared by GOW III · PC Field Guide from the linked maintainer documentation, release records and attributed original reports, with AI assistance in research, writing and implementation. We have not played or independently benchmarked the game. Source checks describe the records read, not our own gameplay results.
- Project README · What worksMaintainer feature descriptions, not this site’s gameplay tests.
- 2.4.0 release · 16 October 2026 UTCBuilt-in aspect ratios, fast screen effects, validation hardware and unresolved issues.
- Project README · SettingsSettings, memory allocation and multisampling behavior.
- 2.3.0 release · 15 October 2026 UTCHistorical texture/RADV/hybrid-GPU fixes, screenshot and vibration validation, and known issues.
- Project README · Performance and compatibilityHistorical maintainer reference system; exact test release is not specified.