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

# Version 2.4.0

Mobile mapping on devices without LiDAR, so any ARKit or ARCore phone can build a map, a shareable version viewer to compare scans over time, and faster, more reliable E57 and MatterPak processing.

### v2.4.0 08-October-2026

**Added**

1. **Mobile mapping without LiDAR.** Maps can now be built from a capture recorded on a phone or tablet with no LiDAR sensor, so mapping works on every ARKit iPhone and iPad and every ARCore Android device. Upload the RGB frames, their poses and the camera intrinsics as a `PosedRGB` capture: no depth images and no mesh are needed. [Mobile Map Upload](/fundamentals/rest-api-docs/map-upload/mobile-map-upload.md)
2. **Share a version viewer.** A share link can now open a viewer that compares the scans in a [Map Version](/fundamentals/map-versioning.md), so anyone with the link can see how a space changed between two scans captured at different times. [Sharing Maps](/fundamentals/sharing-maps.md)

**Improved**

1. **Faster E57 processing.** `.e57` scans now process faster. [Third Party Scans](/fundamentals/third-party-scans.md)

**Fixed**

1. **MatterPak and E57 processing.** Fixes to processing of MatterPak and `.e57` uploads. [Matterport E57](/fundamentals/third-party-scans/matterport-e57.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.4.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.