Loading...
Known Issues and Bugs
September 12, 2026 at 10:53 PM
Reworked the page into fixed and outstanding issues after Update 1.1, and removed the claim that no patch or patch notes existed
STAR WARS Zero Company shipped on August 27, 2026 to broadly positive reception, and for the first two weeks the most common shape of a critical player report was some version of "good game, wait for a patch". That patch arrived on September 9, 2026 as Update 1.1, and it closed a large share of the list below. This page is split to match: what Update 1.1 fixed, what players still report, the hardware-side problems a patch cannot touch, and the design complaints that are not defects at all.
Outside the first table, everything here is community reporting rather than confirmed defect tracking. No standing known-issues list is published for the game, and the guidance issued at launch routes both bug reports and technical support to the publisher's community forums. See Patch History for the update timeline and the complete contents of Update 1.1.
Update 1.1 is the first update for this game with published notes, and it names most of the serious stability problems reported since release. The table below covers only the entries that answer something this page was tracking; the patch itself is considerably longer.
Issue | What Update 1.1 Changed |
|---|---|
Chance to hit recalculating | Fixed. A shot displayed at a 100 percent chance to hit no longer misses. This was the most-cited mechanical complaint of the first two weeks. |
Crash to desktop | Various crashes fixed. The notes do not itemise which ones, so a player who is still crashing should read the entry as partial rather than as a guarantee. |
Visual stutter | Various visual stutters fixed. |
Save corruption | Fixed for the specific case of a sudden or forced shutdown. |
Save loss in Beskar Mode | Fixed twice over: a fault that temporarily deleted Beskar saves was closed, and so was a crash specific to the mode. The single-save design itself is unchanged, so a wipe still ends a run. See Difficulty Settings. |
Character corruption in the Databank | Three separate faults fixed in the Den facility where Operators are created and edited: corruption while the game was saving, corruption while a character was being edited, and renaming one Operator also renaming another. |
Missing pre-order and Deluxe items | Fixed. Players who had not received the items tied to their edition should now have them. See Release Date and Editions. |
Softlocks | A rare main-menu softlock from input spamming, a rare Medbay tutorial softlock, and a squad selection transition that blocked progression were all fixed, along with combat actions that were not being processed. |
Camera drift and wobble | Fixed for two specific cases: drift while an ability was being targeted, and wobble on entering the over-the-shoulder view. |
Graphics settings mislabelled | The Global Illumination and Reflections settings no longer incorrectly reference ray tracing. |
The entries below were either not named in Update 1.1 or are only partly covered by it. Treat them as live on the current build.
Reported Issue | Description |
|---|---|
Relaunch blocked after a crash | A follow-on pattern that comes up repeatedly: the game will not relaunch after a crash until the shader cache directory is deleted by hand. Not named in Update 1.1. |
Turn hang | 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, and separately report multi-minute pauses between turns at random. Update 1.1 fixed several specific softlocks and a class of unprocessed combat actions, which may cover part of this. |
Mission-specific crashes | Crashes are often described as recurring in the same mission rather than striking at random. Because the crash fixes in Update 1.1 are unitemised, whether a particular mission is covered has to be tested rather than assumed. |
The Beskar Mode interaction is still worth understanding before starting that mode, even with the two faults fixed. 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. Update 1.1 fixed various visual stutters and added a settings suggestion for older cards, but did not claim a general performance uplift. |
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. This is architecture rather than a defect. |
Vertical sync resets | Reported as silently disabling itself on each launch while the options menu continues to show it as enabled. Not named in Update 1.1. |
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.
Update 1.1 added one tuning suggestion aimed squarely at the low end. On older graphics cards, specifically the GTX 10 and RTX 20 series, setting Environment Geometry Detail to Off reduces geometry overhead and can steady the framerate.
Reported Issue | Description |
|---|---|
Camera handling | Described as clunky, and clicking before the camera has settled can register the wrong input. Update 1.1 fixed drift during ability targeting and wobble entering the over-the-shoulder view, but the broader complaint remains. |
Menu and interface friction | A recurring but lower-severity complaint, generally about navigation rather than about anything failing outright. Update 1.1 corrected several individual readouts, including the Focus amount appearing only in the radial menu and damage reduced to zero being misrepresented. |
Visual glitching | Reported intermittently, without a consistent trigger. |
Two of the four problems the team acknowledged before Update 1.1 sit outside the game, so a patch cannot close them and the workarounds still apply.
Problem | Workaround |
|---|---|
Crashes with older graphics drivers | Crashes while using upscaling on an older graphics driver release. Updating to the current driver is the suggested fix. Update 1.1 raised the minimum suggested driver versions and updated the in-game prompt that reports them. |
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. |
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, and Update 1.1 did not.
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 were the single most likely reason a player wrote a negative review while still recommending the game to others once fixed.
That makes the date on a report the thing to check first. Update 1.1 answered most of the stability list directly, so a review or a thread written before September 9, 2026 is describing a build that no longer exists. The design entries are the ones least likely to move.