CAD Forum

Is the component fixed?

Ctrl+Q can be your friend.

AlexLachance wrote: ↑Thu Feb 22, 2024 8:16 pm Is the component fixed?

Nope

Glenn Schroeder wrote: ↑Fri Feb 23, 2024 8:29 am Ctrl+Q can be your friend.

Yes, but not this time. Yet another case where SW required delete and start over.

Uncle_Hairball wrote: ↑Fri Feb 23, 2024 12:41 pm Yes, but not this time. Yet another case where SW required delete and start over.

That would have been my next suggestion.

Uncle_Hairball wrote: ↑Fri Feb 23, 2024 12:41 pm Yes, but not this time. Yet another case where SW required delete and start over.

I hate this about SW. Hate it with every fibre of my being.

It reminds me of this... Except, with SW and scenarios like this because it fails, you are required to do the exact same thing again to acheive the desired result.

Glenn Schroeder wrote: ↑Fri Feb 23, 2024 8:29 am Ctrl+Q can be your friend.

Ctrl+Shift+Q might help if there are configurations

Are you using flexible subassemblies?

Uncle_Hairball wrote: ↑Fri Feb 23, 2024 12:41 pm Yes, but not this time. Yet another case where SW required delete and start over.

Was the component part of a symetry or a pattern? If so, an instance from either could have been the one "locking" it in place.

JSculley wrote: ↑Mon Feb 26, 2024 7:46 am Are you using flexible subassemblies?

Nope

AlexLachance wrote: ↑Mon Feb 26, 2024 7:57 am Was the component part of a symmetry or a pattern? If so, an instance from either could have been the one "locking" it in place.

Hmmm... wish I could check because that's a realistic possibility. Too bad I already fixed it. Delete and reconstruct.

Uncle_Hairball wrote: ↑Mon Feb 26, 2024 2:21 pm Hmmm... wish I could check because that's a realistic possibility. Too bad I already fixed it. Delete and reconstruct.

When I'm getting some weird behavior like that in an assembly, I bring the bar back up to remove the patterns and mirrors.

It's also a habit I have which helps in keeping assemblies lighter. I've seen a lot of people not bother with mating to the original component and then have trouble with their assemblies so I've incorporated it in my workflow for large assemblies.

We don't always get mates deleted when components are deleted. I have found that sometimes those will come back if a component was deleted and then added back to the assembly. So, I put a component in (forgetting that it had been in that assembly weeks ago) and try to add new constraints to put it where I think it should be. It will yell because it has unsupressed the mates that had been suppressed when I deleted the component.

Are there external references that could be driving this?

CarrieIves wrote: ↑Mon Feb 26, 2024 2:43 pm We don't always get mates deleted when components are deleted. I have found that sometimes those will come back if a component was deleted and then added back to the assembly. So, I put a component in (forgetting that it had been in that assembly weeks ago) and try to add new constraints to put it where I think it should be. It will yell because it has unsupressed the mates that had been suppressed when I deleted the component.

Are there external references that could be driving this?

Mates does not get deleted if you dismiss the delete confirmation dialog with delete children disabled.
In addition, under system option-error messages there is a checkbox to dismiss missing mates errors in the tree and they are brushed under the rug making the assy slow as those mates are calculated before being suppressed.

missing mates are errors and should not be dismissed.

I think Alex was right. I just had the same thing happen again and it turned out there were mates on both ends of a mirror.

Thanks everyone for the helpful suggestions!

Uncle_Hairball wrote: ↑Tue Feb 27, 2024 12:44 pm I think Alex was right. I just had the same thing happen again and it turned out there were mates on both ends of a mirror.

Thanks everyone for the helpful suggestions!

Sometimes it's unavoidable, but I try to avoid mating to components brought in with a pattern or mirror.

Uncle_Hairball wrote: ↑Tue Feb 27, 2024 12:44 pm I think Alex was right. I just had the same thing happen again and it turned out there were mates on both ends of a mirror.

Thanks everyone for the helpful suggestions!

That was what I was about to suggest as it happened to me in a large assy with mirrored parts... the mates were added to the mirrored parts instead of the parents... it's easy to make this mistake, especially when you have a very symmetrical assy and don't specifically check where in the tree you're working while selecting components in the graphics area for mating.

One help I've found is to color the key parent parts at the assy level, OR live by the rule of always working in a specific quadrant for symmetric assemblies.

DavidWS wrote: ↑Wed Feb 28, 2024 2:01 pm One help I've found is to color the key parent parts at the assy level, OR live by the rule of always working in a specific quadrant for symmetric assemblies.

You call also roll the feature tree back above all the patterns/mirrors so they are invisible and unavailable for mates. Out of sight, out of mind.

JSculley wrote: ↑Wed Feb 28, 2024 2:20 pm You call also roll the feature tree back above all the patterns/mirrors so they are invisible and unavailable for mates. Out of sight, out of mind.

That's what I usually do.