Since Vuforia requires that you have all the databases .dat and .xml files in the same place in your final build app, we implemented a system that prevents you from having multiple databases with the same name. This ensures that all the .dat and .xml are unique and don’t override each other in the final build.
So when you try to import a new database with the same name as a previously imported database, even in another content folder, we alert you with a new custom UI panel to take action. Note that we are checking names as stored in the .dat and .xml files and not as stored in your Content browser, so this behavior will also be activated even if you change your UAsset name after importing in the content browser.
With the Override panel, you can:
- Compare the newly imported database with the one existing in your project; you’ll get the location in your content browser of the existing database, and a table comparison between the two databases, with the type, and number of targets.
- Handle Referencing: You can also see a list of assets referencing the existing database, this can help decide how you want to handle the referencing, as we give three options:
- From Content Browser:
this will give you a list, from your content browser, of databases you can use to replace references. - Do Nothing:
be careful, if you decide to replace the existing database with the new one, this might lead to unexpected behaviors. - Use Newly Imported BD:
This option will automatically replace the existing database references in all your assets with the newly imported database.
- From Content Browser:
- Set Name and Location: You can handle the imported Asset name and location either by using the new or existing name and location.