Testing the Converted Mission

Test the converted mission without reconstructing it. The saved Studio project, its placed objects, and their Space Range controller assignments are the source of truth.

Reopening the saved project

Close and reopen the project. Check that:

  • spacecraft and ground stations load
  • team assignments remain
  • ordinary Studio events remain
  • the Space Range brief, questions, and events remain

This catches controller or configuration changes that were never saved.

Checking the Console

Open the Console Panel and connect with a temporary session name.

Fix:

  • missing-ground-station messages
  • unassigned spacecraft
  • missing or duplicated team IDs
  • component or controller errors

Testing as an operator

Join with every enabled test team and confirm:

  1. the correct spacecraft appears
  2. another team’s spacecraft does not appear as controlled
  3. the expected components appear
  4. basic commands receive responses
  5. telemetry and ground access work
  6. the brief renders
  7. all questions appear

Testing both event systems

Run from reset:

  • confirm ordinary Studio events still perform their intended actions
  • confirm each Space Range scenario event fires at the intended simulation time
  • verify the event changes telemetry or behavior
  • confirm matching questions can be answered

An event marker alone is insufficient. Check the actual component state.

Fixing conversion-specific errors

Team joins with no spacecraft

  • recheck the spacecraft’s Space Range team assignment in Properties
  • save and reopen the project
  • confirm the team is enabled
  • inspect the Console

No communication

  • confirm a valid ground station exists
  • confirm the first station is suitable
  • confirm the Receiver and Transmitter exist
  • confirm team frequency and key settings

Inventory objects disappear

The project was constructed from Space Range definitions. Reopen the pre-conversion backup and repeat the assignment without selecting Construct Scenario.

Space Range event has no effect

  • use the exact component name from the placed spacecraft
  • use a supported preset target and model
  • check parameters
  • verify the affected team and asset

Exporting the handoff

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

Give the facilitator:

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

The facilitator continues with Hosting a Space Range.