The settings table explains the separate controls, and GPU options covers changes that require a new launch.
Find the correct settings layer
The launcher groups options under Home, Graphics, Performance, Game and Advanced. Save pending changes before PLAY. During gameplay, Insert or R3 + L2 opens the port menu; its Image and Performance tabs expose related controls. The game’s own pause and photo menus are separate.
Render resolution, engine frame rate and GPU readback changes in the running-game menu use Apply and restart. Stream buffer memory and Game multisampling take effect on the next launch. Anisotropic filtering, added in 2.3.0, is also applied at game startup. Saving a value is not proof that a running session already uses it.
Sources: Project README · Download and play · Project README · What works · Project README · Settings · 2.3.0 release · 15 October 2026 UTC
Separate resolution, timing and presentation
If you are isolating a problem, native 1080p and a 60 engine rate provide a clear comparison state rather than a promise of optimal performance. Record the previous values, change one setting, restart where required and replay the same scene. For high-rate path or QTE failures, use the specific 60-engine workaround.
What each graphics/performance choice changes
On a narrow screen, scroll the table horizontally to read every column.
| Control | Job | What to watch |
|---|---|---|
| Render resolution | Native 1080p or an offered resolution patch | A resolution patch replaces the separate texture-fix patch; restart after changing |
| Engine frame rate | 60, 120 or 240 timing path; 120 is the documented default | High rates have known progression/QTE blockers |
| Frame-rate limit | Presentation limit, from 30 to unlimited | A 60 presentation cap is not the same change as a 60 engine patch |
| VSync | Presentation synchronization | Keep its state fixed when comparing frame pacing |
| Frames queued | How many frames wait in the queue | Record the choice when describing input delay |
| Anisotropic filtering | Game default, 2x, 4x, 8x or 16x | Sharper oblique surfaces; applies on the next launch |
Sources: Project README · What works · 2.3.0 release · 15 October 2026 UTC · 2.4.0 release · 16 October 2026 UTC
Use the GPU controls for their documented symptom
Performance → GPU data → Stream buffer memory offers System RAM (cached), System RAM (uncached) and GPU memory. Cached System RAM is documented as the default and can improve performance on NVIDIA laptops. Choose GPU memory to restore the previous allocation behavior if your comparison goes the other way; restart and keep the same scene.
Game multisampling → Automatic disables the problematic multisampled-image path on AMD and Intel Windows drivers while retaining it on NVIDIA. Check the selected card and GPU: guest multisampling off or on in the log. If black lighting lines occur on another card, Off is the documented comparison; restore the previous choice if it does not help.
Deferred GPU readbacks should not stay disabled merely because an older texture tutorial told you to do so. 2.3.0 fixes one stale-texture cause and explicitly says to re-enable readbacks after that older workaround. Some long-session corruption remains listed in 2.4.0; use the symptom-specific graphics guide.
Fast screen effects, on by default from 2.4.0, addresses large drops during powers. If the power’s effect is stretched, shifted or wrong, the release says to turn that option off and report the result. Intel gameplay validation was not recorded for this fix.
Sources: Project README · Settings · 2.3.0 release · 15 October 2026 UTC · 2.4.0 release · 16 October 2026 UTC
Do not turn source features into enabled settings
RCAS sharpening is an available image control. The README’s dated feature matrix lists FSR 1, FSR 3.1, FSR 4, TAA and DLSS as disabled in the launcher/game settings path for its 2.2.0 comparison and source snapshot. The checked 2.4.0 and 2.4.1 release notes do not announce enabling them.
The 2.4.1 launcher implementation also forces the experimental-upscaler switch off when starting the game and leaves its temporal-upscaler UI section disabled. An old saved on-switch from 2.1.8 is ignored there. This is a source check of the release path, not a current side-by-side upscaler test.
A dependency name or development document is insufficient to promise an enabled DLSS/FSR option in your package. Use options actually exposed by the chosen release and keep overlay/ReShade integration separate from the port’s own image controls.
Sources: Project README · Feature availability · 2.4.0 release · 16 October 2026 UTC · 2.4.1 source · Launcher settings and save restore
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 · Download and playMaintainer instructions at the 2.4.1 release commit.
- Project README · What worksMaintainer feature descriptions, not this site’s gameplay tests.
- 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.
- 2.4.0 release · 16 October 2026 UTCBuilt-in aspect ratios, fast screen effects, validation hardware and unresolved issues.
- Project README · Feature availabilityThe embedded comparison is dated 14 October and labels 2.2.0; later packages require their own release notes.
- 2.4.1 source · Launcher settings and save restoreSave backups/Restore controls, preferences and package settings at the release commit.