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

# Common Issues

This section covers the most common problems customers may experience with FiveM vehicles.

### Vehicle does not spawn

Check **Vehicle Does Not Spawn**.

### Vehicle is invisible

Check **Vehicle Is Invisible**.

### No handling

Check **No Handling / Vehicle Drives Incorrectly**.

### No sound

Check **No Vehicle Sound**.

### Tuning is missing

Check **Tuning Not Showing**.

### Textures are missing

Check **Missing Textures / Textures Not Showing**.

### Headlights are not working

Check **Headlights Not Working**.

### Sirens or emergency lights are not working

Check **Sirens & Emergency Lights Not Working**.

If none of these articles solve the problem, follow **Before Opening a Support Ticket**.


---

# 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://modster-customs.gitbook.io/modster-customs-docs/common-issues/03-common-issues.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.