> 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/v2/version-2.0.0.md).

# Version 2.0.0

MultiSet VPS Gen2 for higher recall in repetitive spaces, indoor and outdoor modes for 360 to VPS, geometric and high fidelity splat outputs.

### v2.0.0 4-June-2026

**Added**

1. **MultiSet VPS Gen2** is now live on all maps and objects created after 3 June 2026. Gen2 brings a higher recall rate in repetitive areas like train stations, basements, and corridors. Existing maps can be upgraded to Gen2 from the Developer Portal.
2. Improvements to the 360-to-VPS pipeline.
3. Gen2 also improves the recall rate for Object Tracking.
4. **Indoor and outdoor modes for 360-to-VPS.** 360 video processing now optimises the scene according to the environment. [Insta360 Scans](/fundamentals/third-party-scans/360-videos/insta360-scans.md)
5. **Geometric and high-fidelity splat outputs.** 360-to-VPS now produces both a geometric and a high-fidelity version of the splat.

**Fixed**

1. Unity SDK: added the missing **hintFloorHeight** property. [HintFloorHeight](/fundamentals/localization/hint-floor-height.md)
2. Fixed the MapSet map version update issue. [Map Versioning](/fundamentals/map-versioning.md)


---

# 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/v2/version-2.0.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.