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

# Missing tuning, extras or lights

Check missing tuning options, extras, and vehicle lighting.

## Missing tuning or incorrect parts

**Possible causes:** The option is not included, your menu does not support it, tuning metadata has not loaded, or another vehicle package conflicts.

1. Check which tuning options the product actually includes.
2. Test the untouched vehicle using the intended or compatible tuning system.
3. Confirm that the included metadata files are complete and the original manifest is used.
4. On your test server, test without other vehicle packages with conflicting model/modkit assignments.
5. Test again after a planned restart and reconnecting the client.

{% hint style="warning" %}
Do not change modkit IDs as a guess. Incorrect assignments can create additional conflicts. Report a confirmed conflict with the affected packages and their assignments.
{% endhint %}

## Missing extras

Extras and tuning parts are different features. Check the extras listed in the product instructions and whether your menu can toggle them. Garages may restore an old saved vehicle state. Compare a fresh test spawn with the saved vehicle.

## Headlights, warning lights, or sirens do not respond

1. Test the correct model using its intended controls.
2. Check whether the required extras are enabled.
3. If the product requires a light/siren controller, check installation, start order, and vehicle assignment.
4. Separate **sound** from **lighting**: Hearing a siren does not prove its lights are configured correctly.
5. Test without competing lighting or siren controllers on your development server.
6. Compare the result on two clients.

Animations, emissive effects, and special light sequences are included only if the product lists them.

**Include in your ticket:** Vehicle name, affected option, menu/controller, fresh or saved spawn, and a short video.

***

[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/troubleshooting/tuning-lights.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.