> 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/requirements.md). # Requirements Compatibility and requirements before installing DrFx Visual. Review these requirements before installing DrFx Visual. ### Required * A working FiveM server with access to the resources directory. * Access to the CFX account used for the Tebex purchase. * Permission to edit server.cfg and restart the server. * Up-to-date FiveM server artifacts. ### Compatibility notes DrFx Visual is a server-side graphics resource. Players receive the supported visual changes from the server and do not need a separate graphics pack. Avoid running other resources that replace the same roads, lighting, streetlights, terrain textures, clouds, or timecycle files. Conflicting visual resources can overwrite each other and cause inconsistent results. ### Before installation Back up server.cfg and any existing visual resources. Remove or disable conflicting visual packs before testing DrFx Visual. --- # 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/requirements.md?ask=&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.