> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/prepare-your-scene/octane-standalone-and-orbx.md). # Octane Standalone and ORBX Check render targets and animation in Octane Standalone, then save an ORBX package for upload. ## Check an exported ORBX Open the `.orbx` file in Octane Standalone using **File → Open**, or drag the file into the application. Click a **Render Target** node in the **Node Graph Editor** to start its preview. See OTOY's [scene loading guide](https://docs.otoy.com/standaloneSE/SavingLoadingScenes.html). Check the camera, materials, lighting, and geometry against the scene in your 3D application. For an animation, use the viewport timeline to check the start, middle, and end, including frames with simulation or visibility changes. If something is missing, correct it in the source scene and export again. The [scene preparation checklist](/docs/prepare-your-scene/overview.md) covers missing files and caches. ## Set up render targets A render target combines a camera, geometry, lighting, and render settings. Several targets can share the same geometry while using different camera positions or settings. To add one in Standalone, right-click in the **Node Graph Editor** and choose **Render Target**. Connect the required nodes to its inputs, then click the target to check its render. OTOY's [render target guide](https://docs.otoy.com/standaloneSE/RenderTargetNode.html) explains the available connections. Configure [AOVs and render passes](/docs/prepare-your-scene/aovs.md) on the targets before saving. The targets found in the uploaded scene become choices when you [create a job](/docs/web-app/create-a-job.md). ## Save a package Choose **File → Save as Package** to save the scene as `.orbx`. ORBX packages the geometry, materials, textures, and animation together. An `.ocs` scene file on its own is not accepted by the web app. See OTOY's [ORBX format guide](https://docs.otoy.com/StandaloneH_STA/StandaloneSTA/TheORBXFileFormat.htm). If you opened an existing ORBX, **Save as Package** may be unavailable. Use **Save As** to save it as ORBX instead. See [Saving & Loading Scenes](https://docs.otoy.com/standaloneSE/SavingLoadingScenes.html). Follow [Upload Scenes](/docs/web-app/upload-scenes.md) to submit the package. For repeated uploads with large unchanged assets, see [Differential uploads](/docs/prepare-your-scene/differential-uploads.md). --- # 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://know.rendernetwork.com/docs/prepare-your-scene/octane-standalone-and-orbx.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.