> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark/show-modes.md).

# Show Modes

Spikemark can be run in Simulator or Live mode.

## Simulator Mode

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-e5bb55a155c898d3fbd034e9b9d530bdeec79cd7%2FSimulator%20Mode.gif?alt=media)

As the names suggest, Simulator Mode allows you to program cues and check out movements in the [Stage Model Viewer](/docs/spikemark/stage-model-viewer.md) without moving real machines. Cues can be run from the on screen [Cue Controls](/docs/spikemark/on-screen-control.md) or from a [Showstopper Consolette](/docs/showstopper/legacy/showstopper-consolette.md).

{% hint style="danger" %}
Spikemark initially enforces HTR in Simulator Mode. Change this to Soft Stop from the [Showstopper Consolette Settings](/docs/showstopper/legacy/showstopper-consolette/connecting-the-consolette-to-spikemark.md).
{% endhint %}

## Live Mode

Once you're ready to start moving real machinery, Switch to Live Mode, [Configure your machinery](https://app.gitbook.com/@creative-conners/s/spikemark/~/drafts/-MhJKiRfzaSH6l7HHiDo/spikemark/configuring-stagehands-in-spikemark) in Spikemark, and run all your cues that you programmed in Simulator Mode.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-9c85ccd793d0904071889f350fbaa6ccd5668f0d%2FLiveSim.gif?alt=media)

{% hint style="info" %}
Notice how in Live mode, the unit is dark grey by default. This means that it is not yet connected to Spikemark. The tan unit in the Simulator indicates that it is "connected" and ready to move!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.creativeconners.com/docs/spikemark/show-modes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.