> 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.10.0.md).

# Version 1.10.0

On-device localization for iOS, multi object tracking in one session, MapSet alignment in Unity, Faro scanner support, query analytics.

### v1.10.0 08-December-2025

**Added**

1. Introducing OnDevice Localization for iOS: <https://docs.multiset.ai/unity-sdk/on-device-localization>
2. ModelSet Tracking now supports tracking multiple objects in the same session: <https://docs.multiset.ai/unity-sdk/sample-scenes/modelset-tracking#modelset-tracking>
3. MapSet alignment feature in Unity SDK: <https://docs.multiset.ai/unity-sdk/sample-scenes/mapset-alignment>
4. Simulation data capture sample scene in Unity SDK: <https://docs.multiset.ai/unity-sdk/localization-simulation#build-a-simulation-data-capture-app>
5. Added Faro scanner support for VPS using the E57 export: <https://docs.multiset.ai/basics/third-party-scans/faro-scans>
6. Developer Portal now shows query analytics for maps and model sets.
7. Ability to Archive Individual Maps and Maps that are part of a MapSet

**Fixed**

1. Localization performance improvement for Maps, Mapset and ModelSet
2. Confidence values in the VPS multi-frame query API response
3. Confidence check bug with the Single Frame Localization script in Unity SDK
4. Memory management while checking for blurred images in Unity SDK


---

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