I plan to do another test with this location and Lightship/Unity but I haven’t had a chance yet. This morning, however, I tried a simple, 8th wall VPS and it wasn’t stable at all. The public location is on the coast and it was a clear morning. I used my Pixel 6 to view it. What am I doing wrong? I plan to set up a similar project with Lightship and compare using the same phone. In the mean time, here are this morning’s disappointing results.
I tried a few times and it didn’t get any better. Doesn’t matter if I stand still the whole time. Sometimes the scene would just fly off on it’s own and not come back at all.
The further you move back, the less feature points there are to track. Obviously the scale looks incorrect, have you been able to test with any other devices?
You may also consider using VPS to localize the first time and then let world tracking take over (i.e. only use the first locationfound event to place to the plane, don’t continuously try to track the location). You may also consider placing the plane in front of the statue to avoid the poor occlusion.
@Evan can you please explain this logic here: VPS to localize the first time and then let world tracking take over. If i understand this correctly, the VPS mesh with GPS coordinated will be used to localize Item 1 and once that is done subsequent items (2,3 and 4) can be anchored in the scene relative to the first item or does it still use computer vision to identify mesh elements and place items how they were placed in the viewport? Based on your suggestion, does that mean even if tracking is lost we will still have elements within the scene? Is this achievable in Studio?
The way VPS works is by matching live camera frames to a pre-scanned mesh. When the system is confident it’s found the location, any children of the location node in Studio will appear and track to it. If tracking is lost (e.g. the user turns away), content will disappear until it re-localizes.
For more stable experiences, many developers only use VPS for initial placement. After the first locationfound event, they switch to world tracking and stop re-localizing. This avoids content “disappearing,” though it can introduce some drift over time—acceptable for many use cases where perfect accuracy isn’t critical.
Another approach: allow relocalization but disable the hiding behavior so content stays visible even when tracking is lost. This gives users a chance to regain tracking without disrupting the experience.
