> 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/07-14-july-update.md).

# 07-14 July Update

v0.5.4597 / 14 July 2023

## ✨ Improvements

* 🗣️ New Language options for Text-to-Speech Element and Character element voice options
* 🎯 Trigger Radius default changed to 3M for all new character elements: Enjoy more intuitive and accurate interactions with characters in your experiences
* 🖼️ Improved Embed 3D element performance: Smoother rendering and faster loading times for your 3D models.
* 👤 Improved Avatar Selection for quicker entry into the experience: Jump right into the action with faster access to your chosen experience.
* 🇯🇵 Japanese Language translations for collaboration controls: Seamless navigation and collaboration with Japanese language support.
* 🎭 Better random Avatar names: Embrace a new era of diverse and appropriate Avatar names.

## 🐛 Bug Fixes

* 🔊 Fixed an issue where audio match rule didn’t work after seek to operation: Audio triggers now function correctly after seek operations.
* ⌛ Fixed an issue where timer match rule didn’t work after seek to operation: Timers now operate accurately after seek operations.
* 🔌 Fixed an issue where Agora was loaded even in non-multiplayer deployments, improving loading time.
* 🖼️ Fixed Element renaming issue when selected from structure panel.
* 🧠 Fixed issue with renaming AI Brains.
* 🔍 Fixed issue with rules search when searching by color.


---

# 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/07-14-july-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.