> 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/2022/10-14-oct-update.md). # 10-14 Oct Update v0.5.3231 / 14 Oct 2022 ### :rocket: Major Features * **PBR materials** are now supported in 3D Models * New name bubble design over Avatars * Restructured **Branding section.** ### :arrow\_double\_up: Minor Improvements * New deployments are **Live** by default * There are new auto-generated variable for tracking the viewer's last name and full name * Users are hidden when they enter the spawn zone ### :bug: Bug Fixes * Preventing access to the editor without a valid uuid * Fixed inconsistency with durations on the Deployment Analytics page * Fixed styling issues on Analytics page * Fixed clickability issues with Colliders * Viewer name gets computed correctly for CustomList login * Fixed movement when typing inside chatbox * Fixed the avatar selection screen * Fixed OEmbed URL expansion when using an alias for workspace name * Editor blocked on unsupported browsers --- # 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/2022/10-14-oct-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.