Master Part disappears from assembly after 'Get Latest' command...

[J_Solidwool]

Hi,

I am in the final stages of checking through a tooling assembly. I have used a Part as a 'master' to cut the cavity using Boundary Fill. Up until today all parts, this master part included, update using 'Get Latest'.  But today all of a sudden when I use 'Get Latest' the master part disappears from the browser!

What is going on?!

Very Frustrating at this stage and timing in this project (as these things always are.)

Any advice will be greatly appreciated!

Thanks

Justin

[TrippyLighting]

Have you tried running a "Modify->Compute all" ?

[J_Solidwool]

Hi Peter,

Thanks for trying to help.

I hadn't tried that. When I do everything dissapears and then I get a Circular Dependancy alert that I haven't had before. If I click off the view port for that assembly to another viewport / part, then go back to the assembly in question the circular dependancy alert has gone, but I still don't have any parts showing in the browser!

Look everything has gone!

Thanks

Justin

[TrippyLighting]

I have no idea if this helps, but delete all the section views in the Analysis  folder.

[J_Solidwool]

Thanks Peter,

Just tried that and it doesn't improve the situation.

So after running 'Compute all' again all components disappear from view and from the browser. The history tree remains, but I have a circular dependancy (that I didn't have before) and i'm still  being told that a 1 component is out of date. So if I then run 'Get latest' the circular dependancy alert goes, but I still have no components!

Are you thinking this is a bug, or something I have done?

Thanks

Justin

[TrippyLighting]

Hard to say. Can you open earlier versions of the design and how do they behave ?

[J_Solidwool]

Hi Peter,

Thanks - I have tried opening 3 earlier designs and they all behave the same. I think the thing that is odd is that everything was updating ok last week. To reiterate the part just disappears from the components list when 'get latest' is run. And then with 'Compute all' everything dissapears!

Clutching at straws a bit now, but my internet service is poor. So I am just going to go somewhere down the road where they have fibre broadband to see if it is an issue downloading the updated master file from the cloud

Thanks

Justin

[J_Solidwool]

If anyone is following this, the issue is still unresolved. The fibre broadband didn't solve the problem. So the component still disappears after using the 'Get latest' command.

Thanks

Justin

[Rob_Lockwood]

if you open the master part file itself directly, the component is present and unchanged? Is the part a simple insert/xref, or inserted using derive?

If you save a new version of the master, does the issue persist?

[J_Solidwool]

Hi Rob,

Thanks for the reply.

Yes, opening the master itself it's all good. It's on version 57 now and version in the assembly is 47. The differences from 47 to 57 are me saving it after simulations. A few sketches for investigating the part have been added and deleted, and versions 56 and 57 are me going back to version 47 and saving that as latest.

The part was inserted originally using 'insert'. By right clicking and selecting 'insert into current part' on the part in the file explorer.

And finally yes saving new versions of the master the problem still persists...

[jeff_strater]

circular dependencies are not affected by connection to the internet.  That is usually symptom of a problem in your design history.  Sometimes we can show you how to untangle this, but we'd be more curious about how this came to be in the first place.  Have you done any reordering in the timeline?  (dragging features to different timeline locations)?  Can you share your design here?  Even better, can you share a past version of the design that is OK (say, before the Get Latest), as well as the one that is not?

[J_Solidwool]

Hi Jeff,

Thanks for your help.

About sharing the file, unfortunately, I can't publicly for confidentiality reasons. I have sent to the helpdesk though.

About the circular dependency, that only happens if I try a 'compute all' and doesn't happen if I use 'get latest' which is when the component just disappears!

However, if you think the solution lies in using the 'compute all' and trying to unravel the circular dependency that creates, then I'm happy to have a go  well I have just had a look into that and the 'compute all' makes all components disappear as well as throwing up a circular dependency. So it's not possible to edit anything. No bodies or components remain even if I move the history bar back...

[jeff_strater]

OK, I understand about sharing the design.  The issue with a circular dependency is that it essentially blocks all compute, which is why everything appears to disappear.   The good news is that the source data for everything is still intact.  In the report for the circular dependency, it should list the features that are involved in the cycle.  We have been able to fix the cycle by just dragging features in the timeline.  For instance, if the cycle shows that a sketch is in the timeline after a feature that consumes it, sometimes you can fix things by just dragging that sketch before the consuming feature (a separate issue is how the cycle came to be in the first place, which is a topic for another day).  So, even though the circular dependency exists, you can still do this kind of edit (changing the order in the timeline), which is often enough to fix things.

[J_Solidwool]

Thanks @jeff_strater - having a go at unpicking that circular then!

See the image pasted here - if I go back and delete the 'Pinch off profile' sketch, then 'get latest' the master updates and doesn't disappear. So I hope I am correct to think I have found the problem.

I'll rework that sketch and report back here if that has solved it.

But if that works, I really don't understand why that sketch is only causing a circular dependency now, it's been there for a long time!

Thanks for all help from everyone so far.

Jus

[jeff_strater · Accepted solution]

@J_Solidwool - in theory, you should not have to delete that sketch, there may have been other ways to have fixed it, but if that works, that is great.  As to why this fails now, it's really hard to say.  I have seen cases of this that appear to have been caused by reordering timeline features.  In theory, this should never happen, but there must be some bugs in the reorder code that allow it.  But, there have been other bugs over time that have caused cycles (a usual culprit is Project in sketch - there was a case where it was possible to Project geometry that was produced into the sketch that was the profile for that feature).  All of these are, in theory, blocked.