STAR WARS Zero Company Troubleshooting

Symptoms in this group

• Mission won’t start
• Mission won’t appear
• Objective won’t update
• Enemy won’t spawn
• Enemy is unreachable
• Mission won’t end
• Required character is missing
• Timer is confusing

Check in this order

1. 1Name the exact objective that is still open
2. 2Name the target or interaction that objective expects
3. 3Confirm the required Operator is deployed rather than benched or injured
4. 4Confirm every earlier step in the walkthrough is closed

If all four hold and the objective still will not close, it is a state problem rather than a rules problem — record it as a report instead of replaying the mission a fifth time.

Check in this order

1. 1Previous Mission complete
2. 2Required conversation had
3. 3Required Operator on the roster
4. 4Campaign state reached
5. 5No mutually exclusive branch taken
6. 6Expiry window respected

A Mission that never appeared is almost always a prerequisite. A Mission that vanished after the Cycle turned over is usually expiry or a branch, both of which are the campaign working as designed.

Mission availability check

Name the Mission and this page prints its recorded prerequisite instead of guessing. It cannot read your save, so each row is yours to confirm — but you will be checking the condition the game actually uses.

The recorded graph describes 16 of 123 Missions. When a Mission has a prerequisite, the checker shows it; when it does not, the checker says so rather than inventing one.

Symptoms in this group

• Overwatch won’t fire
• A 100% shot missed
• Ability is unavailable
• Can’t target an enemy
• Can’t use a Utility
• Hit chance looks wrong

• ·Identify the exact action that did not resolve
• ·Check whether the action had a condition attached to it
• ·Reproduce it once, deliberately, on the current build

Combat problems split cleanly: either the mechanic was misread, or the action should have resolved and did not. Only the second one is a bug report.

• Didn’t fire
• Triggered unexpectedly
• Enemy fired through cover
• Wrong cone or wrong target

First check

1. 1Confirm the enemy crossed the active cone rather than stopping inside it
2. 2Confirm line of sight existed at the moment of the move
3. 3Confirm the shot was not resolved by the normal cover rules
4. 4Note the build — Overwatch behaviour changed across patches

Overwatch uses the currently supported ranged calculation path for these values. This calculator does not model whether Overwatch triggers.

Patch status: Patch 1.1 shipped fixes for several Overwatch behaviours, and reports continued afterwards. The behaviour stays player-reported until the trigger itself can be reproduced, which is why the checks above come before any bug claim.

Symptoms in this group

• Specialization still locked
• Secondary Specialization locked
• Talent locked
• Cross Training unavailable
• Operator not recruitable
• Den upgrade locked
• Utility or Mod slot locked
• Black Market locked

• ·Read the recorded requirement rather than guessing it
• ·Check the prerequisite upgrade or Mission the requirement points at
• ·Check the Den state or roster the requirement refers to

A greyed-out entry is a statement about your campaign, not a fault. An entry that accepts the click and does nothing is a different problem.

Do this in order

1. 1Identify the platform
2. 2Record the exact symptom, in order, before doing anything
3. 3Preserve the current save state — do not move or delete files
4. 4Check the game build
5. 5Follow the official recovery path

High-risk file surgery is never the first step. Identify, record, preserve, check the build, then use the official route.

Patch 1.1 save fixes

• ✓Beskar save temporarily removedA temporary save removal specific to Beskar mode. Fixed in Patch 1.1.
• ✓Save corruption after a forced shutdownA corruption case tied to forcing the game closed. Fixed in Patch 1.1.
• ✓Some preorder and Deluxe content not deliveredPart of the preorder and Deluxe entitlement delivery was corrected in Patch 1.1.
• ✓Several crash causesPatch 1.1 shipped a batch of stability fixes across reported crash points.

Still happening on Patch 1.1? Then it is a current-build problem and worth a report, not a historical footnote.

When does it happen?

The crash point is a better clue than the platform. Pick the closest one and note it before changing anything.

• Before the main menu

  Often driver or platform-service related, and usually repeatable.

• Loading a save

  Points at the save rather than the renderer — preserve it.

• Starting a Mission

  Often a specific Mission or deployment state.

• During combat

  Note the exact action that preceded it.

• Enemy turn

  Frequently described as a freeze, sometimes with a reaction shot queued.

• After a Mission

  Often on the transition or results screen.

• Returning to the Den

  Transitions and loads rather than combat.

Official first steps

Low risk, in this order, before any community workaround.

