Add the brief, scored tasks, and training faults only after the converted spacecraft passes the first connection test.
Writing the brief
Open Brief in the Space Range window. Tell participants:
- the mission context
- their objectives
- constraints
- evidence to collect
- completion conditions
Keep passwords, correct answers, event times, and facilitator recovery steps in a private run sheet.
Writing questions
Open Questions and choose the type that matches the answer:
| Type | Use |
|---|---|
| Text | One short, unambiguous answer |
| Number | A measured or calculated value with tolerance and unit |
| Select | One correct option |
| Checkbox | Multiple correct options with possible partial credit |
Every question needs a section, prompt, expected answer, non-zero score, and useful reason.
Make the answer observable from the converted Studio mission. Check the final component names, units, telemetry, and visible objects before writing the question.
Adding Space Range events
Open Space Range → Events for training faults and anomalies.
Do not confuse them with the ordinary spacecraft events under Properties → Events:
- ordinary Studio events drive simulation behavior such as camera pointing
- Space Range events introduce exercise faults, GPS effects, or packet changes
Use the shipped default event presets to find supported targets, models, and parameters for the installed Studio version.
For a first event, reduce a Transmitter’s bit rate:
- time:
100 s - repeat: off
- type: Spacecraft
- target: the converted spacecraft’s Transmitter
- parameter:
Bit Rate = 500
Preserving the converted mission
Adding brief, question, and event definitions does not require Construct Scenario for this path. Save the project after editing.
WARNING
If the content appears to require construction, stop and verify that you are still following the Inventory conversion workflow. Constructing can replace the placed spacecraft with definitions from the Space Range window.
Checking content before the full run
- open the brief in Operator
- confirm every question appears
- confirm the Space Range event appears in Admin
- confirm ordinary Studio events still work
- confirm Space Range event targets match the converted component names
For additional examples, see: