Log in or register to post comments

various bugs

October 13, 2012 - 6:02pm #1

Vuforia SDK Version: latest at time of writing

- Description with steps to reproduce: These are bug reports which I made previously. If there is anything unclear or you cannot reproduce it, please post me a mail at

and I will provide some more information.

-If a marker is lost with fast physical camera movements, the marker is still tagged as being tracked for a fraction of a second. This causes the 3d augmentation to be displayed while it should not. I find this very distracting and it breaks the AR illusion. If this is a "feature", please give the user an option to enable or disable this. If this is not a feature, please increase the speed of the marker de-recognition. The speed of de-recognition (marker being lost) is just as important as marker recognition (marker being found). See thread here: http://ar.qualcomm.at/node/2000994

-If the virtual button is occluded by moving the camera so it is partially out of view, the button will still be triggered. This shouldn't be happening. It is known where the camera is in relation to the marker and it's virtual buttons. So the software can test whether or not the button is fully inside the camera view frustum, partially occluded by it, or totally out of it.

-Mark a Frame Marker as LOST or not tracked when one of it's edges is nearly touching or beyond the physical camera view frustum. I noticed that the marker pose often contains large errors while being moved out of view before it is marked as LOST. These errors can be filtered out if the marker obstruction is caused by the marker moving out of the field of view.

-Fix bug when using GetSize() on a marker with x size 1.0 See here:

-If CameraDevice.Instance.Stop() is called, and the remained stopped for a few seconds, it introduces a significant latency between real camera movement and updating of the camera texture. Tested on Transformer Prime.

-CameraDevice.Instance.Stop() doesn't disable the video feed and the marker tracking data exactly at the same time. There is a lag between the two causing pose errors when moving the camera and then freezing the frame. It is very important for my application that the video feed and the tracking stop at exactly the same time.

-Bug: If application is frozen using CameraDevice.Instance.Stop(), then multitasked to home, then back into program: Freeze is automatically unfrozen for video, but tracking is still frozen.

-Fix the grid on video image visual artifact bug with the image target demo.

- Development OS (Mac OS X, Windows, Linux): Windows

- Mobile OS and Version: Android 4.1

- Mobile Device Manufacturer and Model name: Asus Transformer Prime

- Do the Vuforia Sample Applications show the same behavior?: Yes

various bugs

November 12, 2012 - 4:14pm #4

Glad to help :-)

various bugs

October 25, 2012 - 11:37am #3

Hi, let me give you a quick update on some of the issues you pointed out:

- concerning the virtual button occlusion issue (when button gets out of fov), this should have been fixed in the upcoming release of Vuforia 2.0;

- the GetSize() issue in Unity (marker with size 1.0) has also been fixed;

- the latency increase issue after calling CameraDevice.Instance.Stop() does not seem to be present in our tests, so that should be considered resolved.

- similarly, we are not experiencing anymore the visual artifacts that you mention (unless this is device-specific);

As far as the other issues are concerned  (such as synchronization between camera and tracker), these are currently udner investigation and taken into account for possible improvements.


If I have further updates on this I will be happy to share these with you. Meanwhile thank you for all your comments and reports so far, which have been a very valuable input to our engineering team.





various bugs

October 15, 2012 - 2:40am #2

Thanks elecman.

I will rasie with the dev team and get back to you when I have further info.


Log in or register to post comments