Problem with SharedSpace and Colocation

Yes for proper Shared Spatial Anchor / colocation testing, you realistically need two physical Quest devices to make sure that everything works in your physical space.

The Unity XR Simulator does not fully emulate everything, but works for development good enough though.

Also, your original issue (objects appearing in different locations) is exactly what SSA/colocation is meant to solve. Right now both users probably have different local tracking origins. Remember to always recenter the headsets when you launch the application.

A few important notes:

• Both headsets must map the SAME physical space
• Use the same shared anchor UUIDs across clients
• Wait until anchors are fully localized before spawning networked content

Common mistake:

• Networking object transforms before world alignment is complete

Recommended flow:

1. Create/share/load anchor
2. Localize anchor on both devices
3. Align world origin
4. THEN spawn synchronized objects

Without that order, Photon transforms will still mismatch spatially.

I was using Unity XR Simulator + Device with build to test the Shared Spatial Anchor and Colocation, i was hoping that the room i had scanned in my device would appear in the XR simulator when i enter the room but it dont seem to be working, i was presuming that it was because i was testing Simulator x Device because looking at the immersive console everything works fine in the device but not in the simulator.