Loading...
Known Issues and Bugs - Version 5 vs Version 6
Oct 10, 2026, 07:14 PM
Removed duplicate in-body wikilinks
Oct 15, 2026, 01:44 PM
Re-verified and re-dated the known-issues status and noted that Patch 1.2 had not shipped as of October 15, 2026
11STAR 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.2233Outside the first table, everything here is community reporting rather than confirmed defect tracking. Beyond one pinned notice of acknowledged problems, 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.4455Fixed in Update 1.16677Update 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.8899IssueWhat Update 1.1 ChangedChance to hit recalculatingFixed. 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 desktopVarious 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 stutterVarious visual stutters fixed.Save corruptionFixed for the specific case of a sudden or forced shutdown.Save loss in Beskar ModeFixed 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 DatabankThree 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 itemsFixed. Players who had not received the items tied to their edition should now have them. See Release Date and Editions.SoftlocksA 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 wobbleFixed for two specific cases: drift while an ability was being targeted, and wobble on entering the over-the-shoulder view.Graphics settings mislabelledThe Global Illumination and Reflections settings no longer incorrectly reference ray tracing.1010Fixed Since Update 1.111111212One further fix has shipped. A PC hotfix on September 28, 2026 fixed a crash issue for various hardware setups. That line is the whole published note, so it does not say which hardware or which crashes, and it names PC only. The crash entries below stay listed until players stop reporting them.131314-The team's pinned issue notice on the game's store discussion forum still carries the same launch-period problems, and as of October 10, 2026 no newer known-issues post has been published. Patch 1.2 was announced on October 9, 2026 for the following week with no contents given. See Patch History for both.14+The team's pinned issue notice on the game's store discussion forum still carries the same launch-period problems, and as of October 15, 2026 no newer known-issues post has been published. Patch 1.2 was announced on October 9, 2026 for the following week with no contents given; as of October 15, 2026 it had not shipped. See Patch History for both.15151616Still Reported17171818The entries below were either not named in Update 1.1 or the September 28 hotfix, or are only partly covered by them. Treat them as live on the current build.19192020Stability21212222Reported IssueDescriptionRelaunch blocked after a crashA 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 hangCombat 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 crashesCrashes 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.2323The 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.24242525Performance26262727Reported IssueDescriptionChoppy framerateReported 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 settingsConsistent 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 resetsReported as silently disabling itself on each launch while the options menu continues to show it as enabled. Not named in Update 1.1.2828The 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.29293030Update 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.31313232Interface and Presentation33333434Reported IssueDescriptionCamera handlingDescribed 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 frictionA 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 glitchingReported intermittently, without a consistent trigger.3535Hardware-Side Workarounds36363737Two 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.38383939ProblemWorkaroundCrashes with older graphics driversCrashes 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 instabilitySome 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.4040Design Complaints That Are Not Defects41414242A 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.43434444ComplaintDetailDepth of the base layerThe management side of The Den is described as thin next to the tactical layer, with fewer meaningful decisions than the genre usually offers.Squad sizeThe four-Operator deploy limit is a common complaint from players who wanted larger engagements. See Squad Customization for how the limit works.Battlefield scaleMaps are described as small, which interacts with the squad limit to keep encounters tight.Difficulty designHigher difficulties are criticised for leaning on enemy reinforcement waves rather than on smarter opposition.Build varietySome players report that Specializations and equipment offer fewer distinct viable builds than expected.Replay incentiveWith no New Game Plus and a campaign most players finish inside forty hours, there is limited structural reason to start again.4545How Common Are These46464747Read 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.48484949That 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.