> For the complete documentation index, see [llms.txt](https://raceonlife.gitbook.io/raceonlife/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raceonlife.gitbook.io/raceonlife/our-vision/why-unreal-engine.md). # Why Unreal Engine? We chose Unreal Engine for several reasons. The UE 5 version is perfect for creating tropical island races and includes all the latest innovations in game dev. Furthermore, it easily adapts to various platforms. One of the key advantages of UE 5 is the innovative Lumen lighting system. This technology allows developers to create fully dynamic lighting in real time, very close to the graphics produced by cutting-edge computers for high-quality animation and film production. Out of all game engines, UE 5 has one of the fastest scripting and shader compile times. Nanite is the most unique development on UE 5, allowing us, as developers, to automatically and massively scale in-game art assets. Thanks to Nanite's virtualized micro polygon geometry, artists are given complete freedom in creating geometric details as much as the eye can perceive. Currently, game artists often downscale various levels of detail (LOD) for in-game 3D models, each of which has fewer polygons and smaller textures than the previous one. You can notice these low-polygon models when an object is a decent distance from the game camera. This practice is used to save memory space and render time in complex scenes without sacrificing frame quality. But with Nanite, everything has changed. Now artists can import cinematic-quality models containing hundreds of millions, if not billions, of polygons. Since Nanite scales LOD in real-time, there is no need to allocate budgets for polygon counts, polygon memory, and draw calls. Essentially, UE 5 performs the work of creating LOD models according to the scene on the target hardware without quality loss. --- # 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://raceonlife.gitbook.io/raceonlife/our-vision/why-unreal-engine.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.