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

# Tuning is missing or incorrect

Tuning options are absent, the wrong parts appear, or changes are not saved.

{% hint style="info" icon="bolt" %}
**Quick check:** Confirm the product actually includes the option and your tuning menu supports it.
{% endhint %}

## Fix it

1. Test a freshly spawned vehicle, without a saved garage state.
2. Keep the original manifest and all supplied tuning metadata together.
3. On a test server, isolate other packages with conflicting model or modkit assignments. Do not change IDs on a guess.

## Check the result

The documented parts appear on a fresh vehicle. If they disappear only after parking, check garage persistence.

## Still happening?

[More detailed checks](/studioworks-docs/troubleshooting/tuning-lights.md) · [Prepare a support ticket](/studioworks-docs/support/preparing-a-ticket.md)

Include the product version, first error, and the steps you tried. Keep secrets out of logs and screenshots.


---

# 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/missing-tuning.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.