I have symmetrical a piece I am working on. Only every time I modify or continue to work on my original part, the symmetrical part does not update, it remains in the state in which I performed the symmetry. Is there a way to bind my symmetrical part to my original part?
Have you looked in the symmetry options if you haven't severed ties with you the original part??? And if you do a CTRL-Q or the two-color light, the symmetrical part updates??? See the link to the attached tutorial:
If it is an assembly, check your options to see if the Large Design Management checkbox is selected, if so, check the Check and Update All Components Automatically checkbox.
Options --> System Options --> Assemblies.
If you have selected the complex assembly mode and your assembly exceeds the maximum number of parts, uncheck the Do not rebuild check box in the assembly window (same path above).
Alternatively, you can increase the number of components needed to enable these properties (not recommended)
It is a use of a "famous external reference" (which can have several forms)
Depending on the options in SW: he asks the user the question, or does a pre-chosen action.
Generally, it is enough to put the original part in SW (i.e. to open it),
Then open the room that needs to be updated.
If it doesn't update, you may need to remember the context of the symmetry, i.e. the ASM in which it was made). Otherwise you have to see the setting of the external reference, by right-clicking in the name of the file in the creation tree, then "List references" (basically we have 3 choices: dynamic i.e. recalculated at each, locked with possible return, or break but no return possible).
Knowing that for a symmetrical part, there is no need to go through an assembly to make it symmetrical .
Just take the PRT part, select the symmetry plane (a basic plane?), then "insert, symmetrical part"
A.Leblanc that's what I was talking about, it's the setting of "external references"
and Symmetry Part, just like other functions, are in fact "external references"
(and as is often the case, it is used indiscriminately by those who "discover" this function, then saturate the software, when the problem is elsewhere...)