> 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/running-a-test.md).

# Running a test

How mechanics measure a car and what the result means.

1. The driver drives the car onto the dyno.
2. Start the test:
   * the mechanic targets the control point (**\[ALT]** ox\_target) → **Start dyno test**, or
   * a driver with the job presses **\[E]** in the car.
3. A countdown appears, then the car revs to the limiter and the chart grows on the TV.
4. The result shows peak **HP** and **Nm** with their RPM, and a comparison with the previous run (dashed line + HP difference).

Press **\[G]** at any time to cancel the test.

Everyone within `Config.SyncDistance` sees the test live – the TV chart, rising engine RPM and the wheels spinning on the rollers.

## Throttle modes

| `Config.AutoThrottle` | Behaviour                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------ |
| `true` (default)      | The car revs to the limiter by itself.                                                                 |
| `false`               | The driver has to hold **\[W]**. The test is cancelled after `Config.IdleTimeout` ms without throttle. |

## Access rules

* Only jobs listed in `Config.Jobs` (with the minimum grade) can start a test.
* `Config.RequireDriverJob = true` – the driver must also have a job from the list.
* `Config.RequireOnDuty = true` – the player must be on duty (QB/QBX only).
* Someone has to sit behind the wheel, and the car has to stand on the platform.
* After a test, the dyno waits `Config.Cooldown` seconds before the next one.

## Driver HUD

The TV is often not visible from the driver's seat. Set `Config.DriverHud = true` to also show a mini chart in the corner of the driver's screen (position in `Config.DriverHudPos`).

## How results are calculated

Power is calculated from the vehicle handling – `fInitialDriveForce`, `fMass`, `fInitialDriveMaxFlatVel` – plus LS Customs engine (mod 11) and turbo (mod 18) upgrades and engine health. Engine swaps from other scripts that change the handling are included automatically.

These are indicative RP values. Adjust them with:

* `Config.PowerScale` – multiplier for all results
* `Config.EngineModMult` – multiplier per engine level
* `Config.TurboMult` – turbo multiplier
* `Config.DefaultRedline` / `Config.RedlineByClass` – the rev limiter shown on the chart


---

# 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/running-a-test.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.