# Colliders

Colliders are structures that prevent viewers from walking through a space.

There are three types of colliders - Scene Bounds, Collider Volume, Collider Mesh

{% hint style="info" %}
For colliders to work, ensure that "**Enable Collisions**" is enabled in Scene Properties
{% endhint %}

## Scene Bounds

Scene Bound is the boundary of your scene. Every place that you want the viewer to visit should be within the Scene Bounds.

In the editor, scene bounds are visible as a grid and can be toggled from the **Viewport Properties**. Scene bounds are only visible in the editor - you can't see them in the deployed link.

<figure><img src="/files/mZtsXCx5h7UoPoyfyOXX" alt=""><figcaption><p>Scene Bounds</p></figcaption></figure>

### How can I change Scene Bounds?

To modify the Scene bounds of your scene, go to the 'Structure' option and select 'Scene'. Then, you can adjust the X, Y, and Z axis ranges to make the necessary changes.

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FPKAyZgs1RBG1TnVzuPgz%2Fimage.png?alt=media&#x26;token=471122a0-ce19-4c9f-96ec-3df93983bd4a" alt=""><figcaption><p>How to change the scene bounds in your experience</p></figcaption></figure>

{% hint style="info" %}
If you want to remove Scene Bounds - set its size to 0
{% endhint %}

Here's an example experience for Scene Bound. The scene bounds prevent you from going near the windows.

{% embed url="<https://rnghud.gmetri.com/Scenebounds>" %}
Scene bounds - Sample experience
{% endembed %}

## Collider Volume <a href="#collider-box-element" id="collider-box-element"></a>

A Collider Volume is an invisible box/sphere/cone/volume that objects will rest on top of. Without colliders, viewers will fall through floors and go through walls and benches. The position, shape and dimensions of this volume can be adjusted from the properties panel.

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2F0FecCaIzBtp1ZFYvzQ02%2Fimage.png?alt=media&#x26;token=4e07abfe-2cbb-4605-9aa1-5c7fb1226e96" alt=""><figcaption><p>Collider box element</p></figcaption></figure>

In view, the collider box elements are represented as invisible cubes with which the players will collide and not walk through.

## Collider Mesh

Enhance your experience by incorporating a 3D object that has collision capabilities. You can either upload your own customized 3D model or choose one from our pre-installed libraries.

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2Fua2T8roCYYZH6c56cEw4%2Fimage.png?alt=media&#x26;token=aeb5b02d-469d-4e7f-a27f-2ebcccdc337b" alt=""><figcaption><p>Collider Mesh</p></figcaption></figure>

## Collider Example

Here's an example of how a collider works on an experience:

{% embed url="<https://rnghud.gmetri.com/colliders>" %}
Colliders - Sample experience
{% endembed %}

## Video Tutorial for Colliders

{% embed url="<https://www.youtube.com/watch?v=EDsC1Z2hRj4>" %}
Collider Tutorial
{% endembed %}


---

# Agent Instructions: 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:

```
GET https://docs.gmetri.com/metaverse/build/scenes/3d-scene/colliders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.