Just starting on Creo 2.0, and when I save a part (or assembly) I get the following conflict window pop up:
"Mass properties are not calculated"
Now.... I know what it means The trouble is I have not created a mass properties feature or a saved analysis and I currently have no need or desire to calculate the mass properties of my part. I have to check this box off every time I save a file.
Does anyone know how to get rid of this?
Solved! Go to Solution.
It is the mass properties config option:
I have commented it out in my config.pro for the time being. I'm not sure why it now requires a check off every time you save, whereas in earlier releases it didn't. Must be an "improvement".
Something is calling for one of the mass property values, maybe a format is trying to report the weight of the object or even the material callout. Check the relations for the part and the individual features. Something want data. This is not normal behavior for bare bones setups.
There is no parameter calling for any mass property value. I have just created a new part using our standard start part and I get this message even when there is no geometry in the part, just datums.
When I do the same thing, using the exact same start part, in WF5.0 I do not get this message. I only get it in Creo 2.0. Apart from the release of Pro/Creo there is no difference between the two parts, they are both created from the same (WF 5.0) start part.
Yes, it's set to automatic.
This is the same setting as my WF5.0 setup, which is in a different startup folder with different config.pro files.
Yes. I just created a part completely empty, with no template, no features. Same window popped when I tried to save it.
Are you using windchill? What if you open an empty part with the default config.pro?
I just went from Creo 2.0 M030 to M040 and I do not see this message. Something is initiating the need for the requirements. It is likely a new requirement from the WF5 version.
Obviously it is worth opening a case with Tech Support. We would all like to know what could drive this error.