> 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/troubleshooting.md).

# Troubleshooting

<details>

<summary>The dyno is not visible</summary>

Check that `stream/rayn_dyno.ydr` and `stream/rayn_dyno_def.ytyp` are on the server, then reconnect. After the first install every player has to reconnect once so the game downloads the model.

With `Config.Debug = true`, run `/dynoprop` – it places the model in front of you and prints diagnostics to F8.

</details>

<details>

<summary>The same chart appears on several TVs</summary>

Standard GTA TVs (`prop_tv_flat_01` etc.) share one screen. Give every nearby dyno a different RAYN TV – one **RAYN TV 1**, the other **RAYN TV 2**.

</details>

<details>

<summary>The wheels spin backwards</summary>

Set `Config.WheelSpinDirection = 1.0`.

</details>

<details>

<summary>The dyno floats or sinks into the floor</summary>

Select it in `/dynocreator` and press **F** (to ground), or adjust the height with the gizmo.

</details>

<details>

<summary>The dyno prop or TV is visible through MLO walls</summary>

Set `Config.PinToInterior = true`. With `Config.Debug = true`, `/dynoroom` prints the interior and room of you and the pinned objects to F8.

</details>

<details>

<summary>"You do not have access to the dyno"</summary>

The player's job is not in `Config.Jobs`, their grade is too low, or they are off duty while `Config.RequireOnDuty = true`.

</details>

<details>

<summary>"You do not have permission to use the creator"</summary>

Add `add_ace group.admin rayn_dyno.admin allow` to `server.cfg`, or add the player's group to `Config.AdminGroups`.

</details>

<details>

<summary>The results look too low / too high</summary>

Results are indicative RP values calculated from the vehicle handling. Change the scale with `Config.PowerScale`, `Config.EngineModMult` and `Config.TurboMult`.

</details>


---

# 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/troubleshooting.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.