> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-pausemenu/troubleshooting.md).

# Troubleshooting

* **Settings take a few seconds, or GTA's settings screen opens:** the Apply key bindings were moved (see [Keys & Exports](/daddy-studios-docs/scripts/daddy-pausemenu/keys-and-exports.md)), or your FiveM build refuses instant writes. `Config.Settings` lets you turn either way off.
* **No background blur on the character:** Post FX must be Very High or Ultra and in-game depth of field on.
* **The map is empty for a moment:** the first open on a PC draws it from the game's textures; later opens are instant.
* **A blip shows a generic name:** add the shim to the resource that creates it, or call `SetBlipMeta` (see [Map & Blip Names](/daddy-studios-docs/scripts/daddy-pausemenu/map-and-blip-names.md)).
* **Picking a place does not move GTA's map:** after about 16 restarts of the resource in one game session the helper is unavailable until the game restarts; Enter still sets the route.
* **A HUD pack shows wrong blip icons:** set `Config.Map.GameIcons = false` (category letters).
* **Esc opens the menu during your minigame or placement mode:** call `Suppress(true)` while it runs.
* **Another HUD stays on top:** add it to `Config.Huds`, or hide it on `LocalPlayer.state.daddyPauseOpen`.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-pausemenu/troubleshooting.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.