> 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/12-18-dec-update.md). # 12-18 Dec Update v0.5.5142 / 18 Dec 2023 ## 🚀 Major Features * UI to show historical conversation with the Character Element * Support for KTX2 compressed 3D models * Minimap element (beta) ## ✨ Improvements * Stricter restrictions on File Uploads * Support for controlling Avatar quality * Product card - checkbox for enabling share button * Support for controlling Avatar quality * Product card - on clicking share button copies a link to the clipboard and shows notification * Product card - when a shared link is loaded, the product card appears. ## 🐛 Bug Fixes * Reduced poly count for zone element * Fixed idle and talking animations for Character element * Fixed PDF Viewer for Popup element * Fixed render order issue for Zone element * Fixed styling issue for Instruction element * Fixed movement controls when shift key is pressed before WASD * Fixed editor sluggishness when using arrow or wasd keys to move around --- # 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/12-18-dec-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.