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

# Overview

Chassis dyno with a live HP/Nm chart on an in-world TV – visible to every nearby player – built in-game with a 3D creator.

A chassis dyno for mechanic shops. The car drives onto the rollers, the engine revs to the limiter, the wheels spin and the TV in the workshop draws a live **power (HP)** and **torque (Nm)** chart – visible to every nearby player.

Dynos, control points and TVs are placed in-game with `/dynocreator` – free camera and gizmo, no typing coordinates. The framework (ESX, QBX or QB) is detected automatically.

## Features

* Custom `rayn_dyno` model (rollers, eddy-current brakes, ramps, console, fan) – included in `stream/`
* Two custom TVs, `rayn_dyno_tv1` and `rayn_dyno_tv2` – each has its own screen, so two dynos in one shop show their own charts
* HP/Nm chart on an in-world TV + optional mini chart in the corner of the driver's screen
* Comparison with the previous run (dashed line, HP difference)
* Engine RPM and spinning wheels synced for all players
* Job-locked access (ESX / QBX / QB)
* ox\_target or the **\[E]** key
* Result calculated from the vehicle handling – includes tuning (LS Customs engine, turbo, engine swaps from other scripts)
* Full translation support – English and Polish included

## Where to go next

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-list-check" style="color:$primary;">:list-check:</i></h3></td><td><strong>Requirements</strong></td><td>Dependencies and supported frameworks.</td><td><a href="/rayn-scripts-docs/rayn_dyno/requirements.md">Requirements</a></td></tr><tr><td><h3><i class="fa-rocket" style="color:$primary;">:rocket:</i></h3></td><td><strong>Installation</strong></td><td>Get rayn_dyno running on your server.</td><td><a href="/rayn-scripts-docs/rayn_dyno/installation.md">Installation</a></td></tr><tr><td><h3><i class="fa-wand-magic-sparkles" style="color:$primary;">:wand-magic-sparkles:</i></h3></td><td><strong>Creator</strong></td><td>Place dynos, control points and TVs in-game.</td><td><a href="/rayn-scripts-docs/rayn_dyno/creator.md">Creator</a></td></tr><tr><td><h3><i class="fa-car" style="color:$primary;">:car:</i></h3></td><td><strong>Running a test</strong></td><td>How mechanics measure a car.</td><td><a href="/rayn-scripts-docs/rayn_dyno/running-a-test.md">Running a test</a></td></tr><tr><td><h3><i class="fa-sliders" style="color:$primary;">:sliders:</i></h3></td><td><strong>Configuration</strong></td><td>Every option in config.lua.</td><td><a href="/rayn-scripts-docs/rayn_dyno/configuration.md">Configuration</a></td></tr><tr><td><h3><i class="fa-circle-question" style="color:$primary;">:circle-question:</i></h3></td><td><strong>Troubleshooting</strong></td><td>Fixes for the most common issues.</td><td><a href="/rayn-scripts-docs/rayn_dyno/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

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