Options For Connecting Two Or More Magic Leap 2 Devices Locally

General
1

Hello Magic Leap Support Team,

Since the AR Cloud was deprecated in January, what are some alternatives to connecting two or more Magic Leap 2 headsets and viewing/interacting with spatial content within the same environment?

2

You could use Figmin XR:

https://overlaymr.com/get-figmin/

3

Awesome, thank you. I will check this website out. Has Figmin XR worked well for you?

4

Absolutely. It’s the app I use most often.

Also works cross platform — between Magic Leap 2 and Oculus headset.

5

If you are interested in creating a custom solution, you could use the Localization Map and Spatial Anchor Storage APIs. Note: the network communication would still need to be done through a service like Unity’s Net Code , Photon or Mirror.

Here is what the flow would generally look like:

  1. On one of the headsets you would need to scan the space with the Spaces app.
  2. Inside your application you would make sure that the device is localized into the correct space.

3. You can then place Spatial anchors or use the Map Origin as a shared reference point.
4. You would need to implement a network layer (UDP or Photon or Mirror or Unity Netcode) to send the data between the headsets
5. If a device joins it can check if the host is localized into a space. If the host is localized the app could check if the same Space exists on the device

6. If the Space exists you would localize into it and use an anchor or map origin as the shared reference point. If the Space does not exist then you can use the Export and Import functions
i . Export the Space on the host device
ii. Use your network layer to transfer the zip file to the connected device
iii. Import the Space once the zip file is received.

6

Thank you for this suggestion! We will take a look into this app.

7

Great suggestion! Thank you for providing this direction.

8

So we can use the ‘spaces app’ to map the space, correct? Mapping the space every-time they want to connect headsets, is not a good solution. That takes time for our use case. But, if the space is already mapped, if they use indoors, that they mapped already - then the solution of connecting ML2 would be a solid option for us. Would users have to map the same space over again, each time they wanted to connect headsets?