> 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/features/release-notes/2023/03-10-mar-update.md).

# 03-10 Mar Update

v0.5.3959 / 10 Mar 2023

## 🚀 Major Features

* ReadyPlayerMe Integration for [Avatar](/metaverse/player/avatars.md) System

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FfIDeDSmPVxQ1oMVFgjzQ%2Fspaces_-Mgll1jjQMRTVj7p6n7g_uploads_HMlIJ9rnPmSdB6nIOlBK_image.webp?alt=media&amp;token=17376fe2-fc2f-4acd-bb74-dfc1df8499d7" alt=""><figcaption><p>Avatar Selection</p></figcaption></figure>

* A new [Character element](/metaverse/build/elements/character.md) and ReadyPlayerMe Plugin for Filemanager. Characters can be imported from ReadyPlayerMe.

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FztPAqJdVuCprY6pruTCY%2Fimage.png?alt=media&amp;token=7200f74c-507f-4f33-b0ba-8d239f555743" alt=""><figcaption><p>Character Plugin</p></figcaption></figure>

* Viewer Camera Mode - First Person/Third Person for 3D Scenes. Use [keyboard shortcuts](/metaverse/player/viewer-keyboard-shortcuts.md) to switch between the two.
* Branding feature consolidation - [Custom Loader](/metaverse/build/editor/project-settings/branding.md#custom-loader) is now a Professional tier feature, whereas [Remove Splash Screen](/metaverse/build/editor/project-settings/branding.md#remove-splash-screen) and [Remove 'Powered by GMetri' watermark](/metaverse/build/editor/project-settings/branding.md#remove-powered-by-gmetri-watermark) are Enterprise tier features.
* There is no longer a Starter Plan. Check available plans here:[Billing](/platform/billing.md#plans). Older customers who are already on the Starter Plan can continue to remain there.

## ⏫ Minor Improvements

* Preview URLs now start with “preview\.gmetri.com/…”
* On headset, a persistent overlay is visible to enter into Immersive mode
* Actionbar UI improvements
* Streamlined UI for menu, hamburger menu on top-right of the page uses only the required amount of space
* Rotation controls for Meta Quest controllers using the left thumbstick
* Button B interactivity for Meta Quest controllers
* Token expiry screen when viewer token expires

## 🐛 Bug Fixes

* Avatar heights are in sync between non-immersive and immersive modes
* Sideways running issue in 3D scenes in 3rd person view is fixed
* WASD keypress on properties/structure doesn’t trigger movement of the user
* Toast notifications are shown for all operations correctly
* Typo fixes for branding section
* Fixed lighting issue with 3D models
* Avatar Rotation in 3rd person mode
* Resolved UI issues with screenshare element
* Is In List rule for number variable
* Fixed issues in Comment Pins


---

# 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/features/release-notes/2023/03-10-mar-update.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.
