I have a 'feature' of two holes in a sheetmetal part. I mirror those, all good. I decide that I want a third hole in the original feature, and I do this using the "more holes" option within first hole feature. All good.
How do I get the mirror to update to include the third hole?
Yes I can delete the mirror and mirror all three holes again, but I don't want to do that.
Yes I can just add a second mirror feature but I don't want to do that.
Yes I can just go and manually add a hole but I don't want to do that.
Is it possible?
Hi there @pmckay,
Not really the way Sync is supposed to work though, is it?.......doesn't it it drive off the topology, not the feature tree.
IMHO, for your case, I would probably "Break" the mirror, and let design intent pick it up.
Design Manager Streetscape Limited
Solid Edge ST10 [MP0] Classic [x2 seats]
I gave up on synch mirror. If it was truly going to be a synch function it would evaporate and leave just the new features. Or it would be updateable, but it is nether. I just switch to ordered if I want to have a real mirror.
of course Sync is thinking a little bit different.
But the question is: "Is it necessary to think as mirrored in the classic way?"
Since You says that there is a "mirror" feature in Your pathfinder I suppose You have pressed the "Persist Mirror Associativity".
This - for me - is more or less a persistent relation on the fly!
I personally prefer the non persistent method by unselect thos button.
What is the difference?
Solid Edge Sync then creates additional holes within the same hole feature, and yes the are symmetric due to the live rules, or better to say due to the "Design Intend"
Where will I see the advantage doing so?
The hole feature still is a single hole feature, only with the double of numbers of holes in it.
If You later need an additional hole no problem, and You can mirror this one again without any problem.
You even can delete the original hole without destroying the mirrored one.
And - and this IMHO is the most important AND - due to it is a single hole feature YOu can use it for a pattern in an assembly.
Take this in a consideration wether it might help.
This way of working makes me want to use Sync more. When I do a mirror, I want that as only a starting point, then the two parts evolve on it's own path. Nice to know that about Sync.
Your question sounds rational and understandable.
What is the reason for a persistent mirror?
I for myself have found one reason to use it at all
I use it if the mirror plane is NOT one of the major reference planes and so Live Rules will not recognize them by default.
There is an advanced live rule (Design Intend) You can activate but AFAIK this is to be set always again while the persistent mirror will keep this relation automatically.
Maybe there are other goot reasons which will recommend a persistent mirror, but this one for me is enough to be happy about this feature.