> For the complete documentation index, see [llms.txt](https://docs.scenery.graphics/sciview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scenery.graphics/sciview/vr-and-ar/vr-and-ar.md). # VR & AR ## Prerequisites sciview works with all VR headsets that are supported by SteamVR, including: * Oculus Rift S * HTC Vive, HTC Vive Pro, HTC Vive Pro Eye * Valve Index * Windows Mixed Reality headsets (such as the Samsung Odyssey) In addition, we have alpha-quality support for the Microsoft Hololens. Support for this AR headset will be extended in the future. For the moment and in the remainder of this article here, we concentrate on VR headsets. In order to be able to use VR headsets for rendering in sciview, especially when rendering volumetric data, a relatively powerful computer is recommended. Our recommendation there would be to have at least 16-32 GB of RAM, and a GPU capable of fast VR rendering at high resolutions, such as a Geforce RTX 2080 or an AMD Radeon RX5700. sciview relies on [SteamVR/OpenVR](https://store.steampowered.com/app/250820/SteamVR/) for rendering to your VR headset. You can follow the [setup guide for the HTC Vive](https://support.steampowered.com/steamvr/HTC_Vive/) for setting it up, or use the one for your specific headset. Note that if you use a Windows Mixed Reality headset, you need to have [Windows Mixed Reality for SteamVR](https://store.steampowered.com/app/719950/Windows_Mixed_Reality_for_SteamVR/) installed in addition to SteamVR itself. ## Rendering to your VR headset in sciview To activate rendering to an attached VR headset, choose `View`> `Render to OpenVR HMD` in sciview's menu bar. If not already open, SteamVR will start and the current scene will appear in your VR headset. --- # 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.scenery.graphics/sciview/vr-and-ar/vr-and-ar.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.