Large Assembly Modeling Workflows & Vault Copy Design.

Large Assembly Modeling Workflows & Vault Copy Design.

bradeneuropeArthur
Mentor Mentor
758 Views
3 Replies
Message 1 of 4

Large Assembly Modeling Workflows & Vault Copy Design.

bradeneuropeArthur
Mentor
Mentor

Hi,

The below methods are Inventor design methods that are explained in the help file.

 

https://help.autodesk.com/view/INVNTOR/2018/ENU/?guid=GUID-456388EE-9B7F-442E-B917-B76BDE016FD2

 

They work beautifully for Inventor.

But if the design needs to be copy Designed with Vault the references to the parts where the "Projected Geometry" comes from is not updated and changed to the new Copy design files.

For the derived parts this is done correctly.

 

Please find attached a document with my comments.

 

Please advice how to do this this issue.

@johnsonshiue 

@CGBenner 

@ihayesjr 

 

Best regards,

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes
759 Views
3 Replies
Replies (3)
Message 2 of 4

johnsonshiue
Community Manager
Community Manager

Hi Brendan,

 

Many thanks for reporting the behavior! If I understand the issue correctly, this is actually an Inventor's bug. The simplified workflow is like this. You have an assembly with two parts. One is adaptive to the other. In Inventor browser, the adaptive geometry source is shown correctly. If you use Vault Copy Design or iLogic Design Copy, the source name will not be updated to the new file.

This is a bug and a limitation. The issue here is that, though the file reference has been changed, the adaptive compute does not kick in to "refresh" it. Rebuild All will make it updated.

We have had several rounds of internal discussion about this. The fact that Rebuild All brings it up-to-date means a compute event is needed. However, duplicate the design should not require a recompute. So, there is a conflict here. We don't want to recompute automatically, since it may not make sense. In the meantime, you can use Rebuild All to bring it up-to-date.

Many thanks!



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 3 of 4

swalton
Mentor
Mentor

I'm not sure I understand the issue...

 

What I get from @johnsonshiue's post is that the copied Inventor model has the correct dependency links in the background, but will not show them to the user until after a rebuild-all is performed.  Additionally, the Autodesk team thinks that the performance cost of forcing a rebuild-all is too much, so Inventor should display confusing information. 

 

Do I understand this correctly, or do I need more coffee?

 

 

Steve Walton
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Inventor 2025
Vault Professional 2025
0 Likes
Message 4 of 4

bradeneuropeArthur
Mentor
Mentor

@johnsonshiue wrote:

Hi Brendan,

 

Many thanks for reporting the behavior! If I understand the issue correctly, this is actually an Inventor's bug.

Is that confirmed?

The simplified workflow is like this.

You have an assembly with two parts. One is adaptive to the other.

In Inventor browser, the adaptive geometry source is shown correctly.

If you use Vault Copy Design or iLogic Design Copy, the source name will not be updated to the new file.

This is a bug and a limitation.

That is Exact the case here too.

The issue here is that, though the file reference has been changed, the adaptive compute does not kick in to "refresh" it.

Rebuild All will make it updated.

Do you mean that

step 1 is Copy Design in Vault.

step 2 is open the design (Assembly where the files are projected from with all related files) and use "Rebuild" will change the references correctly?

We have had several rounds of internal discussion about this.

Internally at Autodesk.

The fact that Rebuild All brings it up-to-date means a compute event is needed.

You mean after a Copy design?

However, duplicate the design should not require a recompute.

What do you mean with duplicate design here?

So, there is a conflict here.

Can you explain this a bit further?

We don't want to recompute automatically, since it may not make sense.

Why not if this would solve the isssue! Or do I undestand wrong the indeed a rebuild is needed after a Copy Design Automaticaly?

In the meantime, you can use Rebuild All to bring it up-to-date.

So fact is that after Copy Design using Rebuild All in Inventor should solve the issue and bring the new references correct and updated?

Many thanks!

 

Thanks for you answers,

 

Arthur Knoors


 

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes