> For the complete documentation index, see [llms.txt](https://docs.multiset.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multiset.ai/quick-access/changelog/v1/version-1.9.3.md).

# Version 1.9.3

Xgrids scanner support through E57 export, mapped area analytics, better mesh generation for E57 imports.

### v1.9.3 16-November-2025

**Added**

1. Added Xgrids scanner support for VPS using the E57 export: <https://docs.multiset.ai/basics/third-party-scans/xgrids-scans>
2. Map analytics now shows the total mapped area in sq ft.

**Fixed**

1. Unity SDK: Mapping Scene upload issue is fixed.
2. Mesh generation improvement for E57 scans imports.
3. Updated glTF and draco packages for Android 16 KB support.
4. Developer Portal: Mesh visualization optimization for loading large Maps/MapSets.
5. MapSet manual alignment transform update was resolved.
6. MultiSet App UI is optimized for iPad.


---

# 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.multiset.ai/quick-access/changelog/v1/version-1.9.3.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.