Environments & rehearsal · Running
Running an exercise
Attach an environment, load a scenario, release the adversary. Three steps, in that order.
Start it
Settings → Scenarios, pick one, press Start.
Two things happen in order. The environment attaches, which resets the runtime. Then the scenario loads and brings its own map and anchor.
The order matters and the product handles it, so there is nothing to sequence by hand. What is worth knowing is that attaching an environment discards anything staged. Starting a scenario is not a way to add to a running picture; it replaces it.
The run bar
Once a scenario is loaded the console carries a run bar: the scenario name, the environment, the elapsed sim time, and pause and stop.
| Control | Does |
|---|---|
| Pause | Freezes sim time. The picture holds; nothing decays. |
| Stop | Ends the run and finalises its record. The environment stays attached. |
| Release | Lets the adversary begin, if the scenario is holding it. |
Stop does not detach the environment, so the next scenario starts faster. Changing environment is the heavier act, and it lives in Settings.
Loaded is not running
A scenario can be loaded with its adversary held. The picture is live, your own aircraft are flying, and nothing hostile has appeared yet.
That state is deliberate and it is where a briefing happens. The run bar shows it, so you can tell the difference between nothing is coming and nothing has been released.
Sim time and wall time are different
Time scale above 1 runs the exercise faster than real time. Beyond that, the tick loop catches up when the host is busy, so sim time and wall time drift apart on their own.
This matters in one practical way: do not use a stopwatch to decide when something should have happened. Read the sim clock.
What you can do while it runs
Everything the console does with a live picture. Change posture, approve or reject plans, task an asset, open a feed, ask the Copilot for an assessment.
Doctrine changes take effect immediately, which is the point of being able to make them mid-exercise. Tightening posture during a raid and watching the gates change is a legitimate thing to rehearse.
Stopping
Press Stop. The run is finalised with its outcome, and it appears under Runs & replay.
A run superseded by starting another one is recorded as aborted rather than lost.
Where to go next
- Runs & replay for comparing two runs.
- Configuring a simulation to change what you just ran.