> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/products/drfx-visual-fivem-server-graphics-pack/configuration-and-tuning.md).

# Configuration & Tuning

Choose modules and test the visual result safely.

### Module selection

DrFx Visual is modular. Control which visual components load by adding or removing their ensure lines in server.cfg. Keep the original folder names.

### Recommended testing

1. Start with the complete package enabled.
2. Test during daytime, sunset, nighttime, rain, and clear weather.
3. Check city roads, countryside terrain, streetlights, and the sky.
4. If a conflict appears, disable one overlapping visual resource at a time.
5. Restart the server after every change.

### Asset Escrow files

Do not modify protected files. Only edit files that are explicitly provided as configurable. Renaming protected resource folders or altering escrowed files can stop the resource from starting.

### Updates

Back up your current configuration, replace the old package with the new download, restore only supported configuration changes, and restart the server.


---

# 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://drfx-store.gitbook.io/drfx-store-docs/documentation/products/drfx-visual-fivem-server-graphics-pack/configuration-and-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.