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

# Installation

Install and start DrFx Visual on your FiveM server.

### 1. Download the resource

Download DrFx Visual from the CFX Portal or the delivery link associated with the Tebex purchase. Use the same CFX account that completed the purchase.

### 2. Prepare the files

Extract the download and keep the supplied folder names unchanged. Upload the DrFx Visual resource folders into your server's resources directory.

### 3. Configure the start order

Add the supplied resources to server.cfg in the order included with the package. Start the base DrFx Visual resource before its optional visual modules when the download instructions require it.

### 4. Remove conflicts

Disable other resources that modify the same roads, lighting, streetlights, terrain, clouds, or timecycle files.

### 5. Restart and verify

Restart the server completely. Join the server and verify roads, lighting, sky, terrain, and streetlights at multiple times of day.

If a module does not load, check the server console for the exact resource name and error.


---

# 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/installation.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.