> 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-9-nov-update.md).

# 11-09 Nov Update

November 2021 Update (Teaxr v0.5.1426)

### :rocket: Major Features

* Viewer
  * Shopping element and product card redesign

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

* Editor
  * Toaster is shown on all updates in the publish section
  * Rightbar panel design updates
  * On adding new section in popup, all previous sections auto collapse
  * Add red bounding box even when elements are locked
* Viewer
  * Deprecated: Scene pitch correction. All scene pitch correction in scene gets converted into point to rules automatically.

### :bug: Bug Fixes

* Editor
  * Reset view not working in orbit mode fixed
  * Dragging in Orbit mode fixed
  * Changed all docs links on portal and editor
  * Action bar rules’ 3rd element inconsistency when updated from v4 to v5 fixed
  * Project property defaults shown correctly
* Viewer
  * Pitch range min value not working fixed
  * Product card, quiz position fixes
* 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/11-9-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.