Question Best Practices for reducing jitters with mars

Hi, I'm using mars for some very simple image target recognition that spawns an overlay onto the image target. My issue is that as I move the phone around my overlay does not stay attached to the image target. It seems to float and jitter constantly which creates a clunky experience. Normally in AR, this issue is solved by creating an anchor when instantiating the overlay that you never want to move from it's current position.

I'm trying to understand how this can be done within MARS as I assumed image target proxies might create an anchor under the hood but the results I'm seeing, this does not appear to be the case.

I have double checked the dimensions of the image target as each spot it is referenced and everything is correct.

Is there anything else I should consider adding via Mars or will I need to call some ARcore/Arkit functions myself? Given this is a common AR problem that has existed since 2016 I assume there is a solution for it within MARS and that is why I created this post, to better understand how to use and think with MARS instead of AR foundation or native API's.

Thanks.

 

I am currently working on Android.

 

submitted with a video and explanation/walkthrough which I believe will be much more helpful to you than the project.

 

I have the same issue , and I find that if you preset the gameobject under the Image Tracker , it can follow as perfect , if you spawn in runtime , I will have a terrible drifting and jitter

https://drive.google.com/file/d/1aD-is8AeJnWuZxD5Gm0aJD0KGVeqZYIU/view?usp=sharing

here are the video to help , the cube is pre-create at the scene and the plane with grid is create afterward and attach to the Image Tracker.In debug log , their position unchange.
I don't know is that the reason or the bug is , I have already struggle for that few month .