algorithmic modeling for Rhino
Hello,
I set something up that relies on the CullPt component to both give me a list of unique points and to report the valence of each of those points. This worked fine at first, but sometimes when I change the input point list it will turn red and give the runtime eror "1. Solution exception:Object reference not set to an instance of an object."
I was trying to set up an example file to attach to this, but in so doing I've confused myself more. You see, if I bake my problem collection of points and input it directly into the CullPt component, it works fine, no problem. But within my much broader definition, it won't accept the points from the other components that helped create them in the first place.
To me, all my groups of points seem to have the same properties, so what is it that I'm doing to get this error? Rebuilding the points doesn't seem to help. The Kangaroo Remove Duplicate Points works fine, but it doesn't give me a valence output, so I'd rather get the CullPt component to work. This problem is really inscrutable to me.
Help, please?
Tags:
Any help on this? I've trawled through past discussions; lots of people seem to get this error, but usually not on the CullPt component. It usually seems to have something to do with the input data being bad, but I cleaned my tree and tested for nulls and that still didn't reveal anything to me.
Which GH version are you using?
I'd really like a file that shows the bug. Instead of baking the points and re-importing them, you can also directly internalize a point parameter. Does the error stay when you do that?
--
David Rutten
david@mcneel.com
Tirol, Austria
Version May-16, 2013 Build 0.9.0056
Other plugins used in file: Kangaroo (removeDuplicateLines)
In the Rhino file, you'll see I've included a bunch of arrangements of circles to input and labeled whether or not they work. Some notes:
-Internalising the point list in the P input of CullPt does not seem to make a difference.
-Sometimes, but not always, Reversing the point list in the P input of CullPt helps. I've labelled the ones that this works for.
-The same input curves can work in one part of the Rhino document but not in another, as with the second and third groups in my file. This seems especially strange.
-I'd tried to set up a file with just the points in it, to be directly inputted into the CullPt component, but I couldn't get as many errors that way. Is one of my other components messing this up?
Hi Gwendolyn,
I think I've encountered the same issue. It only occurs when I use the setting "average" in the CullPt component AND when all the input points are supposed to be merged into one point. As soon as at least one input point exceeds the tolerance, the component works fine again.
I'm not sure if this suits your problem as well, but here's a little work-around:
check if CullPt output is Null -> if yes, insert the average of all input points
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by