# 12-08 Dec Update ### :rocket: Major Features * A new section at the top of you portal - **My Metaverse Rooms** which is a set of deployments that you can use out of the box with a GMetri account.

My Metaverse Rooms

* Replaced "Cube Collider" with "**Collider Volume**" elements that allows many shapes like sphere cube, cone, cylinder, sphere, polygon and torus. * Added a new element "**Collider Mesh**" that allows you to specify a 3D file (glb or gltf) as a collider. * Added a new property "**Mouse Jump**" to both collider elements that lets you decide if the user should be allowed to jump on the collider using right click or not. * Added a new element "**Workspace Logo**" that gets replaced with the Workspace Logo (or the Project Logo if you have specified that) depending on which workspace the project is in. * Added a new property to 3D elements - **Environment Map Intensity**. This can be used to reduce any "burn" in a 3D Model caused by the environment map selected in a scene. ### :arrow\_double\_up: Minor Improvements * Added **Fly Controls** to editor. This can be toggled only through the shortcut `alt` + `q` as of now. * Added ability to both add and replace users to the Viewer Group type "**Custom List**". * In **Host Mode,** in case the number of participants is large, a few of the names go below the page. Now there’s a scrollbar to help with this. * **Team Members count** is a lot more lenient now in accordance with the latest pricing. * Rules are now **tracked** even for the rule (“**Open URL**” on the same tab). Earlier, because of the page switch, the rule didn’t get tracked ### :bug: Bug Fixes * In the rules "Open Deployment", fixed overflowing content in the open deployment modal to choose deployments from * Fixed API where on renaming deployment name, the new deployment name should not be a part of deployment list * Better WebGL crash messages * The default rule that was part of a new experience crashed viewer. This is now fixed. * Fixed an issue where in certain cases, audio chat didn't work in scenes with long names --- # 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/features/release-notes/2022/12-08-dec-update.md?ask= ``` 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.