
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
Doesn't matter for me whether I select first or not. CTD either way. I sure hope it's not some sort of AMD thing. My machine is an AMD 2100+ with 1gb ram. jk <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Yes, I've had the same problems you describe. I found that if I choose the axis and subassembly prior to selecting the > component pattern command I could make it work. If I select the component pattern command then select the axis and > subassy it would ctd. Also, I don't have a problem on my day job computer, only on my home machine. > > Work machine is a Dell 2.8GHz Zeon 1GB ram with NVidea Quadro4 900 XGL > > Home machine is a AMD 1.4 GHz 768 GB ram with Oxygen GVX1 > > MT > > On Tue, 2 Dec 2003 20:42:53 -0800, "John Kreutzberger" <[EMAIL PROTECTED]> wrote: > > >I had a mold design last week than I could repeatedly CTD. I had a component > >pattern in it referencing a sub-assy. Whenever I tried to edit the component > >pattern-hello desktop. That one was a linear pattern. > > > >My new job also has a sub-assembly within a parent assembly. I located this > >sub where I wanted it and then created an axis. I then used this axis to > >make a circular pattern (180°) with the sub-assy. Every time I try to > >complete this component pattern, I immediately CTD. It usually happens when > >I am trying to change the 15° default to 180°. (by the way-who decided that > >15° shoud be the default??. I almost always use 180°.) > > > >To repeat ; inserting a sub-assy into an upper level asembly and then trying > >to pattern that new sub-assy will ALWAYS CTD. > > > >By the way, that first job would also CTD when I tried to edit component > >patterns that didn't reference the sub-assy. > > > >My VAR has confirmed the first one, but hasn't seen the second one yet. > >(only wierdos like me are working this late.) > > > >Anybody else see this? > > > >Thanks, > > > >jk > > >
| <-- __Chronological__ --> | <-- __Thread__ --> |