Constructing and Testing

Construct Scenario turns the definitions in the Space Range window into the Studio world. Test that world from the participant’s perspective before handing it to a facilitator.

Reviewing the configuration

Before constructing, check:

  • Pathfinder exists with ID SC_001
  • its required components exist and have unique names
  • Main contains SC_001
  • Blue Team is enabled and assigned to Main
  • Madrid and Singapore exist under Stations
  • the simulation ends after the 100-second event
  • the brief has no private answers
  • both questions have non-zero scores
  • Low Bit Rate is enabled

Constructing the world

Save the project, then select Construct Scenario.

Studio:

  1. clears the currently constructed Space Range world
  2. applies the simulation and universe settings
  3. creates stations and other objects
  4. creates a ground controller for each enabled team
  5. resolves each team’s collection
  6. creates the spacecraft in that collection

WARNING

Construction replaces existing Space Range-managed spacecraft and stations. This behavior is expected in this definitions-first path, but it can destroy an Inventory-built mission. Use the intermediate conversion path when preserving manually placed Studio objects.

Inspecting the Console

Open the Console Panel. Fix every Space Range warning or error before connecting.

Check for:

  • missing ground stations
  • missing collections
  • missing spacecraft IDs
  • unsupported component classes
  • unsupported component variables
  • invalid event targets

Studio can skip one invalid item and continue constructing the rest. A partly populated Outliner is not proof that the scenario is valid.

Joining the test session

Under Client, use a temporary session name. Configure the intended broker and admin password, then select Connect Client.

Join from Operator as Blue Team using its six-character password.

Confirm:

  1. the session can be found
  2. the password is accepted
  3. Pathfinder appears
  4. the expected components appear
  5. a basic command receives a response
  6. the brief renders
  7. both questions appear

Running the exercise

Reset, then run from the beginning:

  1. verify normal telemetry before 100 seconds
  2. run past 100 seconds
  3. confirm Low Bit Rate appears in Admin
  4. confirm the Transmitter bit rate changes
  5. answer the orbit question
  6. answer the communications question
  7. confirm the expected score
  8. reset and repeat the smoke test

Fixing common errors

Blue Team joins with no spacecraft

Check:

Blue Team → Main → SC_001 → Pathfinder

The team collection, collection ID, listed spacecraft ID, and spacecraft definition must all exist.

No team can communicate

  • confirm at least one valid station was created
  • confirm the first station is valid
  • confirm the team frequency and key
  • confirm Pathfinder has its receiver and transmitter
  • inspect the Console

A question is missing

  • use Text, Number, Select, or Checkbox
  • give Number and Select an expected value
  • check option ordering
  • reconstruct and test with a new team

An event appears but does nothing

  • match the target component name
  • use a supported target model
  • check parameter spelling and capitalization
  • check the selected assets
  • verify the resulting telemetry

Exporting the facilitator copy

Save the successful project and export it as a .zen file. Re-import that file into a clean Studio library and repeat the join test.

Give the facilitator:

  • the versioned .zen file
  • the Studio version
  • team credentials through a secure channel
  • the admin password through a secure channel
  • a private event timeline and expected outcomes

The facilitator can now follow Hosting a Space Range.