Log in or register to post comments

Device/Positional Tracking

November 8, 2018 - 7:47am #1

Hi guys,

Bit of an issue regarding device/positional/extended tracking:

Unity 2018.2.14f1

Vuforia version 7.5.26

Samsung Galaxy S3 Tablet (T-825)

Extended tracking seems to be sporadic at best, non-existent mostly. I've enabled device positional tracking, the vumarks are of ok quality and camera device mode is OPTIMIZED_QUALITY, camera_continuous_autofocus enabled for AR camera.. I've dropped the number of tracked images to one(necessary for vumarks?)

Note: It works fine on both my S9 and an S7, but I've no other tablets to test it on.

What could I be missing? Or could this be a bug or known issue witht he S3 tablets?

Device/Positional Tracking

November 14, 2018 - 9:52am #4

Hello,

gcampbell90 wrote:

Nothing seemed to make it work, I've tried some troubleshooting and found that only the image targets are allowing for extended/positional tracking after the image has been lost.

I am sure I have had it working with the vumark on a separate android device but suddenly its extended tracking would not work either. 

To the SDK, there is little difference to how a VuMark is handled during tracking compared to an Image Target. Thus, I find it very surprising that Extended Tracking works for one but not the other.

Can you better explain how you've qualified/quantified that Extended Tracking is not working for VuMarks? Also, is this observation valid for both device tracking and our legacy SLAM implementation?

What would be most helpful is if you can provide the VuMark device database and some printable instances. This way I could attempt to replicate your findings.

Thanks,

Vuforia Engine Support

Device/Positional Tracking

November 14, 2018 - 6:33am #3

Thanks for the reply,

Nothing seemed to make it work, I've tried some troubleshooting and found that only the image targets are allowing for extended/positional tracking after the image has been lost.

I am sure I have had it working with the vumark on a separate android device but suddenly its extended tracking would not work either. 

I have found that setting up my vumark as an image target does indeed give me extended tracking, then essentially implementing the vumarks aswell to act as triggers, as I can retrieve the id code the functions around which id is currently on screen. 

This seems like a very silly bug, why does the tracking suddenly cease for the vumarks and not the image targets?

Since I'm strictly only working with 3 different vumarks, I should just replace the vumarks with separate image targets instead of the method I described above but it had me stuck for days thinking it was a design/unity error.

Thanks for your help but can you confirm if this is a well known issue that vumarks cant be used for ET? Or at least behave differently than image targets?

Device/Positional Tracking

November 12, 2018 - 2:58pm #2

Hello,

gcampbell90 wrote:

Bit of an issue regarding device/positional/extended tracking:

Samsung Galaxy S3 Tablet (T-825)

Extended tracking seems to be sporadic at best, non-existent mostly. I've enabled device positional tracking, the vumarks are of ok quality and camera device mode is OPTIMIZED_QUALITY, camera_continuous_autofocus enabled for AR camera.

I suggest you evaluate the performance when setting the Fusion mode to FUSION_OPTIMIZE_IMAGE_TARGETS_AND_VUMARKS:

https://library.vuforia.com/content/vuforia-library/en/articles/Training/vuforia-fusion-article.html

We've seen varying device tracking performance on Android devices, so you may want to try using our legacy SLAM tracker for Extended Tracking.

gcampbell90 wrote:

I've dropped the number of tracked images to one(necessary for vumarks?)

For VuMarks, this is not necessary. The VuMark dataset is a template the can recognize hundreds/thousands/millions/billions of VuMarks depending upon how they have been configured.

Thanks,

Vuforia Engine Support

Log in or register to post comments