Skip to main content
Oloap92
Inspiring
May 23, 2025

OVR Spatial Anchor Network connection and space location question

  • May 23, 2025
  • 2 replies
  • 459 views
I am developing an app that uses Meta's spatial anchor features.
I deployed the app on two different headsets and noticed that, if the headsets are on different network connections, the Spatial Anchor API does not work well: specifically, it returns an error (-1006 or -1001) when loading shared anchors.
 
Do the headsets have to be on the same network and/or close to each other?
 
Thanks for any help.
    This topic has been closed for replies.

    2 replies

    JeffNik
    JeffNik
    Honored Contributor
    May 23, 2025

    In the documentation for shared spatial anchors, I recall seeing that sharing an anchor requires the headsets to be on the same local network. In your situation, are the multiple network connections on the same LAN? If not, that may be your issue. For example, I have a dedicated router for wireless Link gaming. My Q3 uses that connection, and my QPro connects to my standard router... two different connections to the same LAN, and I can share anchors in my testing.  But if I was to connect my Q3 to the internet directly through my cell tower internet provider router (which is not on my LAN) - it doesn't work.

    Oloap92Author
    Inspiring
    May 26, 2025

    Hi, thanks for replying.
    I had some tests with two headsets on same and different networks, and it seems to confirm what you say.
    I am wondering if the colocation system uses also the gps data to figure out it or only the network's ones.

    Terms & ConditionsAccessibility statement