On this page
Unfamiliar word? Select a dotted-underlined term for its meaning.
Check before giving another order
- For an operational save, read the handover brief. For a saved lesson, read its Objectives panel instead. Confirm this is the saved situation you meant to open. Loading replaces the situation you were playing; it does not join the two games together.
- Check Game Time and the time controls. Do not assume loading leaves the game paused or running at normal speed. Open the Escape menu if you need to pause while reading.
- Check the selected radar and its power and datalinks. If a contact is missing, follow the picture checks before deciding that the aircraft has gone.
- Open ACTIVE OPS. Match each important flight by callsign and check its task, target and position. Use the group checks to include the other fighters.
- Check fuel for the return journey and the aircraft data before extending a flight. A saved fighter waiting to depart and one already in the air need different checks. Use the next section before issuing another launch.
A waiting launch and an airborne flight load differently
| What you saved | What to check after loading |
|---|---|
| QRA accepted, but the fighters had not appeared yet | In v0.8.16.0, a valid saved waiting request starts the aircraft departure process when loaded. Its old pre-launch speech and waiting countdown are skipped. Look for the actual fighter flight in ACTIVE OPS and on the map before ordering another launch. This does not mean the aircraft are instantly airborne: departure checks and takeoff still matter. |
| Fighters already existed in the saved situation | Check the restored flight’s actual task, target, position and radio channel. Do not start a fresh launch just because you did not hear its original launch call. Follow task changes or RTB if you now want it to do something else. |
| The expected waiting launch did not appear | A saved waiting request whose target or base cannot be restored may not continue. Read the latest ASMA messages, check the existing flights and use availability checks. A missing pending row alone does not prove there is no flight. |
For example, you save while QRA is still waiting, then load that save. The old countdown is not a timer you should keep waiting for. Find the restored aircraft and read their current task. Normal launch waiting and cancellation describes the ordinary sequence before a load.
Loading is not replaying a recording
Loading clears old speech and rebuilds the saved situation. Fighter pairs and sortie radio connections are rebuilt for the aircraft that were restored. Check every expected member in ACTIVE OPS before giving another group order. Loading does not promise to replay every sentence or continue a clip from the same word. A silent moment is not proof that an order failed. Check the selected channel, sortie communications and the flight’s current task. In a lesson, also read the current objective; loading is not a way to replay the last instruction.
Saved ASMA report text can return without its old SET choices. Check the flight’s current task before repeating an order. See restored reports and requesting new ATC choices.
If the loaded situation looks wrong
- Check the save name, profile and Game Time first. Then compare the relevant flight, radar or objective with the saved situation you expected.
- If loading reports a problem, or important aircraft or tasks are missing, keep the original save. Do not overwrite that only copy with a situation you are unsure about.
- Record the game version, save name, the action just before saving and what changed after loading. Include a screenshot or short video and keep the save for the bug report.
- If you need to continue, use another known-good save or start a fresh session. Use a different save name to keep the evidence separate. See saving, loading and recovery.
A load that fails partway through is not a guarantee that the previous situation is still intact. Check what is on screen before continuing.