We are evaluating Vuforia for an AR project that needs to track around 10 markers simultaneously. We have been impressed with Vuforias tracking abilities, but the initial detection of a VuMark appears to require the VuMark to be very close to the camera. For the user this means they have to lean close in to each marker for the initial detection, and then the tracking works pretty well after that. Is the initial detection distance configurable in any way? What we suspect is happening is that Vuforia is doing an analysis of the camera image to find candidate contours to check for Vumark codes. Any contour below a certain size is probably rejected, and this is why you need to be close for the initial detection. Is this the case, and is there any way to configure that? We understand that this would have a performance cost as there could be many more candidate contours in the image to check for Vumarks.
The performance we are looking for in terms of initial detection is similar to that of Aruco marker detection as seen here:
https://docs.opencv.org/3.4/d5/dae/tutorial_aruco_detection.html
Would it be possible to get similar performance from Vuforia if using a similar marker pattern? We have been testing using the Mars samples.
Hi,
Hi,