> For the complete documentation index, see [llms.txt](https://ostomo.gitbook.io/ostomo-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ostomo.gitbook.io/ostomo-notes/graphics.md). # Graphics ### Natural world * LOD procedural generation: generate rough large-scale statistics like orbit, size, location, color + normal map, & store this only long-term * Then generate more and more details with a neural network client-side, on the fly * Will probably train a specialized neural network that given high-level stats & view, generates details that look identical to the high-level picture when zoomed out. * Can train this with sth like a GAN, with training samples produced "in reverse" by running a slow algorithm that procedurally generates detailed planets, then zoom out * No bikes or cars, or in general land vehicles: physics simulation too computationally intensive. Also who would want cars in a world where you can have hovercars ### Notes Need some fast GI approximation that doesn't rely on anything prebaked Target: half life 2 quality on integrated graphics Z-buffer tricks in space, possibly quadruple-precision floats in galaxy space as ground truth? Depends on travel mechanics --- # 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://ostomo.gitbook.io/ostomo-notes/graphics.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.