NXMold
Industrial
- Jan 29, 2008
- 206
In ProE the regeneration order was pretty obvious, it started at the top of the tree and stepped through until the bottom. Thats it.
UG is a little more interesting I see, in a single part it updates after each change (it seems) and I can only guess that it goes through the part navigator items in order like proe did, with the addition of unparameterized features.
What I don't get is what happens with assemblies. I work with generally 40-200 part assemblies (not counting multiple instances) with quite a fair bit of interpart modeling (wave linked, and expressions). Everything works just fine until..... I add mating conditions.
Let the circular references fly! So far I have avoided mating, but that Will be changing very soon. My previously acceptable modeling practices no longer work, and I suspect it has to do with regen.. updating the other parts in an assembly after a change, then that update causing the other part to update...
I don't get the order as it applies to wave linking and mating. If I need to give a more specific example I can.
UG is a little more interesting I see, in a single part it updates after each change (it seems) and I can only guess that it goes through the part navigator items in order like proe did, with the addition of unparameterized features.
What I don't get is what happens with assemblies. I work with generally 40-200 part assemblies (not counting multiple instances) with quite a fair bit of interpart modeling (wave linked, and expressions). Everything works just fine until..... I add mating conditions.
Let the circular references fly! So far I have avoided mating, but that Will be changing very soon. My previously acceptable modeling practices no longer work, and I suspect it has to do with regen.. updating the other parts in an assembly after a change, then that update causing the other part to update...
I don't get the order as it applies to wave linking and mating. If I need to give a more specific example I can.