In my top down assembly which I am currently building, there are Virtual components that always have the rebuild icon in the feature tree.
Why are thee not rebuilding?
I cant explain why, but I just did a pack and go of this assembly. Even though its all virtual, I thought this might purge any items that aren't being used. After the pack and go there is no traffic light. The model has resolved perfectly.
Thanks for the support guys. Much appreciated.
That's not much info to go on..
If you dig into the tree can you see traffic lights lower down...on a specific component or feature that is causing it?
Digging into the tree, All of the components within these virtual assemblies also have the traffic light.
Lee Kiefer wrote: Digging into the tree, All of the components within these virtual assemblies also have the traffic light.
Lee Kiefer wrote:
If you open a component and rebuild it, does the traffic light go away temporarily, or is it permanent?
It's very tricky to diagnose from here.. it could be anything really.
I like to show update holders - and sometimes I reorder them - although if this has any effect I'm not entirely certain - but it makes me feel better.
I have assemblies that are well behaved almost always but then sometimes need a rebuild for no reason I can discern.
I have a hunch is has to do with the order files are saved, but again I'm very hesitant to be sure... and if you have virtual files then this is out of your control anyway.
If I open the component and rebuild it, the traffic lights do not go away.
I have update holders visible as well. There are a lot of them in this assembly.
Even closing the assembly then reopening it does not seem to make a difference.
I typically never have this issue which is why I am at a loss on this assembly. I am not accustomed to trying to fix a situation such as this.
With all of the sub assemblies in this model, the issue only lies with one of them so it shouldn't be this hard to track down the cause.
Lee Kiefer wrote: If I open the component and rebuild it, the traffic lights do not go away.I have update holders visible as well. There are a lot of them in this assembly.Even closing the assembly then reopening it does not seem to make a difference.I typically never have this issue which is why I am at a loss on this assembly. I am not accustomed to trying to fix a situation such as this. With all of the sub assemblies in this model, the issue only lies with one of them so it shouldn't be this hard to track down the cause.
That's partly good news at least. ..and it sounds to me like you know what you are doing.
So is it just the one sketch that is causing the trouble?
There's a possibility, it's a SW thing. I have an SPR for something similar, sent me nuts, in the end I had to remodel it a different way
Ive narrowed it down to one virtual part. I cant seem to get it to go away, but it does seem to be isolated to this one part. I think you might be right that its the ghost in the machine lol. I think on this on I will live with it since its not actually causing any issues other than disturbing me.
Lee Kiefer -
Constant need to Rebuild is from Circular References
Like Rob Edwards mentions, we have no info to go off of, so we are like a; one armed blind man wall papering his room, while on banana peals and all the flees of a thousand camels in both arm pits...
If you have assembly driven parts, the assembly must be open to edit parts and have them update.
Thanks for responding.
I wast sure what information to add so I kept it vague and figured I could elaborate on it once the conversation started to roll.
So this is a top down assembly that contains all virtual component including sub assemblies.
When I open these sub assemblies, the components inside of those are also showing the traffic light one each on.
The main assembly is open as I am working since I am modeling top down.
I was thinking there might be a setting that tells solid works not to rebuild this assembly under certain circumstances.
Lee Kiefer - It depends on where you are getting the information from and to where you'er sending it too.
Always push information down the Feature Tree, never pull it up from the bottom. It is best to have the driven Sketch in the top of the feature tree and if you're using Top Down design then I would suggest you have a Skeleton Sketch Part or a Master Part as the first item in the feature tree. Keep all your driving sketches/planes/axis etc in that Part, then when you add a new part you'll be pulling information down from a part or sketch...
Everything you point out is good advice and is how I modeled this. I have the main driving sketch in the top of the feature tree as the first item in the main assembly. This is the sketch that drives the sub components.
Lee Kiefer - Ok, that's good, how are you driving the Sub-Assembly Components??
Check if you have a cyclic reference in equations somewhere down the three in subassemblies
There are no equations in this assembly or any of its components.
Awesome that you got it working for you, things like that can drive ya nuts..
I'm giving you the correct answer......that solidworks can drive us nuts. True statement.
Lee Kiefer - Gee thanks, but not necessary
Lee Kiefer - Geeez - now you took the correct answer away, who's driving who nuts Are your middle initials SW...
the continuous rebuild error. yep better to have that than the circular references crash. Top down assembly takes some thought and practice to get things right. A little trial and error. if that does not drive you nuts trying to work on parts created by some coworkers will.
Retrieving data ...