> 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/troubleshooting.md). # Troubleshooting Fix common DrFx Visual installation and conflict issues. ### The resource does not start * Confirm the folder names match the original download. * Confirm every ensure line matches an installed resource folder. * Check that the purchasing CFX account has access to the asset. * Read the first relevant error in the server console. ### Some visual changes are missing Confirm all selected DrFx modules are started. Clear the FiveM client cache, reconnect, and test again. Also check whether another map or visual resource replaces the same files. ### Lighting or roads look incorrect Temporarily disable other timecycle, road, lighting, streetlight, terrain, cloud, and weather resources. Re-enable them one at a time to identify the conflict. ### Players see different results Ask affected players to reconnect after clearing their FiveM cache. Confirm the server is running the same DrFx Visual version for everyone. ### Still need help? Join the DrFx Discord and include your order information, server framework, artifact version, enabled DrFx modules, and the relevant console 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/troubleshooting.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.