> For the complete documentation index, see [llms.txt](https://help.rhinonature.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhinonature.com/requirements.md). # Requirements ## Minimum * Quad Core 2.5 GHz 64-bit Processor * 8 GB RAM Memory * 1 GB Disk Space * Rhinoceros 5 64-bit * Windows 7 64-bit ## Recommended * Hyperthreaded Quad Core 3.0+ GHz 64-bit Processor * 16+ GB RAM Memory * 1 GB Disk Space * Rhinoceros 7 64-bit * Windows 10 64-bit ## Supported renderers Currently, Rhino Nature works seamlessly with the following render engines: * Octane (2020.1.4.122 and above) * Rhino Render - Cycles (Rhino 7 and above) * Unreal Engine (Datasmith) * V-Ray (5.00.01 and above) Hopefully, this will be an ever-growing list. If you are a user and your favorite engine is not listed, nothing's lost. You can take action by notifying the development team of your tool of choice that there is a simple API allowing tight integration with it, and redirect them here. If you are a developer you probably look for several words of explanation about [integrations](/api/integrations.md). In case you need an NFR license for heavy field tactic inspections of your integration, drop an email at [support@rhinonature.com](mailto:%20support@rhinonature.com). --- # 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://help.rhinonature.com/requirements.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.