GUIDE / TECHNICAL
Launch troubleshooting
A methodical troubleshooting order for day-one problems — without pretending to know the actual failure modes yet.
A methodical order to work through day-one problems — with the honest caveat that known failure modes do not exist until the build ships and the wiki publishes them with version scopes.
The method, in order
Editorial guidance1 Reproduce — note exactly what fails, when and with what settings. 2 Update the obvious — drivers, OS, firmware, store client. 3 Verify files — Steam integrity check or the console's equivalent; corruption is the cheapest fix. 4 Isolate hardware — reseat nothing over the network, but test a second display/HDMI path if video is the symptom. 5 Report with receipts — version, hardware, steps and what you already tried, via the corrections flow.
Known issues list
UnverifiedThe wiki publishes reported issues in the updates page only after verification: each entry carries the game version, platform, the report method and its status (confirmed / reproduced / fixed). Pre-launch, the list is empty by design — no invented day-one bug list will appear here first. Check ps5/pc pages after launch morning for the first verified entries.
When to blame the game
Editorial guidanceA common launch-day failure is misattribution. The same symptom (crash at a cutscene) can be driver, file corruption or game bug; only after steps 2–4 fail in order should the game bear the blame — and then the wiki wants your report, not your anger.