This step converts the placed Studio spacecraft into a team-operated Space Range asset. The assignment is stored with the Studio project.
Creating the team
Open Space Range from the toolbar, then open Teams.
Create an enabled team with:
- a clear name
- a unique numeric ID
- a unique six-character password
- a starting frequency
- a starting telemetry key
- a distinct color
For the worked example, use Blue Team.
The participant joins with the password, not the numeric ID. See Configure the Server and Teams for each team field.
Assigning the placed spacecraft
Return to the main Studio workspace and select the spacecraft.
In its Properties, open the Space Range configuration and assign the spacecraft to Blue Team. Repeat this for every spacecraft participants should operate.
Do not assign:
- decorative or passive objects
- spacecraft that should remain facilitator-controlled
- shared neutral targets
- another team’s spacecraft
Saving the controller assignment
Reset the simulation, then save the project. Studio stores the spacecraft’s Space Range controller and team linkage with the project.
Close and reopen the project before the first full test. Confirm that:
- the spacecraft still exists
- its team assignment remains
- the ground station remains available
Avoiding Construct Scenario
Do not select Construct Scenario in this path.
Construction:
- clears Space Range-managed stations and spacecraft
- applies definitions from the Space Range window
- creates spacecraft through collections
That is correct for the beginner definitions-first path and advanced JSON path, but not for preserving manually placed Inventory objects.
If construction removes the mission, reopen the backup made before conversion.
Running the first connection test
Under Client, configure a temporary session name and the intended broker. Connect, then join from Operator with the team’s password.
Before adding the brief, questions, or faults, confirm:
- the team can join
- its spacecraft appears
- the expected components appear
- a basic command receives a response
- no missing-ground-station message appears in the Console
Fix this connection gate before continuing.
Next, add the training content.