> 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/11-12-nov-update.md).

# 11-12 Nov Update

November 2021 Update (Teaxr v0.5.1446)

### :rocket: Major Features

* Viewer
  * Better transparency management and rendering of all elements
* Editor
  * Undo-Redo can be accessed using keyboard shortcuts. The list of all keyboard shortcuts is published [here](https://www.gmetri.com/docs/platform/create/experience/keyboard_shortcuts)

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

* Editor
  * Adding new element when a group element is selected adds it within the same group
  * For all elements that have background\_source, 3d\_model\_source, a new option to remove the selected assets
  * Deprecated text length from viewer form

### :bug: Bug Fixes

* Editor
  * `On End` event added to instructions element. Fires when all stories have finished
  * FOV change shows up correctly in the 360 environment
  * Updates to experience can be viewed correctly in the preview/view links. Experience data/cache gets updated correctly.
  * Correct updates to deployment authentication
* Viewer
  * Fixed billboarding in VR mode
  * Fixed issue with Product card where it doesn't show `3D Model` button


---

# 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/11-12-nov-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.