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

# Invisible model or missing textures

Investigate invisible models, missing parts, and texture problems.

## Symptom

A model is fully or partly invisible, has incorrect surfaces, or loads correctly for only some players.

## Checks and fixes

1. **Compare with the original:** Is the complete package installed? Are streaming files missing, or have names or metadata been changed?
2. **Check the variant:** Use the correct model name and matching ped components. Weapons and attachments must belong together.
3. **Reconnect cleanly:** Test a newly connected client after the resource starts.
4. **Check conflicts:** Test without other packages using the same model or texture identifiers on your development server.
5. **Compare two clients:** Use the same position, distance, and action to check whether everyone is affected.
6. **Check dependencies:** Any additional package explicitly required by the product must be installed and running.

## Describe the scope

| Observation                               | Useful next test                                             |
| ----------------------------------------- | ------------------------------------------------------------ |
| Everyone sees the same issue              | Package, version, settings, and resource conflicts           |
| Only one player is affected               | Reconnect, save client errors, and compare another client    |
| Issue appears only at a distance          | Record the distance; possible LOD/streaming case for support |
| Textures are also missing on other assets | Check overall streaming load and newly added resources       |
| Issue started after a texture edit        | Compare the untouched original version                       |

## Avoid unnecessary resets

Do not delete game data or reset the entire server. Cache changes do not replace identifying the cause. If support requests a specific cache test, follow that procedure and preserve important local settings.

Keep protected files unchanged. For a reproducible issue in the original package, provide a screenshot or short video with distance, viewing angle, and model name.

**Include in your ticket:** Version, affected variant, whether all players are affected, original-file changes, and conflict-test results.

***

[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/models-textures.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.