> For the complete documentation index, see [llms.txt](https://docs.odyssey.stream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.odyssey.stream/faq/vulkan-renderer.md). # Vulkan renderer Odyssey ships all projects using Linux, which uses the Vulkan renderer. Currently Vulkan has some limitations that can either cause stability issues, or visual differences from Windows. {% hint style="info" %} Epic is committed to fixing these issues and bringing Vulkan inline with directX on the 5.4 release. {% endhint %} ## Known issues * **Hardware Raytracing** is not supported. * **DLSS** is not supported. * **SM6** features are not supported. * **Panning textures** are not supported. * **Virtual shadow maps** can occasionally have visual issues. * **Nanite double-sided foliage** renders incorrectly. ## Testing Vulkan locally It's helpful at times to test Vulkan locally if you are debugging certain visual issues. You can achieve this by packaging your project locally and running with `-Vulkan` argument. 1. Enable SM5 in Project Settings -> Platforms - Windows -> Vulkan Targeted Shader Formats. 2. Package your project. 3. Run your project through a command line with the `-Vulkan` argument. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.odyssey.stream/faq/vulkan-renderer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.