Grasshopper

algorithmic modeling for Rhino

Hi,

For some reason, my Shatter component keeps shuffling my data trees around without any logical reason...

It also returns a " Solution exception:Object reference not set to an instance of an object." message

Have you ever had the same problem before?

Any thoughts on how to avoid this?

Thank you in advance

Views: 1188

Attachments:

Replies to This Discussion

Hi Julien,

looks like at least one bug. Can you internalise those curves and parameters then post the file so I can check it out?

Hi David,

Thanks for your prompt reply!

I think I figured that the Shatter component doesn't seem to like extremely small values of the t parameter  (see attached screenshot)

I modified the seam of the curves and everything was working perfectly.

You'll also find attached the grasshopper definition with internalised params and curves (which kept on crashing when I tried to reopen it...)

Attachments:

Thanks Julien,

I'm getting a cast error (one of the curves is a Null curve). Is that supposed to be the case?

Also your geometry is very far away from the origin and very big in comparison to your tolerance. This can cause problems and severe slowdowns and Rhino is forced to solve issues at a ridiculous level of accuracy.

Not on my computer. There was only an error on the Shatter component.

Unfortunately I can't double check the definition I sent you, it keeps crashing when I try to open it..

I will fix the position of the drawing and the tolerance straight away.

Thanks a lot for your help David! 

I found and fixed the bug in the shatter logic, it was indeed to do with extremely short segments. The fix will go out with an upcoming Rhino6 WIP.

It works now despite the tolerance issues.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service