Question Proxy Objects moving around

Hi there! The behavior you are seeing is somewhat by design. MARS tries to continuously update your proxy matches based on the conditions you have defined, and find you a better match as new data comes in. There are a couple of approaches for controlling this behavior.

• Use synthetic data
  • If you instantiate a new Synthetic Object with a Synthesized Tag and a Synthesized Pose, you can create a Proxy to match that tag, and then you have control over the location and lifecycle of that synthetic data. In this case, you'd have a proxy or replicator matching the planes you are looking for, with a script on it to instantiate the synthetic object (from a prefab or using AddComponent) on match. Then you'd have a second proxy with a semantic tag condition looking to match the tag of the Synthetic object.
• Stop plane finding
  • If you get to a "good" point where all your proxies match, or determined by user input (a "done scanning" button or something), you can just stop updating planes. `IUsesPlaneFinding` exposes a `StopDetectingPlanes` method that you can use for this.
• Set the evaluation mode to `WaitForRequest`
  • You can implement the `IUsesMarsSceneEvaluation` interface to get access to `SetEvaluationMode` and set it to `WaitForRequest`. In this mode, MARS will only update queries (and therefore proxy locations) when you call `RequestSceneEvaluation`.
• Pause MARS
  • This will temporarily halt the MARS solver and other MARS behaviors like plane and point cloud visualizers while still allowing AR subsystems to function. Simply set `MARSCore.instance.paused` to true.

Hope this helps!

 

Can you share your project/scene? This does sound like the expected behavior: MARS evaluates the best match for all of your proxies on a fixed interval. The bit about a lot of objects in one place seems wrong, but it may just be a matter of choosing `Reserved` data exclusivity for one or more of these proxies.. It would help for us to see exactly how you have things set up so that we can recommend a fix.

Also, it does sound like what you want is the `WaitForRequest` evaluation mode. That way you can have your app wait until scanning is complete, and then request an evaluation for all of the content to lay itself out one time. Something else you can try is to use the Compare Tool to figure out why your proxies are matching to one surface vs. another.