Shared Spatial Anchors Sample

1. Click Create New App under your developer organization.
2. Enter a name for your app.
3. Choose Meta Horizon Store.
4. From the left navigation, go to Requirements > Data Use Checkup,
5. Complete Age group self-certification before requesting access to User ID and User Profile platform features.
6. From the left navigation, go to Development > API. Ensure you’ve selected an app, and then note the number under App ID.

1. Enter the Quest App ID from above in the Meta Quest/2/Pro field.
2. To test with Link, enable Use Standalone Platform and Use Meta Quest App ID over Rift App ID in Editor, then enter your test user’s credentials.
3. Under Build Settings, replace the Bundle Identifier with a valid and unique Android package name, like com.yourcompany.ssa_sample. Your app’s anchors will be associated with this package name.

1. Create an account on Photon⁠.
2. On the Dashboard page, follow the prompt to create a new app.
   • Select Photon SDK: set to Realtime. The sample setup warns against selecting PUN because of a known dashboard issue; the Unity project still uses PUN2.
   • Name and Description: can be set to anything.
   • URL: can be left blank.
3. Add the Photon app ID to the App Id Pun entry in the PhotonServerSettings file under Assets/Photon/PhotonUnityNetworking/Resources/. You can find the PhotonServerSettings from the menu at Window > Photon Unity Networking > Highlight Server Settings.

• Tracking Origin Type: STAGE
  • The STAGE tracking origin type will ensure that virtual objects do not move when a re-center event occurs.
• Anchor Support: Enabled
• Shared Spatial Anchor Support: Required or Supported
  • The sample app uses Supported because it includes local anchor functionality.

• <uses-permission android:name=”com.oculus.permission.USE_ANCHOR_API” />
• <uses-permission android:name=”com.oculus.permission.IMPORT_EXPORT_IOT_MAP_DATA” />
• <uses-feature android:name=”com.oculus.feature.PASSTHROUGH” android:required=”true” />

• Toggle Anchor Creator: Toggles anchor creation mode. When enabled, an anchor preview is visible on your right hand. Upon pressing the trigger, you can place a new Spatial Anchor into the scene.
• Load Local Anchors: Downloads and instantiates any anchors that are saved to the headset.
• Spawn Networked Cube: Spawns a cube just above the menu. The cube is visible and grabbable by all players in the room. Grabbing the cube transfers network ownership to the player that grabs it.
• Photon Info Panel: Shows the photon room that the player has connected to, the current connection status, and a list of users in the room.
• Logging Panel: The right half of the menu is used for logging (for debug purposes). You can press the arrow buttons on the bottom right to navigate multiple pages of logs.

• Save Anchor Locally: Saves the anchor to your local headset. Load the anchor by selecting the Load Local Anchors option from the control panel.
• Hide Anchor: Deletes the anchor from the scene, but remains saved in your local headset storage if you saved it. You can respawn it by selecting the Load Local Anchors option on the control panel.
• Erase Anchor: Deletes the anchor from the scene and erases the saved file in local storage. You’ll no longer be able to load the anchor.
• Share Anchor: Shares the anchor with all other users that are connected to the room and any new users that join the room.
• Align to Anchor: Realigns your headset’s coordinate system to be based on this anchor transform. This enables co-location when multiple users align to the same Shared Anchor. You’ll notice the networked cube appears in the same position for all users.

• Assets/Scenes/Menu.unity: Select a sharing workflow and manage local sample data.
• Assets/Scenes/SharedSpatialAnchors.unity: Share anchors to users using Photon PUN2 to exchange user IDs and anchor UUIDs. Align peers with MRUK world locking and synchronize networked cubes.
• Assets/Scenes/ColocationSessionGroups.unity: Advertise or discover nearby sessions with OVRColocationSession, share and load anchors by group UUID, and align peers without Photon. An arbitrary group UUID can also be used to test group sharing without discovery.

• MRUK world locking: In the user-sharing scene, the host exchanges the anchor’s original pose through Photon. Clients use MRUK.Instance.SetCustomWorldLockAnchor to align to that reference.
• Classic tracking-space alignment: In the group-sharing scene, Alignment.SetOrigin adjusts the camera rig’s tracking space relative to the shared anchor. It can also reposition existing non-anchored objects to preserve their placement during alignment.