# Prepare and run a game session

Choose a game in TholusOS, check installation and requirements, prepare controls and manage the session. Covers Chroma, Sagitta and Immersive SuperTuxKart.

Canonical: https://docs.theusualnext.com/en/tholusos/games/overview/
Updated: 2026-10-22
Publisher: the usual neXt

**Games** contains the catalogue and controls for preparing, starting and ending a game in the room. Each title presents its participation format, requirements and state; the available options depend on your installation and licence.

Some games are marked beta. Use the catalogue on your workstation to check current availability, supported formats and the preparation required by each title.

## Before choosing a game

A session needs an installed game, the required access, a configured room and the devices used by its selected mode. Requirements distinguish a title listed in the catalogue from a session that is ready for an audience.

Open **Room status** and check projection, audio and accessories. For a new installation, complete [Getting started](/en/tholusos/getting-started/) and [calibration](/en/tholusos/projection/calibration/). Check the movement area and participant equipment against the intended room configuration.

If another game is already open, return to that session and close it before preparing a different title. Check the game state and output availability before moving on to a video or experience.

## Read the catalogue and install a title

Each card shows the game, participation format, player count and status. Its information button also provides installation and licence details where available.

1. Open **Games**.
2. Use **Refresh game catalog** to check availability again.
3. Open the title’s information and check its requirements and download state.
4. If available, select **Download game**. Read the download size and free-space requirement in the confirmation, then choose **Download and install**.
5. Wait for completion before preparing the session.

**Release in preparation**, **Download suspended** and **Requires a compatible license** indicate conditions that need to be resolved before downloading. **Playback support needs an update** means this TholusOS version lacks the support needed to operate that catalogue title; check for a compatible TholusOS update. A visible card does not necessarily mean the game is ready on this workstation.

Update and uninstall actions are available from the card when the game is closed. Managed uninstallation moves the game to Trash and keeps saved games, settings and room configuration. If an external copy is detected, the app may offer **Show in Finder**; that copy is not moved or deleted automatically.

## Choose the participation format

The input device depends on the title and format. Read the card and configure the controls you actually have; different games can require different inputs.

| Title | Participation described in the app | What to check |
| --- | --- | --- |
| Tholus Chroma | Balls or pointers, depending on the format | Experience, saved configuration, room surface and input. |
| Sagitta | Balls on a screen or pointers in a dome | Selected mode, output, input detection and calibration. |
| Immersive SuperTuxKart | One driver, with an optional crew | Driving device, track, participants, output and driver handoff. |

Refer to the catalogue information for the participant count supported by the installed version. For modes with pointers or sensors, prepare and check those devices in Room. A title appearing in the catalogue does not replace its input configuration.

## Prepare the session

The game page contains session options and its preparation command. Preparation may open the game software and check connections, so perform this step when you are ready to use the room.

1. Select a title from the catalogue.
2. Check **This game** and any **More options**. Audience, duration, difficulty and game-specific choices vary by title.
3. Open **Configuration** for the required connections and devices.
4. Resolve attention messages using the suggested action to reach the relevant settings.
5. Select **Prepare game** or the title’s specific preparation command.
6. Wait for the ready state and check that participants understand how to interact.

A missing requirement keeps dependent commands unavailable. To investigate a blocker, open **Details**: this panel reports the session’s state, messages and requirements. Sensor and equipment tests are available through Room.

## Use Chroma experiences

Chroma provides an **Experiences** view for selecting an experience and saved configuration, with a preview on the Mac and separate preparation and start commands.

These controls apply when an enabled Chroma build is available on the installation. If the catalogue says **Release in preparation**, the download is not yet available; use the catalogue's current availability status before planning the activity.

Open the experience, choose a configuration and check its mode, language, duration and music. Where available, change the layout or preview view to inspect how the content occupies the surface. The computer preview does not start the projectors.

Check **Room status**, then use **Prepare** and **Start** when the conditions are met. The **Room controls** tab provides the game’s operational controls. If an experience has no usable configuration, complete one before the session.

## Start, pause and finish

When the session is ready, choose **Start game** or the title’s equivalent command. During play, controls are shown according to the current state, including pause, resume and stop where supported.

Immersive SuperTuxKart may show **Start countdown** after preparation. The driver uses the game controls; crew phones are optional. When phone participation is available, **Show join code** opens the session QR code. Use the address shown for that session.

For local phone participation, connect phones to the room network and start the local server. When offered by the selected game and enabled for the installation, **CloudPlay** provides a cloud joining route; check its connection status before sharing its code. **Check phone connections** opens the network controls when a local joining address is unavailable.

If the selected mode requires it, use **Confirm pilot handover** once the next driver is ready. At the end, review the result and choose **Play again** to prepare another game, or **Close game** to release the output when that command is available.

**Stop game** and **Close game** have different roles: stopping a round may leave the software open for another session. Before switching to [media playback](/en/tholusos/media-server/playback/), check that the output has been released.

## Troubleshoot common problems

The game page’s message identifies the requirement to check. Start with that message to avoid unnecessary changes to the room configuration.

| Message or symptom | Action |
| --- | --- |
| No games available | Check access, catalogue and installation, then open Room status. |
| A game is already open | Return to the active game and close its session before switching. |
| Needs checking or preparation | Open Configuration and complete the listed requirements. |
| Device disconnected | Reconnect the expected input or select a compatible device. |
| Join QR unavailable | Check participation status and the network service used by the session. |
| Attention required | Open Details and follow the offered recovery action; check the state before resuming. |
| Output occupied after stopping | Check whether the game software still requires Close game. |

For checks shared with media and experiences, see [Troubleshoot playback and sessions](/en/tholusos/settings/troubleshooting/).