Pre-release reference — content last verified August 28, 2026
Launch troubleshooting reference
Separate EA's documented troubleshooting steps from launch reports about PC crashes, Xbox crashes, black screens, low FPS, and stuttering.
These actions come from EA's troubleshooting material. They are confirmed recommendations for diagnosis, while the result can still depend on the platform, hardware, driver, and game build.
Install any pending Zero Company update and platform update, then check for a current graphics driver. EA lists pending updates, outdated drivers, and unmet requirements among common causes of launch problems and poor performance.
Use the platform's verify or repair flow when the game will not start, crashes during loading, or shows signs of missing or corrupted files. A successful file check does not prove that low FPS or stuttering has been solved.
EA recommends closing background applications and lowering graphics settings when they are competing for resources or the system is struggling to maintain performance. Retest the same scene after each change so the result stays useful.
Compare the PC with the official requirements. Intel Arc users should also check Resizable BAR when troubleshooting FPS. The requirements target is a baseline, not a promise that every system will have the same frame rate.
The symptom pattern is real enough to document, while the reports do not establish one universal cause or solution.
Players report crashes in the tutorial, character creation, enemy turns, holotable scenes, and when loading saves. Some reports come from high-end systems, so meeting the recommended requirements alone does not rule out a launch issue.
A launch Reddit thread includes reports of the game shutting down the console during missions or cutscenes and returning to the dashboard. Windows Central also reports hard crashes during an Xbox review playthrough after the day-one patch.
EA connects black-screen or launch problems with pending updates, graphics drivers, corrupted files, and system requirements. SteamOS players also report a black screen after the splash screen, with Proton changes helping some users only.
Launch reports describe low FPS, frame drops, micro-stutters, texture loading problems, and slow movement even on low settings. The exact bottleneck varies across hardware and scenes, so keep the test context with the result.
These ideas have been reported by players or published in the EA forum. They can be useful experiments, with no guarantee that they solve every crash or performance problem.
The EA forum optimization post recommends turning Environment Geometry Detail off for GTX 10-series and RTX 20-series users who meet the minimum requirements. Reddit users also report sizable FPS gains after changing it, though other players report no crash improvement.
Some AMD players say disabling Frame Generation and Anti-Lag stopped tutorial crashes. This is a player report without a controlled comparison, so keep the graphics-driver version and GPU attached to any retest.
Some SteamOS players report that Proton 9.0.4 or Proton 10.0.4 allowed the game to pass the splash screen. Other players report different results, and this page does not promote one Proton version as a stable fix.
Players suggest testing fullscreen or borderless mode, VSync, and a capped or unlimited frame rate when the problem is tearing or uneven frame pacing. These settings have mixed reports and should be tested one at a time.
Use these only as reversible experiments after the official checks. A report that helped one player does not establish a platform-wide fix.
One player reports that running Steam as administrator allowed a saved game to load after repeated crashes. The report does not show why it worked or whether it remains necessary, so treat it as a temporary experiment.
Xbox players mention testing Performance and Quality modes, but the launch crash discussion includes failures under both conditions. No mode has been verified as a fix for shutdowns or dashboard returns.
Cache clearing appears in platform troubleshooting discussions and can help with stale temporary data. It should be reported as a startup experiment, with no claim that it fixes the game's underlying low-FPS or stutter behavior.
Keep the troubleshooting record reproducible so a later patch can be compared with the launch snapshot.
Write down PC, Xbox Series X|S, or SteamOS, plus whether the failure is a crash, black screen, low FPS, stutter, save-load failure, or update problem.
Update Zero Company, the platform, and PC graphics drivers where applicable. Restart before changing several settings at once.
Run the platform's file verification or repair flow when the game fails during startup, loading, or save access.
Close background apps, lower settings, or test the hardware-specific community suggestion. Record the result from the same scene or mission section.
Keep the game build, operating system, driver, GPU or console model, graphics settings, and location of the failure with the report.
Continue reading