1. 1Restart the game and the platformThe cheapest step, and it resolves more of these than any setting change.
2. 2Update the gameCheck the build first. A launch-version bug is not worth debugging.
3. 3Check platform and EA servicesAn outage can look like a local fault.
4. 4Repair or verify the game filesWhere the platform supports it.
5. 5Clear the cacheA supported platform step rather than a file-level experiment.
6. 6Update the GPU driverPC only, and worth doing before any advanced workaround.

Report it with evidence attached

Note the platform, the crash point, any error message, the driver version and the game build before you change a single setting — otherwise you will not know which change mattered.

A performance issue is not a crash issue

The official FAQ describes the game as CPU-bound, so lowering GPU-heavy settings does not necessarily give the same gain it gives in other games.

1. 1Separate frame rate from stability — a stutter is not a crash
2. 2Check the upscaling setting before dropping image quality
3. 3Change one setting at a time and note the result

Symptoms in this group

• Keyboard stopped responding
• Can’t close a menu
• Controller input is broken
• Interface element is missing
• Can’t select a weapon

1. 1Check whether the control is disabled or unresponsive — the two have different causes
2. 2Check whether the game is waiting on a prompt you dismissed
3. 3Record the point of the soft-lock and the exact input that failed

Menu and input soft-locks have been reported since launch. A disabled button is usually a requirement; a button that clicks and does nothing is not.

Official / patch-confirmed

• FIXEDA 100% hit chance could miss
• FIXEDBeskar save temporarily removed
• FIXEDSave corruption after a forced shutdown
• FIXEDSome preorder and Deluxe content not delivered
• FIXEDSeveral crash causes

Player Reports

Not an official known-issues list. Multiple player reports without an official acknowledgement. These stay player-reported, however many people repeat them.

• Freezes during combat and on enemy turns

  PLAYER-REPORTED

  Reported on PC and consoles both before and after the current patch.

• Overwatch triggers that look wrong

  PLAYER-REPORTED

  Reports continue after the patch, but the condition that should have triggered is rarely recorded with them.

• Mission soft-locks, including unreachable enemies

  PLAYER-REPORTED

  A final enemy behind a spawn door that cannot be reached leaves an eliminate-all objective open. This is a mission-state soft-lock, not a mechanic misunderstanding.

• Crashes after a Mission completes

  PLAYER-REPORTED

  Reported around the results and transition steps.

• Menu and input soft-locks

  PLAYER-REPORTED

  Reported around menus and weapon selection since launch.

A report becomes confirmed only through Official patch notes, an official known-issues list, or a behaviour that can be verified in the current build.

Launch-version issues

• A 100% hit chance could miss

  FIXED

  On the current build a displayed 100% hit chance is expected to hit. If it still misses, it is a new report.

• Beskar save temporarily removed

  FIXED

  Keep the save where it is and check the build before you attempt any recovery step.

• Save corruption after a forced shutdown

  FIXED

  Quit from the menu where possible. If a save still looks wrong, preserve it before anything else.

• Some preorder and Deluxe content not delivered

  FIXED

  Confirm the build and the account. Remaining entitlement gaps go through official support rather than a workaround.

• Several crash causes

  FIXED

  Stability reports continued after the patch, so identify the crash point rather than treating “crash” as one problem.

These records stay published because the searches that find them still exist. The page does not pretend a fixed launch bug is currently broken.

Checklist

• ✓Platform
• ✓Game version
• ✓Mission or objective
• ✓Operator
• ✓Exact action you took
• ✓Expected behaviour
• ✓Actual behaviour
• ✓Whether it is reproducible
• ✓Screenshot or video
• ✓Any error code shown

Report builder

Fill in what you know, then copy the report. Empty fields stay visible as Not recorded so you can see what is still missing before you send it.

Platform: Not recorded
Game version: 1.1
Mission / objective: Not recorded
Operator: Not recorded

Expected: Not recorded

Actual: Not recorded

Action taken: Not recorded
Reproducible: Not recorded
Screenshot / video: Not recorded
Error code: Not recorded

Where each answer comes from

• Game mechanics and requirementsThe shipped game data this site already resolves
• Patch status and fixed issuesOfficial patch notes
• Technical fixesOfficial support guidance
• Current player reportsCommunity reports, labelled as unconfirmed
• Derived diagnosticsThis site, built from the four layers above

Keeping the layers apart is what stops a Reddit thread from answering a Mission prerequisite question, and what stops reversed game data from being used to explain a GPU crash.