Include the following details (edit as applicable):
- Platform category: Unity
- Device type & OS version: Android / iOS
- ARDK version: 3.17.0
Description of the issue:
We are building one Lightship VPS experience for a single real-world location, but we need multiple Test Scans of that same site so users can localize from different physical spots.
The problem is that each Test Scan appears to have its own anchor/origin space. Because of that, the same scene does not line up across scans unless we apply a different per-scan translation and rotation at runtime. We are not changing scale.
That creates a problem for production content:
we want one shared scene for the location, but if we have to move/rotate that scene differently depending on which Test Scan localized, baked data like Light Probes and baked occlusion no longer behaves correctly.
Our question is:
what is the recommended Lightship workflow for supporting multiple Test Scans of one physical location while keeping one stable content coordinate system for the scene?