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

# Version 1.9.0

### v1.9.0 12-September-2025

**Added**

1. Mapping scene in Unity SDK for integrating scanning capabilities into phones with LiDAR support. <https://docs.multiset.ai/unity-sdk/sample-scenes/mapping>
2. Continuous localization until success for the first attempt in a session has been added
3. MultiSet Mobile App UI overhaul with the ability to upload .glb objects for object tracking.
4. Navigation scene added in Meta Quest SDK: <https://docs.multiset.ai/multiset-quest-sdk/sample-scenes/navigation>

**Fixed**

1. Improved localization response time in Meta Quest SDK.
2. ModelSet object tracking improvements for smaller objects
3. WebXR SDK can handle localization in both portrait and landscape mode <https://github.com/MultiSet-AI/multiset-webxr-sdk>
4. 3D viewer launch orientation while rendering large scans on the developer portal is improved.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://multiset.gitbook.io/multiset/quick-access/changelog/version-1.9.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.