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

# 11-26 Nov Update

November 2021 Update (Teaxr v0.5.1524)

### :bug: Bug Fixes

* Editor
  * New scenes will automatically get added to the menu
  * QRMatcher rules show correct entries in rules
  * Directional light impacts all 3D models correctly
  * Timer position shows correctly in editor and viewer
  * Green screen effect on videos
  * Fixed issue with viewer form not working when there all entries are deleted
  * Fixed issue inconsistent menu entries when scenes are deleted
  * Geolocation can now be used from the deployment section
  * Linked variables with media upload are shown correctly in the “Autogenerated” variables section
* Viewer
  * Multiple fonts for text elements can be used on iOS devices
  * Fixed fluctuations on mobile devices when using scene range locks
  * Instructions element skips entries that don’t have any asset selected
  * Removed viewer state save calls for preview mode
  * Large viewer state updates now allowed
* Portal
  * Deprecated editor login
  * Fixed Azure login


---

# 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-26-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.