Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Unity 2018.3 is now released.
    Dismiss Notice
  6. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

localized and non-localized maps for better tracking results

Discussion in 'ARCore' started by areavisuale, Jul 6, 2018.

  1. areavisuale

    areavisuale

    Joined:
    Jul 23, 2015
    Posts:
    28
    I'm trying to create a scene using ArCore where I instantiate a gameobject when the app starts tracking, and I would like that, after the tracking is lost and resumed, my gameobject remains in the position it was before tracking was lost.

    Positioning my gameobject at the first tracking (using this code: Pose firstpose = m_AllPlanes[0].CenterPose results in an undesiderable behavior, because probably the first tracked plane isn't so much stable.
    I read in this page: https://github.com/google-ar/arcore-unity-sdk/issues/37 that ArCore has "Localized" and "non-localized" maps, and in the first case the gameobject remain always in position also after tracking is lost and resumed; this can be seen in the HelloAr scene, where some instantiated Droids disappear and some remain after tracking lost and resumed.

    Do you know how to understand when the tracking is stable and the created maps are "localized" so I can Instantiate my gameobject only in that case?
    Thanks