"We offer new support options and therefor the forums are now in read-only mode! Please check out our Support Center for more information." - Vuforia Engine Team

Trackables not working

By hectots on Wed, 06/20/2012 - 17:09
I've uploaded several images to make them trackable but so far I haven't had any success. I'm trying to track a bottle label but is not working. What could I be doing wrong? The width confuse me as to what exactly should I put there. I'm using the mm of the image that I measure in the printed copy. Please help :confused:

DavidBeard

Tue, 03/06/2012 - 20:58

Permalink

Have you been able to create and import a trackable of the bottle label? If so, what's the rating of the label - how many stars? Go ahead and use the width of the printed label, the TMS will infer the height from the submitted image.

The image have a rating of 4 stars. Is possible is the width. The chips trackable have a width of 247 but when I measure my print copy is 225 mm. So I'm confused about what to use as a width. The label is 98.38 mm, it may be that's too small?

Ok, this is getting weird. I'm not sure what I'm doing wrong here. I uploaded the default chips.jpg to my trackables using the same width of 247. I added it to the image target in Unity and still no tracking. :confused::confused:

DavidBeard

Wed, 03/07/2012 - 02:58

Permalink

Which version of the SDK are you using? To confirm, are you sure that you're loading and activating the new datasets - that your environment isn't using another set of trackables? The width of your label is fine, though I'd recommend an integer value.

Ok, here's what I do to setup my project step by step. [LIST=1] [*]I upload an image into my trackables and set the width to the width of the print copy in mm. [*]Then I create a new project in Unity. [*]To that project I import vuforia-android-1-5-10.unitypackage, a simple 3d model and the trackab

DavidBeard

Wed, 03/07/2012 - 05:29

Permalink

You still need to configure the Data Set Load Behaviour component on the ARCamera to load and activate the dataset.

That's it! That's the missing step. Thanks a lot DavidBeard! I don't recall seeing that step in the documentation.