The Model Target Generator (MTG) converts an existing 3D model into a Vuforia Engine dataset that can be used by the Vuforia Engine for Model Target tracking. This tool enables you to confirm whether the features of your model will be useable, to set-up the initial snapping position, and then export the final dataset.
The dataset produced by the MTG includes renderings of the model from the Guide View (detection position), which you can use if you want to create your own custom Guide View images that might be a better match for the visual style of your app than the default Guide View image that the Vuforia Engine API provides.
MTG can read a variety of 3D file formats and convert them into Vuforia Engine’s internal mesh format. Consequently, any visual error in the model introduced in this conversion process will be displayed in the MTG viewport. Some source model formats can result in wrongly converted models since they are missing mesh information. Therefore, the MTG should be used to check whether the imported model corresponds to the source data. If there are issues, using a different file format may resolve them; if not, the source data may need to be cleaned up.
The Model Target Generator lets you define multiple Guide Views for each object. It also allows you to merge datasets for multiple Model Targets into a single dataset, and create training data that allows your app to automatically switch between multiple objects and/or multiple Guide Views at runtime based on what is visible in the camera.
After importing the 3D model into the MTG, the user should make sure the model fulfills the requirements of the checklist displayed on the side. In addition, the user needs to make sure that the scale of the model is correct. Some file formats do not have unit information propagated through the import pipeline. For this reason, the MTG displays the size of the volume occupying the object in meters.
If the object is in fact modelled in different units, this can be quickly fixed via a pop-up menu. This information is then propagated to the exported dataset to ensure tracking works properly. Setting the unit in the UI does not re-scale the 3D object - it only specifies how a unit of 1 is supposed to be interpreted. Rescaling the model is not supported in the MTG as it is only designed to be a 3D model viewer, and not a mesh editor.