> 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/09-11-sep-update.md).
# 09-11 Sep Update
v0.5.4972 / 11 Sep 2023
## 🚀 Major Features
* Updated UX for Avatar Selection
* New reactions for Players\
* Introducing a new Brain type: Role Play (can hold conversations given a personality)
## ✨ Improvements
* Shortcut for deleting elements updated from Ctrl + Delete / Cmd + Delete to Delete
* Introducing 10 new talk animations for characters
* Performance Monitor to calculate Videos, Audios and GIFs overhead
* Improvements in Brain selection UI
* Introducing optimized scene transition type for 360 to 360 scene
* Adding Preset avatars for RPM Avatar system for easier and faster access
* Adding gendered animations for custom avatar system
## 🐛 Bug Fixes
* General optimisations to reduce RAM usage
* Fixed Copy and Paste for elements
* Fixed Experience renaming
* Popup showing slides in sorted order now
---
# 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/09-11-sep-update.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.
