SHATTER component misbehaving

Replies to This Discussion

Permalink Reply by David Rutten on April 9, 2012 at 7:49am

Hi Andy,

you are plugging XYZ points into a curve parameter input. Curve parameters are single numbers.

Also Reparameterizing curves AFTER they are used in an Intersection event means your intersection parameters won't make sense anymore. I would not use Reparameterize at all.

I cannot help out because my current version has a bug with Data Matching I'm still solving so I can't run complex files.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Andy Charles on April 9, 2012 at 11:10am

Thanks very much David,

I have incorporated your advice, but its still not outputting the shatter curves. 

The shatter component seems to contain the output, Contours multiplied by Intersection events.

But when I try to export the curve data always seems to output same contours as were inputted.

Maybe I'm missing a step.

To split the curves, at the point event... should be apparently simple but....

I've uploaded the changes I've made to GHX - and a list item extract to test output

Attachments:

• 024Afor.gh, 5 KB

Permalink Reply by Andy Charles on April 9, 2012 at 11:26am

I would add. I am trying to hook this up to a kangaroo bend component, which is why I need both curve and point objects in this set up...

Permalink Reply by Yoann Mescam (Systemiq) on April 9, 2012 at 4:23pm

Try this :

Clean Tree, Simplify, Shift Paths.

Permalink Reply by Andy Charles on April 10, 2012 at 6:25am

Hey Systemig,

Thanks for the tip.

Some how, on some curves this achieves the shatter.

On others, it shatters at completely different points.

Here's a couple of images:

Permalink Reply by lucas cañada on April 10, 2012 at 7:22am

Hi Andy! See attached deff. ;)

Attachments:

• 024Afor_1.gh, 6 KB

Permalink Reply by Andy Charles on April 10, 2012 at 7:43am

Hey Lucas

Cheers Thanks!!