Multiple Objects, multiple Guide Views for Advanced Recognition
When you use an Advanced Model Target Database containing multiple Model Targets and/or multiple Guide Views, Vuforia Engine distinguishes between objects purely by their visual appearance, which means that the following additional considerations should be taken into account when selecting different objects and/or different Guide Views.
Essentially, each Guide View must look different - that is, each Guide View must be distinguishable based on appearance alone. There should be no ambiguity about which object the user is looking at, nor which Guide View corresponds to the current viewing angle and distance.
Objects should look different
All your objects must look different from each other. If you have multiple objects that have a similar shape (for example two cars) you will need to make sure that each one still can be well distinguished from the other (in the car example the sedan and convertible versions would be likely distinct enough).
Guide Views should look different and Recognition Ranges should not overlap
If you have multiple Guide Views, the object should look different from every viewpoint representing a Guide View. This includes the entire Recognition Range of each Guide View. There should never be any ambiguity about which Guide View corresponds to a particular viewing angle and positions.
- If your object is asymmetric (i.e. it looks different from all sides), you just need to make sure the Guide View angle and distance ranges do not overlap.
- If your object is symmetric (i.e. it has some parts that appear similar to each other) you need to make sure that only one Guide View covers the symmetric part, and that every other Guide View you make looks different to the symmetric part.
In addition, if you have multiple objects in a single Advanced Model Target dataset, each of the Guide Views for each object should be visually distinct.
- Having a database where one object is a simple cube, and another object is a machine that has a large, dominant cube-shaped part should be avoided. Both objects might be confused. If you cannot avoid such situations, then you need to make sure that one of the objects has at least a distinctive appearance (logo or pattern) covering ideally most of its surface. When doing so you need to use the realistic option during training. Alternatively, you could set up the Guide Views for the machine so that they do not include its cube-shaped component (e.g. by setting the Target Extents to exclude it).