Solution exception:Object reference not set to an instance of an object ?

Replies to This Discussion

Permalink Reply by David Rutten on May 1, 2016 at 6:04am

Yes, that error is always a bug. It means the programmer (me in the case of Shatter) wasn't careful enough and assumed something was always available when it wasn't.

I can't repeat the problem though because you didn't include the geometry needed at the start of the file.

Permalink Reply by Jonas Blazinskas on May 1, 2016 at 11:34am

Honest mistake, there is it with geo

Attachments:

• shatterbuggeo.gh, 18 KB

Permalink Reply by David Rutten on May 1, 2016 at 11:37am

I'm running it on Rhino6 and there's no error here. It could still be due to tolerance settings, what is the absolute tolerance of your 3dm file?

Permalink Reply by Jonas Blazinskas on May 1, 2016 at 12:33pm

wowwwwww there is rhino6? Time to level up and upgrade that gear :D

Permalink Reply by David Rutten on May 2, 2016 at 4:31am

Rhino6 (or RhinoWip) is available to beta test for Rhino5 owners. You can get access to it from the McNeel discourse forum (just ask there).

Permalink Reply by Jonas Blazinskas on May 1, 2016 at 12:37pm

And nvm I uploaded wrong file again, but problem was fixed by reparameterizing the curves, I guess that fixes the tolerance. Sorry for bothering you :)

Permalink Reply by Kristen on May 26, 2016 at 5:18pm

I'm also getting this error with the shatter component, it's working most of the time but not with the geometry internalised into the attached file. I've reparameterized my curves and written a bit of c# code to change values close to 0/1 to 0/1 to no avail. Any suggestions?

Attachments:

• 160526 Shatter Bug.gh, 32 KB

Permalink Reply by Yoann Mescam (Systemiq) on May 26, 2016 at 6:02pm

Should work if you remove duplicate parameters. I guess Shatter doesnt like cutting a curve several times at the same location.

Also, you may be interested in my new and improved ShatterInt