> 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/metaverse/build/scenes/360-scene.md). # 360 Scene ## Properties of a 360 Scene The properties panel in a 360 scene provides multiple options to adjust an element or an item in an experience.

### View The functionalities of Yaw, Reset Rotation, and Allow Zooming in any experience are similar to those in a 3D scene. * **Gyro Lock** - Enabling this option will lock the gyroscope view of the experience. If the option is not checked, the adjustments to the gyroscope view can be made by adjusting the yaw and pitch ranges. ### Advanced Environment Map and Selective Bloom in any experience are similar to those in a 3D scene. ## How do I add a 360 panorama into my experience? ### Step 1: Add a 360 Scene You can add a 360 scene by clicking on the '**+**' icon in the left bar and selecting '**360 Scene'.**

### Step 2: Go to properties of Pano Element and select Upload/Choose File

{% content-ref url="/pages/89Dj2jFYZ5UbZ0t6i2fd" %} [Selecting a file](/metaverse/build/editor/file-manager/3rd-person-scenes.md) {% endcontent-ref %} ### Example 360 Scene {% embed url="" %} 360 Scene Example {% endembed %} --- # 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/metaverse/build/scenes/360-scene.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.