> 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/05-16-may-update.md).

# 05-16 May Update

v0.5.4293 / 16 May 2023

## 🚀 Major Features

* [Broadcast mode](/metaverse/multiplayer/broadcast-mode.md) for deployments that allow broadcasters to send audio stream and be visible in all rooms instances.
* [Linked Popups](/metaverse/build/elements/linked-popups.md) - Image and video elements can be linked to popups that opens when the element is clicked

## ⏫ Minor Improvements

* Changed defaults for new experiences. Default scene - 3D scene, default camera controls - 3rd Person
* On duration matches rule for Audio Element

## 🐛 Bug Fixes

* Fixed keyboard shortcuts when using chat and comments
* Fixed Comments for 3D Scenes
* Fixed scaling issue for character element between editor and viewer
* Fixed popup rendering issue for older experiences
* Fixed name templating in emails
* Fixed editor crash when user name doesn’t exist


---

# 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/05-16-may-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.