> For the complete documentation index, see [llms.txt](https://rayn-scripts.gitbook.io/rayn-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_dyno/creator.md).

# Creator

Place dynos, control points and TVs in-game with /dynocreator.

Run `/dynocreator` (admins only – see [Installation](/rayn-scripts-docs/rayn_dyno/installation.md#who-can-use-the-creator)). The creator opens a free camera and a panel with your dynos.

## Creating a dyno

1. Click **+ New dyno** and click the spot where the car should stand. The dyno faces the camera direction – the orange outline shows the car position and the line shows the front.
2. Fill in the **Basic** section – name and platform radius (m).
3. *(Optional)* **Control point** – click **+ Set point** and click in the world. This is the ox\_target point where the mechanic starts the test. Without it, a driver with the job starts the test with **\[E]** in the car.
4. **Chart TV** – pick a TV model, then click **+ Place TV** and click where it should hang. Set **Visible from (m)** for the draw distance.
5. Click **Save**.

Saving writes to `data/dynos.json` and works for all players immediately – no restart needed.

## Options

| Option                  | Description                                                                                           |
| ----------------------- | ----------------------------------------------------------------------------------------------------- |
| **Dyno prop (rollers)** | Turn it off if your MLO already has its own dyno – the creator then shows only a transparent preview. |
| **Spawn the TV**        | Turn it off if the chosen TV model already hangs in your MLO – the chart will appear on it.           |
| **TV model**            | `RAYN TV 1` or `RAYN TV 2`, from `Config.Monitors`.                                                   |

{% hint style="warning" %}
**Two dynos close to each other?** Give one **RAYN TV 1** and the other **RAYN TV 2**. Each RAYN TV has its own screen. Standard GTA TVs (`prop_tv_flat_01` etc.) share one screen, so the chart would appear on every such TV nearby. The creator warns you when a TV is already used by another dyno.
{% endhint %}

## Controls

| Key             | Action                     |
| --------------- | -------------------------- |
| LMB             | Select / drag a gizmo axis |
| RMB             | Look around                |
| W A S D + Q / E | Fly                        |
| Shift           | Faster                     |
| T               | Move mode                  |
| R               | Rotate mode                |
| F               | Drop to ground             |
| Delete          | Remove the selected object |
| Esc             | Deselect                   |

Camera speed and snapping are set in `Config.Editor` – see [Configuration](/rayn-scripts-docs/rayn_dyno/configuration.md#dyno-creator).

{% hint style="info" %}
The creator handles placement only. Jobs, run timing and results are still configured in `config.lua`.
{% 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://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_dyno/creator.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.