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

# Model won't spawn

Check the model identifier, resource startup, and spawn tool separately.

## Symptom

A vehicle or ped fails to appear, is reported as unknown, or disappears immediately. A weapon cannot be given or equipped.

## Possible causes

Incorrect model name, unloaded resource, another package using the same model identifier, or restrictions in a menu, framework, or spawn script.

## Checks and fixes

1. **Read the startup log:** The resource must start without entitlement or manifest errors.
2. **Verify the identifier:** Use the exact model/spawn name in the product instructions. Folder names and store display names are not reliable substitutes.
3. **Test directly:** Use an existing authorized administration tool. Chat commands depend on your server; guessed `/car` or `/ped` commands are not universal tests.
4. **Reconnect:** Test a newly connected client after a clean installation.
5. **Isolate conflicts:** Disable other packages with the same model identifier on a development server. Do not remove random metadata entries.
6. **Check integration:** If the direct test works, investigate the garage, menu, inventory, or dealership.
7. **Investigate disappearing entities:** Check entity-cleanup, garage, and administration logs/settings. Do not broadly disable protection systems on your live server.

## Interpret the result

| Result                              | Next step                                                                         |
| ----------------------------------- | --------------------------------------------------------------------------------- |
| Resource fails during startup       | [Resource won't start](/studioworks-docs/troubleshooting/resource-wont-start.md)  |
| One tool works and another does not | Check the second tool's permissions and settings                                  |
| Model loads but is invisible        | [Models & textures](/studioworks-docs/troubleshooting/models-textures.md)         |
| Spawning causes a crash             | [Crashes & performance](/studioworks-docs/troubleshooting/crashes-performance.md) |

**Include in your ticket:** Model identifier, product version, spawn tool, exact error, and result of the direct test.

***

[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/spawn-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.