No I'm not. Shatter is working correctly. Can you send me an example of a weird output?
-- David Rutten [email protected] Robert McNeel & Associates On Apr 10, 6:52 am, rustychow <[email protected]> wrote: > great! > > also, i think there was a problem with the shatter command as well, > producing twice as many output curves as it should. not sure if you > noticed that from the thread. i can send you my definition file if > you need it ... > > thanks for the rapid response! > > -russ > > On Apr 9, 7:52 am, David Rutten <[email protected]> wrote: > > > Yes, I forgot to add Data Tree logic to these components so the output > > segments kept overwriting each other. > > I fixed all 6 components (Brep & Region Trim/Split), will be available > > in the next release. > > > Thanks for tracking down the problem, > > David > > > -- > > David Rutten > > [email protected] > > Robert McNeel & Associates > > > On Apr 9, 9:24 am, rustychow <[email protected]> wrote: > > > > yup had this problem too. tried to use the shatter command with the t > > > values from an intersect operation, but this produces some extra > > > curves, inexplicably... think it's broken? split worked fine in > > > release .5 > > > > On Mar 20, 9:50 pm, holbrd <[email protected]> wrote: > > > > > I am using version .6006. i was using thesplitcomponent with brep > > > > and found that the curve gets divided and then it deletes the second > > > > half. is there anything i can do to retrieve the other half? i > > > > uploaded a jpg of my problem > > > > >http://grasshopper3d.googlegroups.com/web/split.jpg
