Loading...
Loading...
Known Issues and Bugs
September 9, 2026 at 09:42 AM
Added the four issues acknowledged by the team and the announced first update
STAR WARS Zero Company shipped on August 27, 2026 to broadly positive reception, and the most common shape of a critical player report is some version of "good game, wait for a patch". This page collects the problems players have reported since release. Four problems have been acknowledged by the team and are listed first. Everything after that is community reporting rather than confirmed defect tracking: no formal known-issues list and no patch notes have been published, and as of September 9, 2026 no post-launch update has shipped.
Thirteen days after launch no fix has shipped. The store announcement feed has not carried a post since launch day, and it reports itself complete in both directions, so the silence on the formal channels is a real absence rather than a gap in what can be read; the acknowledgements above came through community channels instead. The guidance published at launch routes both bug reports and technical support to the publisher’s community forums for the game.
In early September the team publicly acknowledged four problems for the first time, alongside saying that a first post-launch update addressing bugs and performance was being prepared. These are the only issues with any official recognition; everything further down this page is community reporting.
Issue | What Was Said |
|---|---|
Chance to hit recalculating | A shot displayed at a 100 percent chance to hit is incorrectly recalculated to a lower chance when it is taken. The team said it is looking into a fix. |
Crashes and CPU threading | Acknowledged as being worked on, without further detail. |
Crashes with older graphics drivers | Crashes while using upscaling on an older graphics driver release. Updating to the current driver is suggested. |
Desktop processor instability | Some 13th and 14th generation Intel Core desktop processors can be unstable in a way that causes crashes. Updating the system BIOS is suggested, or lowering the performance core ratio from 55x to 54x, 53x or 52x with the manufacturer tuning utility. |
The last two are hardware-side workarounds that can be applied now rather than waiting for a patch. See Patch History for the update timeline.
Reported Issue | Description |
|---|---|
Crash to desktop | The most frequently reported serious problem. Crashes are often described as recurring in the same mission rather than striking at random. One follow-on pattern comes up repeatedly: the game will not relaunch after a crash until the shader cache directory is deleted by hand. |
Turn hang and softlock | Combat stops advancing to the next turn after certain actions. Players describe waiting several minutes to a quarter of an hour before giving up and restarting the mission. Separately, multi-minute pauses between turns are reported at random. |
Save loss in Beskar Mode | The most damaging reported issue. Beskar Mode uses a single save file, so a crash at the end of a mission can destroy a run with no recovery path. Losses of twenty to forty hours have been reported, including on Expert difficulty. This is the direct cause of several otherwise favourable negative reviews. |
Save corruption | Reported far less often than crashes, but almost always inside a negative review when it does appear, because the outcome is lost progress. |
The Beskar Mode interaction is worth understanding before starting that mode. See Permadeath for what the setting does and how it combines with losing Operators.
Reported Issue | Description |
|---|---|
Choppy framerate | Reported even at the lowest settings, and sometimes on hardware at or above the recommended tier. Several players report the console versions running better than their PC. |
Limited benefit from lowering settings | Consistent with the studio’s own pre-launch explanation that the game is more CPU bound than GPU bound, so individual graphics options move the framerate less than they would in most other genres. |
Vertical sync resets | Reported as silently disabling itself on each launch while the options menu continues to show it as enabled. |
The recommended specification is worth reading with its caveat attached. The 1440p at 60 frames per second target is measured with the default upscaler on, not at native resolution, which is documented in System Requirements. That caveat plus the CPU-bound behaviour together explain why fitting a faster graphics card often does not move the framerate as much as players expect.
Reported Issue | Description |
|---|---|
Camera handling | Described as clunky. Clicking before the camera has settled can register the wrong input. |
Menu and interface friction | A recurring but lower-severity complaint, generally about navigation rather than about anything failing outright. |
Visual glitching | Reported intermittently, without a consistent trigger. |
A separate set of criticisms describes the game working as designed and players wanting something different. They are listed apart because a patch would not address them.
Complaint | Detail |
|---|---|
Depth of the base layer | The management side of The Den is described as thin next to the tactical layer, with fewer meaningful decisions than the genre usually offers. |
Squad size | The four-Operator deploy limit is a common complaint from players who wanted larger engagements. See Squad Customization for how the limit works. |
Battlefield scale | Maps are described as small, which interacts with the squad limit to keep encounters tight. |
Difficulty design | Higher difficulties are criticised for leaning on enemy reinforcement waves rather than on smarter opposition. |
Build variety | Some players report that Specializations and equipment offer fewer distinct viable builds than expected. |
Replay incentive | With no New Game Plus and a campaign most players finish inside forty hours, there is limited structural reason to start again. |
Read against the overall reception, these are the complaints of a minority inside a largely satisfied player base. Roughly four in five reviews are positive, and among the critical ones the technical issues appear far more often than the design ones. Crashes in particular are the single most likely reason a player writes a negative review while still recommending the game to others once fixed.
The absence of a patch is the live variable. If an update lands, the stability entries above are the ones most likely to change; the design entries are unlikely to.
