I have a 3D model and I'd like to have to option to attach it to an Image Target OR a Ground Plane. The way I implemented this is by keeping the model as a child of the Image Target, and pressing a button it's parented to the Ground Plane Stage. Pressing the button again brings the model back into the image Target.
It works, but the model is VERY unstable and jittery, sometimes while being parented to the Image Target it behaves like it's in a mid air stage (stays in the same real-world point). I have tried different approaches, even having a copy of the 3D model in both trackables, unregistering targets, nothing seems to work. Am I missing something?
I saw there is a lengthy discussion about a similar problem and it looks like Image Target and Ground Plane don't work well together out-of-the-box, while I had no problems making them work independently (i.e. a scene with only Image Targets or only one Ground Plane)
I'm using Unity 2019.2.5f1 and 2019.2.9f1, this happens in-editor on Windows 7 and the last Mac OS using the webcam and on an iPad Air 2 (no ARKit), haven't tested on other devices.
Hi,
I determined the behavior to be related to the Extended Tracking.
Scenario1: ImageTargets and GroundPlane in different scenes
Extended tracking is only activated on the GroundPlance scene. Hence you do not see the mentioned the behavior in the Image Target scene.
Scenario2: ImageTargets and GroundPlane in the same scenes
Extended tracking is activated as soon as you start the scene and you see the jittery behavior
I've also brought the behavior internally to the Dev team and they mentioned that in the Extended Tracked scene you get to see the last pose of augmentation, in comparison to the Image Target scene where when the tracking is lost, the augmentation disappears.
To address this issue I found two workarounds:
1. Split the scene in two, you already tested this and it works as expected
2. In 8.6.7 we now have the possibility to render content based on the Trackable result. This means that the Image Target can be confirmed to render the augmentation based on the status Tracked and not on Extended_Tracked. Ignoring the Extended Tracking which in this case should resolve the behavior faced. More info, here: https://library.vuforia.com/content/vuforia-library/en/articles/Solution/How-To-Use-the-Trackable-Base-Class.html
and Release notes: https://library.vuforia.com/articles/Release_Notes/Vuforia-SDK-Release-Notes
Thank you.
Vuforia Engine Support