Problem with derived/linked components

Problem with derived/linked components

gsaDO
Enthusiast Enthusiast
586 Views
3 Replies
Message 1 of 4

Problem with derived/linked components

gsaDO
Enthusiast
Enthusiast

I'm got myself in some kind of twisted confusion I could use help making sense of.  I think it's from a combination of things I did without really understanding the implications.  Right now, all three files show they are out of date, but if I try to update any of them the gear disappears.  (To add possible confusion, there is a second gear component which is hidden.  For reasons that I can't remember I created a second one in order to do something and found I couldn't find a way to get rid of the first one.)  What a mess.  Here are the files.

Any help would be appreciated.

Thanks.

0 Likes
Accepted solutions (1)
587 Views
3 Replies
Replies (3)
Message 2 of 4

gautham_kattethota
Autodesk
Autodesk
Accepted solution

Hi @gsaDO 

I looked at one of the F3Zs and the screencast provided and the problem with disappearing bodies is because it seems you are removing a component that is used as a source for the derive feature. Hence it "disappears" in the target document after you do an update.

In the Gear.f3z, the Gear subcomponent is used as the source for the gear wheel in the file Gear.f3d - you have other features in this file that add the teeth to the gear.

In the source document "axel plug_short", you have used the Remove feature on the Gear sub-component.  You will notice the Remove feature at the end of the timeline.  This essentially removes this feature in the document after that point in the timeline.  Also it does end up affecting the Gear document since you have derived this sub-component into it.  Thats why when you update the Gear document, the derive feature does not find its source component and derived body is lost.  Thats why things disappear in the Gear document.

To fix this, delete the Remove feature in "axel plug_short", save, and update "Gear".  This should restore the design in Gear document.

I didnt check the other F3Zs, but i am assuming it might be the same problem.  If not, let us know and we can investigate further.

 

Regards



Gautham Kattethota
Software Development
Message 3 of 4

TrippyLighting
Consultant
Consultant

@gautham_kattethota spot on. I was just going to post the same thing.

While it should work, I would generally suggest you don't derive geometry out of a design into a new design and then link the design back into the file it was derived out of 😉 


EESignature

0 Likes
Message 4 of 4

gsaDO
Enthusiast
Enthusiast

Thanks.  That was an easy fix.  I need to work with the derived function more to really get a handle on the do's and don'ts.

Glenn

0 Likes