Complete and test the mission as an ordinary Studio project before opening Space Range. This keeps simulation-design problems separate from team and exercise problems.
Learning the Studio workflow
If you have not built a Studio mission before, complete these existing paths first:
The spacecraft tutorial covers:
- creating a spacecraft and orbit
- adding a chassis and components
- configuring the environment
- adding ordinary Studio events
- plotting data
- running the simulation
Those pages remain the source for normal Studio construction. This sequence begins where that tutorial ends.
Building your own mission
Your Studio project should have:
- a meaningful project name
- the intended primary planet and epoch
- one or more spacecraft
- configured orbits
- a chassis and mission hardware
- any ordinary Studio events required by the simulation
- plots or views needed to verify behavior
Add and configure objects with the Inventory Panel, Outliner Panel, and Properties Panel.
Testing before conversion
From the reset state:
- play the simulation
- confirm every spacecraft follows the expected orbit
- confirm attitude control and payload actions work
- confirm ordinary Studio events fire
- check plots and the Console
- reset the simulation
- save the project
Use Saving a Simulation and Save Files for current persistence behavior.
NOTE
Ordinary Studio events and Space Range scenario events are separate. Keep events that drive normal spacecraft behavior. Add training faults later through Space Range → Events.