Planar example issues

0 votes
asked Jan 4, 2016 by Daniele Suppo (210 points)
Hello, I'm testing planar example on Android and I've noticed some issues:

1) When I launch the app (the Unity splash screen disappear and the camera open) it take a long time loading something, before I can track the reference picture.

Is it normal?

2) It seem a bit slow to detect / track the reference picture (compared to Vuforia, for example), and it seem to easily loose the target orientation (I'm using a printed reference picture, well lit).

Is it normal?

3) During the reference picture tracking I see the green motion vectors, and a green frame around the picture: I suppose I should only see the RGB axis, isn't it?

4) When I create the apk from Unity I get this message "Unable to find unity activity in manifest. You need to make sure orientation attribute is set to fullSensor manually."

Is it normal?


I'm using Unity Personal (free) 5.3.1f1 running on OSX 10.9.5

Device: Samsung Galaxy S5 Mini - Android 4.4.2


1 Answer

+1 vote
answered Jan 4, 2016 by Alex (6,680 points)

Hi Daniele,

please read my answers below...


1) the first time you launch the tracker it creates the actual image targets database on-the-fly so it requires a little bit until the tracker is actually ready to recognise and track any target, but if you can choose to save a 'cache' that will make the loading much faster the next time you start the tracker (this can be done using the cache_write and cache_read parameters in the conf.xml file, they should be set to 1) - nonetheless consider also that the actual device you are using as a great role from the performances point of view...


2) recognition times and robustness may depend on several factors, it is difficult to provide a solution/configuration that will work in all cases, what I can suggest is to modify the conf.xml file by increasing the number of features to track and by lowering the number of features required to init, there are many other parameters that can affect both init time and tracking robustness, you should play with them and in case it is not clear their meaning do not hesitate to write again - again the actual device is very important when talking about performances...


3) motion vectors, features and the green rectangle are there only to help you to tune the tracking parameters, you can hide them all by setting the debug_mode parameter to 0 (if you want to hide only the green rectangle set the parameter to 1)


4) does the app start despite of that message?




commented Jan 4, 2016 by Daniele Suppo (210 points)
Thank-you Alessandro,
1) Ok, I see. Just a question more: does this operating time increase linearly with multiple targets in the same app?
2) Ok, I'll do some test.
3) Ok, I supposed it.
4) Yes

commented Jan 5, 2016 by Alex (6,680 points)
Hi Daniele,
yes, the time required to prepare the tracker increases linearly with the number of images you want to recognize and track.

Regarding the message you are getting when exporting the APK from Unity, we did not manage to reproduce it ...we will keep doing some tests on our side.

Welcome to Developer Portal Q&A, where you can ask questions and receive answers from other members of the community.