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

# Vehicles

Choose your symptom to get the quickest checks and a focused solution.

## What is happening to your vehicle?

Choose the description that matches what you see. Each guide starts with a quick check, then the fix and a way to verify it worked.

| I have this problem                                                                                  | What we check first                                                                                              |
| ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| [Vehicle won't spawn](/studioworks-docs/vehicles/wont-spawn.md)                                      | Check the resource starts without errors, then compare the exact spawn/model name with the product instructions. |
| [Vehicle missing from the garage](/studioworks-docs/vehicles/missing-from-garage.md)                 | Confirm the direct model test works before editing vehicle files.                                                |
| [Tuning is missing or incorrect](/studioworks-docs/vehicles/missing-tuning.md)                       | Confirm the product actually includes the option and your tuning menu supports it.                               |
| [Lights or sirens don't work](/studioworks-docs/vehicles/lights-sirens.md)                           | Check the intended controls and required extras. Siren sound and lighting are separate tests.                    |
| [Vehicle is invisible or missing textures](/studioworks-docs/vehicles/invisible-missing-textures.md) | Compare your installation with an untouched complete package.                                                    |
| [Crash when spawning or driving](/studioworks-docs/vehicles/crash-spawn-impact.md)                   | Save the crash text and identify whether one client, all players, or the server process is affected.             |

{% hint style="info" icon="magnifying-glass" %}
**Have an exact error?** Search the message at the top of the page (**Ctrl + K**). Keep the error wording; leave out passwords, license keys and tokens.
{% endhint %}

## I am installing this for the first time

[Installation & setup](/studioworks-docs/vehicles/installation.md) · [Requirements](/studioworks-docs/installation/requirements.md)

## I could not find my problem

[General error messages](/studioworks-docs/troubleshooting.md) · [Contact support with logs](/studioworks-docs/support/preparing-a-ticket.md)


---

# 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://studioworks.gitbook.io/studioworks-docs/vehicles.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.