Relocalizing ARKit scene using ARFoundation after backgrounding

I’m pulling my hair out and can’t figure out how to properly relocalize an ARKit scene after backgrounding an app. I can’t figure out where or how to set the ARFoundation equivalent to Apple’s sessionShouldAttemptRelocalization. Instead, I’ve enabled ARKitCoachingOverlay which does indeed come up when you switch back to the application asking you to move around. If you’re pointing at the same area it usually seems to work but if you’re pointed somewhere else it doesn’t ask you to return to the previous area as Apple’s docs (https://developer.apple.com/documentation/arkit/arcoachingoverlayview) seem to indicate it should. Again maybe because we can’t set sessionShouldAttemptRelocalization first?

In testing it always seems to return trackingState of “initializing” instead of “relocalizing” before moving to “tracking” so I don’t even know how to differentiate or capture this condition. It also doesn’t bring up the Start Over button to allow the user to reset tracking if it gets lost. Further, I don’t see any ARFoundation equivalents of coachingOverlayViewDidRequestSessionReset to allow us to intercept that even if the button did show up.

So someone please help me understand the best practice to handle relocalization for ARKit using ARFoundation. Am I missing something or is Unity missing functionality for all this in ARFoundation?

Many thanks.

 

Bump. Anyone?

 

Bump

 

Waiting for this feature since ARFoundation 1.0 , I think it's missing. It used to be in the UnityARKitPlugin from bitbucket

 

Looking for this as well

 

@todds_unity the issue is that notTrackingReason is never Relocalizing, perhaps due to the
sessionShouldAttemptRelocalization option apparently missing
https://developer.apple.com/documen...rver/2941046-sessionshouldattemptrelocalizati

So users cannot be directed to relocalize using the coaching overlay or other means. The session will just reinitialize automatically if not recovered within a few seconds.

 

Has anyone found any solution to this yet? Without this feature it is very difficult to create relocalization experiences as the code has no way of knowing if relocalization was in fact successful.