Are files created in previous version of MDTools compatible with MDTools 975 and vice versa?
Files created in MDTools 975 are not directly compatible with the previous versions of the MDTools 900 series and vice versa.
This issue can be avoided by exporting manifold designs to the MBXML format then importing them into the previous version.
Using the two commands, Export Manifold and Import Manifold, designs from the previous versions of MDTools, such as 970, can be exported to the MBXML format. This can then be imported into MDTools 975.
The same is applicable for files created in MDTools 975 exported to MBXML format and imported into previous versions of MDTools 900 series.
Once imported, designs will be in Virtual design mode but can be converted if designing in Feature mode is preferred.
Related Articles
How do I find the version of MDTools I have installed?
MDTools Ribbon Menu, click the 'About MDTools' option to display the version and build number.How do I find the version of MDTools I have installed?
MDTools Ribbon Menu, click the 'About MDTools' option to display the version and build number.When trying to click on the MDTools options and adjust settings, the error “Object reference not set to an instance of an object” appears. No changes made to settings get saved?
This error can occur if the user profile does not have full permissions to following folder: C:\ProgramData\VEST\MDTools <version>. or Provide full permissions to that folder and then relaunch MDTools. If issue still exists then reinstall MDTools.Why does MDTools crash when inserting a cavity or when creating a new block?
This can occur if Microsoft Access Database Engine 2010 present in Control Panel > Programs List is corrupted. To resolve this issue: Uninstall Microsoft Access Database Engine 2010 from Control Panel > Programs List. Locate the MDTools setup on ...When trying to click on the MDTools options and adjust settings, the error “Object reference not set to an instance of an object” appears. No changes made to settings get saved?
This error can occur if the user profile does not have full permissions to following folder: C:\ProgramData\VEST\MDTools <version> or C:\ProgramData\VEST\MDTools <version> or Provide full permissions to that folder and then relaunch MDTools. If issue ...