Player-reported evidence: reproduce these steps on your platform and demo build. They are not publisher promises or universal results.
DIRECT ANSWER
There is no confirmed universal performance fix. First compare your PC with the official requirements, reboot and update graphics drivers, close overlays, test native resolution, then toggle VSync or a frame cap one at a time. Keep any result tied to the demo build and your exact hardware.
Evidence state
Player reportedConfirmed now
- Official minimum and recommended PC requirements are current.
- Steam lists Windows and DirectX 12.
- Performance symptoms are configuration- and hardware-dependent.
Launch check
- 1.0 shader compilation and frame pacing.
- Platform-specific crash signatures.
- Console performance modes and Steam Deck status.
FIELD DECISION / 01
Steps to follow
- Record the baselineNote demo version, OS, CPU, GPU, RAM, driver, resolution, display refresh, controller, and the exact scene where the issue appears.
- Start cleanRestart the game and system, finish pending OS or driver updates, and close capture, monitoring, and overlay tools for one test.
- Change one display variableTest native resolution first; then compare VSync on/off or one frame cap. Do not change resolution, quality, and synchronization together.
- Verify files and storageUse the platform’s file verification if startup or crashes repeat, and leave free space beyond the listed 4 GB.
- Report a reproducible caseInclude steps, scene, frequency, log/crash output, and whether a clean save reproduces it. Avoid presenting a single workaround as universal.
WHY THIS WORKS
Why this route is reliable
A one-variable test separates frame pacing, display synchronization, driver state, and corrupt files. The result becomes reproducible evidence instead of a list of random settings changes.
IF IT DOES NOT WORK
Failure states and fixes
| Symptom | Check | Next move |
|---|---|---|
| Horizontal tearing during camera movement. | Compare display refresh, VSync, and frame-cap states one at a time. | Keep the single synchronization mode that removes tearing without creating unacceptable input or pacing issues. |
| Stutter in new scenes | Repeat the same route after the first pass and monitor background overlays. | If the second pass improves, record that pattern; do not call it a permanent fix before 1.0 verification. |
| Crash or black screen at startup | Verify files, driver/OS state, overlays, and required DirectX-capable hardware. | Preserve the crash details and escalate with the exact build if clean startup still fails. |
LEDGER NOTE / 02
Core Web-style evidence discipline
A performance report needs a device, build, scene, symptom, reproduction rate, and before/after condition. “It stutters” is a useful query signal, not enough evidence for a universal fix.
LEDGER NOTE / 03
What this page will add at launch
The Sep 22 strike will separate confirmed regressions, common player reports, known workarounds, and fixed patch versions. Bugs and patches have private schemas but will not publish empty pages.