By Duane
on Mon, 11/05/2012 - 19:18
I have a couple of targets that are successfully matched in the cloud, but not on the client. One of them has a tracking rating of 1, so I'm not shocked there, however, I have another with a rating of 2 which seems to match just fine using the older 1.5 SDK.
This leads to an unfortunate situation where the app goes out of cloud scanning mode, then never matches the allegedly matching target.
Should I just destroy and resubmit these targets to get them reprocessed?
Targets recognized in cloud, not in client
Have you confirmed this in your logs? - that the resulting trackable is never detected.
You can try re-provisioning them, but that shouldn't make a difference.
Targets recognized in cloud, not in client
I definitely see the hit in the QCAR_onUpdate() handler - I'll need to add some more logging in the local target matching code.
Targets recognized in cloud, not in client
Be sure that you're using the latest sample version as well.
Targets recognized in cloud, not in client
OK, on more rigorous testing, it appears I am able to recognize these targets locally, but it's *much* more picky than the recognition by the cloud.
So, probably a false alarm.
Targets recognized in cloud, not in client
The Cloud Reco service is capable of more robust detection. Did you try running them through the TMS as well?
Targets recognized in cloud, not in client
Yes, we have the same target on the old-school TMS and it also rates it as 2, however, it *feels* like the Vuforia 1.5 client recognizes it more readily than the Vuforia 2.0 client, but that's purely subjective and I certainly can't back that up with hard data.