LINK ISSUE

LINK ISSUE

Anonymous
Not applicable
555 Views
3 Replies
Message 1 of 4

LINK ISSUE

Anonymous
Not applicable

Hi everyone,

 

I have two objects, lets say A and B.

I link my B object in A so I can modify A and see B.

So far so good....

But when I try to link A in B so I can do the same with B fusion says I have a "cyclic dependency not allowed".

 

What is the right way to do this basic thing?

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

innovatenate
Autodesk Support
Autodesk Support

Could you use the break link command to get what you need? Do the designs need to be X-Referenced (Is A & B going to be used in other designs)? If not, the design could be self-contained and contain A & B components. 

 

Cyclical dependencies are prevented because you would get caught in an endless update loop if they were not. Update A -> Update B -> Update A -> Update B, etc...

 

Perhaps the easiest solution is to insert A & B into another design C if they must be x-referenced. I'm not sure about the end goal, but I hope this helps.

 

Thanks,

 

 

 




Nathan Chandler
Principal Specialist
0 Likes
Message 3 of 4

Anonymous
Not applicable

Thank you Nathan but I would like to keep things linked so it remains interactive..

0 Likes
Message 4 of 4

innovatenate
Autodesk Support
Autodesk Support

If you insert A & B into design C and then update A or B, it will automatically update in design C. Cyclical dependencies  are purposely, intentionally block to prevent getting stuck into an endless update loop. The only way around this is to keep the references contained to a single design. If you do not use X-References, you can do the same thing B -> influence A -> which influences component B again by leveraging the parametric timeline in a design.

 

It only makes sense to have A & B be x-references if they are going to be used in many more assemblies. 

 

I hope that helps to address your question.

 

Thanks,

 




Nathan Chandler
Principal Specialist
0 Likes