This is a multi-part message in MIME format.
------=_NextPart_000_000E_01C8642E.94F0EE70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I found a new (to me, maybe to you, too) use for Model Player ~ fixing =
assemblies. I created a new assembly from an existing one with 'Save a =
copy', replaced some components, then notices, after a regen that the =
first component was frozen. I did a search, using the Search tool for =
components with the Status of 'frozen' and found a few hundred of them. =
The loss of assembly constraints cascaded from the first frozen =
component (an ECAD export of a PWA).
I tried several different methods of trying to facilitate unfreezing or =
even getting to the frozen components, including Insert mode. That gave =
me the idea to try Model Player because it does the equivalent in a more =
dynamic way. The interesting thing about MP is that it has this button =
called 'Fix Model'. Pressing this throws you, temporarily and =
interactively, into Resolve mode where you can 'Redefine', 'Fix Model', =
etc.
The first great thing about this was that it cleared away all the later =
components so you could start from the beginning and regen or fix =
anything 'broken'. The second great thing was that after you fixed the =
frozen component, it resumed right where you left off. The third was =
that, unlike typical Resolve mode operation, it showed you the placed, =
frozen component so you didn't have to guess or figure out before hand =
what and where the component was/lived. The fourth was that it let you =
get inside groups/patterns to an individual component and redefine that =
without disturbing the pattern or group. When the lead component in a =
pattern was redefined, just pressing the advance button got each of the =
patterned elements regen'd with every button press. I got through the =
several hundred frozen components in a couple hours with minimal pain.
The only smarter way would have been to NOT use replace but to assemble =
the new components on top of the old, use the search to find everything =
that was a child of the mating surface and bulk Reroute the components =
to the new surface.
David Janes
------=_NextPart_000_000E_01C8642E.94F0EE70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>I found a new (to me, maybe to you, too) use for Model Player ~ =
fixing=20
assemblies. I created a new assembly from an existing one with 'Save a =
copy',=20
replaced some components, then notices, after a regen that the first =
component=20
was frozen. I did a search, using the Search tool for components with =
the Status=20
of 'frozen' and found a few hundred of them. The loss of assembly =
constraints=20
cascaded from the first frozen component (an ECAD export of a =
PWA).</DIV>
<DIV> </DIV>
<DIV>I tried several different methods of trying to facilitate =
unfreezing or=20
even getting to the frozen components, including Insert mode. That gave =
me the=20
idea to try Model Player because it does the equivalent in a more =
dynamic way.=20
The interesting thing about MP is that it has this button called 'Fix =
Model'.=20
Pressing this throws you, temporarily and interactively, into Resolve =
mode where=20
you can 'Redefine', 'Fix Model', etc.</DIV>
<DIV> </DIV>
<DIV>The first great thing about this was that it cleared away all the =
later=20
components so you could start from the beginning and regen or fix =
anything=20
'broken'. The second great thing was that after you fixed the frozen =
component,=20
it resumed right where you left off. The third was that, unlike typical =
Resolve=20
mode operation, it showed you the placed, frozen component so you didn't =
have to=20
guess or figure out before hand what and where the component was/lived. =
The=20
fourth was that it let you get inside groups/patterns to an individual =
component=20
and redefine that without disturbing the pattern or group. When the lead =
component in a pattern was redefined, just pressing the advance button=20
got each of the patterned elements regen'd with every button =
press. I=20
got through the several hundred frozen components in a couple hours with =
minimal=20
pain.</DIV>
<DIV> </DIV>
<DIV>The only smarter way would have been to NOT use replace but to =
assemble the=20
new components on top of the old, use the search to find everything that =
was a=20
child of the mating surface and bulk Reroute the components to the new=20
surface.</DIV>
<DIV> </DIV>
<DIV>David Janes</DIV></BODY></HTML>
------=_NextPart_000_000E_01C8642E.94F0EE70--
|
