> 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/2021/10-26-oct-update.md).

# 10-26 Oct Update

October 2021 Update (Teaxr v0.5.1379)

### :rocket: Major Features

* Viewer
  * VR mode supports Point to action
  * VR mode supports animations during scene transitions
  * VR mode supports scene offset rotations

### :arrow\_double\_up: Minor Improvements

* Editor
  * Deprecated: Height from text elements
  * Deprecated: width/height/depth from cylinder
  * Improved updates from number/decimal properties
* Viewer
  * Deprecated: Scene pitch correction. All scene pitch correction in scene gets converted into point to rules automatically.

### :bug: Bug Fixes

* Editor
  * Gracefully handling all resource failures to remove any unwanted crashes
  * Fixed errors while adding new text elements
  * Updates to experience can be viewed correctly in the preview/view links. Experience data/cache gets updated correctly.
  * Correct updates to deployment authentication
* Viewer
  * Disallow rotation using mouse scroll when gyro lock is enabled in a scene
  * Fixed text input in comments to clear text on submit and prevent text clipping
* Portal
  * Fixed new project creation flow.


---

# 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/2021/10-26-oct-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.