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

# Installation & setup

Install vehicle resources and test spawn, garages, extras, and tuning separately.

## Installation

1. Check whether the product is an add-on or replacement vehicle. Read any game-build or additional-resource requirements.
2. Copy the complete resource into your resources folder. Keep the included manifest and metadata files together.
3. Start any required additional resources before the vehicle package.
4. Start the vehicle resource and check the server console.
5. Test the specified **model/spawn name** with your existing administration tool. Folder name, display name, and spawn name can differ.

## Garages and dealerships

Add the vehicle to your garage or dealership only after the direct model test works. Depending on the system, you may need the model name, category, price, database entry, or ownership data. Follow that system's documentation and the product instructions; there is no universal SQL statement for every garage.

If manual spawning works but the vehicle is missing from the shop, check its model mapping and the shop's conditions. Editing the vehicle model generally does not fix that integration issue.

## Test checklist

| Check               | What to look for                                                      |
| ------------------- | --------------------------------------------------------------------- |
| Model               | Correct vehicle, no duplicate resource using the same model name      |
| Basic use           | Entering, driving, collision, and intended seating                    |
| Appearance          | Paint, glass, interior, and textures                                  |
| Additional features | Only the extras, doors, lights, and animations listed for the product |
| Tuning              | Included options in the supported tuning system                       |

## Common issues

* **Will not spawn:** [Check the model name, resource startup, and spawn tool](/studioworks-docs/troubleshooting/spawn-issues.md).
* **Missing tuning or incorrect parts:** [Check tuning and metadata](/studioworks-docs/troubleshooting/tuning-lights.md).
* **Lights or sirens behave incorrectly:** Check extras, controls, and any included controller; see [Tuning, extras & lights](/studioworks-docs/troubleshooting/tuning-lights.md).
* **Crash when spawning or colliding:** [Narrow down the crash trigger](/studioworks-docs/troubleshooting/crashes-performance.md).

{% hint style="info" %}
Lighting, audio, and animation controllers are required only if the specific product lists them. Do not install unrelated controllers as a guess.
{% endhint %}

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

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