ARKit Anchor Image tracking - slow updates when marker is moving

Hi,

I was following this tutorial https://blogs.unity3d.com/2018/02/16/developing-for-arkit-1-5-update-using-unity-arkit-plugin/ and I manage to track a marker image and display the AxesPrefab on top of it. The marker is tracked very well when the marker is not moving, but the update of the axes is very slow when the marker is moving (maybe around 1 Hz?). Was wondering if this is the normal/expected behaviour or I have to do some changes in my scene?

Thanks!

 

As explained in the docs and blog, the image is not tracked, just recognized. So that is expected behavior.

 

Thanks! Right, but isnt the recognition script running at quite a fast speed so that the recognition and augmentation steps would be running and appearing smooth in the screen? Through the docs I could not understand the reason why this recognition and display would be this slow (it refreshes around every second). Could you point me to the docs explaining that?

I thought this could be because of if you move the marker that a new anchor is created and this takes time, but while debugging I saw that the script of adding a new anchor is not called.

Thanks!

 

if you think about it, once you recognize a static image in AR you don't have to track it, because AR is already tracking the world, so it'll stay 1:1.

 

Hi @vTimePawel, not sure I understood what you mean. In my case the marker is not static and is moving, so the marker has to be recognized continuously

 

https://developer.apple.com/documentation/arkit/recognizing_images_in_an_ar_experience?language=objc
"ARKit doesn’t track changes to the position or orientation of each detected image"

 

Thanks, missed that. And this is not possible to change? So is it that it only analyzes the image at around 1 second rates?

Any suggestions how to go about tracking dynamic objects and displaying AR content relative to them at faster rates?

Thanks!

 

@jimmya @jose-araujo the docs are pretty confusing as they relate to the actual behavior. I was expecting the images to *not* update, but rather they *do* update - just slowly.