> 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/10-04-oct-update.md). # 10-04 Oct Update v0.5.5015 / 4 Oct 2023 ## 🚂 Editor Upgrade: V4 to V6 We released the v5 editor in November 2021 and introduced v6 in August 2023. Both of these releases marked major upgrades in terms of the underlying technology and the way we store GMetri projects. During the transition from v4 to v5, we did not automatically update older projects. Instead, we have continued to support the older v4 format in legacy mode for approximately two years. Throughout this time, GMetri's feature set has expanded significantly. We are planning to decommission the v4 editor in the near future. Fortunately, this change will not impact your deployments. This is because, for an extended period, v4 projects have been viewed using the latest viewer. In the viewer we update v4 projects on the fly to the latest version (to v6), without saving them back, to ensure that you can still use the v4 editor, while getting the benefits of our latest viewer. However please be aware that before the next release, when you access older projects, you will start seeing the new editor instead of the older v4 editor. ## ✨ Improvements * Unfocused windows no longer cause audio events to not fire * Updated supported browser versions: ## 🐛 Bug Fixes * Fixed orientation issues with VR mode * Fixed Point To action in VR mode * Fixed variable templating for Embed 3D element --- # 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/10-04-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.