> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/guidelines-compatibility/limitations/vr-mode-support.md).

# VR Mode Limitations

Support for immersive mode on Headsets and Phones

## Limitations

If you are designing for headsets or for VR mode on Phones, these are the limitations:

* Stick to [Universal Elements](/metaverse/build/elements.md#universal-elements). Other elements don't work in VR Mode.
* [HTML Only Elements](/metaverse/build/elements.md#html-only-elements) don't work in VR Mode. So avoid them.
* Gyro locks won't work in VR Mode.
* Viewer height scene property does not work in VR Mode.

## Designing for VR Mode

These are design consderations you should keep in mind when creating an experience primarily for headsets:

* Keep testing on a headset - if you build for headsets!
* Pay special attention to scale - keep things as life-scale as possible.
* Don't change the default viewer height - let it be the default.


---

# 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://docs.gmetri.com/guidelines-compatibility/limitations/vr-mode-support.md?ask=<question>&goal=<user_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.