Inventor Part Density/Mass Shows a “0.000” Value After Upgrade

May 28, 2021 Heath White

Inventor Part Density/Mass Shows a “0.000” Value After Upgrade

Issue:

After upgrading Inventor, you notice that existing parts will show a “0.000” value for both “Density” and “Mass” in the iProperties.  New parts may or may not exhibit the same behavior.  If the problem parts are sent to someone else who is using a different material library, they will see the same issue with the currently selected material, however changing the material will cause the density and mass to update correctly.  Switching back to the original material will still show a “0” value.

Causes:

This issue appears to be caused by a corrupt Material “.adsklib” file.  This will be evident when checking the material properties since, even though the material information stored in the file is populated and correct, as shown below, the density and mass will not populate correctly in the iProperties.

Solution:

There does not appear to be a way to repair the library, so the best option is to replace the corrupt library with either, a) a backup of the library if you customized your material library or b) with a copy of the default library, depending on which you were using prior to the upgrade.  This has been shown to resolve the issue without the need to recreate the parts or materials.

For the Autodesk Material Library, the default location is in the following location:

NOTE: The path illustrated is for Inventor Professional 2022, adjust for your release of Inventor.

 

For the Default Inventor Material Library, the following is the default location:

NOTE: The path illustrated is for Inventor Professional 2022, adjust for your release of Inventor.

About the Author

Heath White

Sr. Technical Support Specialist, Manufacturing

Follow on Linkedin More Content by Heath White
Previous Article
Clean Uninstall of the IMAGINiT Reprise License Manager
Clean Uninstall of the IMAGINiT Reprise License Manager

Clean Uninstall of the IMAGINiT Reprise License Manager

Next Article
Measure, Distance, and Area commands not giving correct values
Measure, Distance, and Area commands not giving correct values

This problem is usually because you have items at different Z elevations, and are using Object Snaps (OSNAP...