Technical FAQs

Ask a Question

Opening an exported application on the same PC results in the 'DTM Audit Tool' reporting a mismatch in the DTM version.

Causes and Fixes​
If you use Unity 11.1 to export an application containing a DTM configuration and then open it on another PC using
Unity 12, The DTM Audit tool could report a version mismatch between the DTM that is installed on the PC and the
one within the application.   If the application is saved in Unity 12 and then exported as a .zef file and reopened using
Unity 12 on the same PC, a version mismatch will still be reported in the DTM Audit Tool.

Due to technical reasons, this behavior is by design to help reduce the amount of time needed to build or rebuild an
application containing a large number of DTM's:  The behavior is described as follows:
  • When a DTM is installed, it creates a dataset with a version number.  
  • When a DTM is added to the application, it brings in the dataset with it;'s version number to the application.
  • When the application is built or rebuilt, the dataset version remains the same.
  • No matter how many times the application is either built or rebuilt, the version number will never change,  
  • The only way that the version will get changed is when the DTM is modified.

Engineering has indicated that the application is still OK even with the mismatched version number message that
is reported in the DTM audit Tool.  This message just indicates that the dataset is not up to date.
Was this helpful?
What can we do to improve the information ?