Mass requires update after RebuildAll

[johnster100]

Hi, 

I have the problem that when I do a RebuildAll several of my parts need to be saved due to 'Mass Updates'.

It's the same issue as listed here:

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Assembly-does-not-...

Is there a way to fix this?

It leads to my drawing constantly saying that the assembly requires updates.

thanks

[johnsonshiue · Accepted solution]

Hi John,

Rebuild All does have the tendency to dirty the files. It is a tool that is not supposed to exist. The fact that Rebuild All is needed, it means something did not work correctly. Please share an example that exhibits the behavior here. I would like to understand the behavior better and see if there is a way to avoid the file dirtying.

Many thanks!

[johnster100]

Hi,

thanks for the reply. I was not aware that rebuild should not be used. We quite often add this our ilogic rules just to catch any model which has not been updated. I will change this code.

thanks again,

John

[mrB_Young]

Hi Johnson,
So, are you implying that Rebuild All should be avoided used unless absolutely necessary?

I have recently had a problem with the Job Processor not creating PDF files due to an error whereas the parts being processed were created with Inventor 2024 but were "save as/save copy as" from files created with older versions of Inventor.
I discovered that by performing Rebuild All on the model files the problem went away.  (I posted about it in the Vault forum)

And this problem got me wondering if iLogic should be utilised when doing a Save As, so that it would Rebuild All first before saving.  Or maybe a macro do the same thing.
But it sounds like the iLogic should do: Rebuild All --> Update Mass --> Save As

The problem with the errors on the Job Processor is that it is part of the automation in Vault.
I really want to weed out things that cause such issues.   Is there anything else I should be aware of when using Rebuild All?

[johnsonshiue]

Hi! I should have revised my posting a bit. Rebuild All as a command should not have existed in the first place. Inventor was designed to update the document on demand (when needed). However, we do have some workflows where the on-demand update does not happen properly or timely. As a result, Rebuild All is added to the panel as a way to force Inventor to recompute features from top to bottom in a part or the assembly features/constraints in an assembly.

Such forceful operation does have the tendency to dirty the files.

From my perspective, when Rebuild All is needed or it helps resolve an issue, it means there is a bug somewhere.

Based on your description, it sounds like a bug to me. If possible, please share the files in zip that can reproduce the behavior here or send it to me directly johnson.shiue@autodesk.com. I am more than happy to take a look and understand the behavior better.

Many thanks!

[mrB_Young]

I have actually opened a support case and used about 1 hour on a zoom call yesterday with one of your colleagues showing this behaviour and how I could repeat this.
So, I guess you (as in Autodesk) are on it. Or do you still want me send of some files?

[johnsonshiue]

Hi! Since you have already contacted Autodesk Product Support, I will let the team take care of the issue to avoid duplicate efforts.

Many thanks!

[henrikubbe4438]

In my 15 odd years working with IV i practically never had a case where I didn't have to use Rebuild all. 

I need to do it All. The. Time. 

And then I have to go in to properties and click update to update the mass, since that is almost never updated. 

It seems like there is a problem with my workflow, then. 

I wonder what I am doing wrong to produce this behavior. 

[CGBenner]

@henrikubbe4438 

Hi, if you could share an example of a part or assembly where you see this behavior, maybe someone could take a look and offer some advice.  What version of Inventor are you using?

[henrikubbe4438]

I have a dataset I can send, but it's too big for the limit. 

[blandb]

Does the Tools > Application Options > General Tab> Physical Properties > Update Physical Properties on Save not do what you want?

[henrikubbe4438]

I have these settings:

...and just saved. This is a screenshot of mass prop post save. 

[blandb]

I was referring to this:

I noticed in your screen shot, it has "MASS PROPERTY UPDATE" "NO"?

[henrikubbe4438]

I tried your suggestion, it does indeed updates it on save.

I still, however need to do a lot of Rebuild all for other reasons. 

The "No" in my image refers to "Prompt to save" and the default setting is yes. 

[CGBenner]

@henrikubbe4438 Did the information provided answer your question? If so, please use Accept Solution so that others may find this in the future. Thank you very much!

[henrikubbe4438]

Only partially.

As I wrote, I still have to press rebuild all and update mass. to get all up to date. 

[CGBenner]

@henrikubbe4438  Did you see the post above from @blandb highlighting the "Update physical properties on save" setting?

[henrikubbe4438]

Yes, I saw that and tried the change.

It does update global mass on save. It does not, however, solve the problem with a rebuild all being needed, so the global mass might still be off, even if it has a number. 

Global update (instead of rebuild all) does not update all files, only rebuild all does this. 

So the only workflow for my assemblies at the moment is rebuild all and update mass/save all files.

But this might be another problem alltogether, as Shiue says. I often have multiple derived files, in several layers, and sometimes use Frame Generator. And also linked parameters. 

[johnsonshiue]

Hi Henri,

Rebuild All should not be necessary to keep things up-to-date, though it does help sometimes. Please share the files that exhibit the behavior with me directly johnson.shiue@autodesk.com. I would like to understand the behavior better.

Many thanks!

[henrikubbe4438]

Mail sent.