BUG: Curve Plane intersection errors out when NULL result would be expected

Hi David,

Thanks for a great release of GH 0.9

I am encountering an issue. I have a list of curves that I would like to intersect with a plane. As soon as it hits a curve that does not intersect with this plane, the component errors out and does not return any values at all. In previous versions, the results for these operations would just be 'Null'

I hope this could be fixed.

Thanks,

Ramon

Tags: bug, curve, intersection, null, plane

Attachments:

CurvePlane.gh, 7 KB

▶ Reply to This

Replies to This Discussion

Permalink Reply by Mateusz on August 16, 2012 at 5:34am

I was just searching if someone else encountered this problem. I'm not alone then. Is there any way to get around that by the time it will be fixed?

▶ Reply

Permalink Reply by Ramonster on August 16, 2012 at 5:50am

Hi,

To get around it, I just created very large plane surfaces on the planes and then performed Curve-Surface intersections. That works for me.

▶ Reply

Permalink Reply by Mateusz on August 16, 2012 at 5:56am

/facepalm

That was just too obvious so i could come up with that ;) Thanks :)

▶ Reply

Permalink Reply by Anthony Buckley on September 13, 2012 at 1:59am

I am encountering the same issue with some old code. Unfortunately I cannot get around it though with very large planes. Previously I would accept the null items then use "clean tree" to remove the null values. Could this component be modified to allow the null values to follow through please?

▶ Reply

Permalink Reply by David Schweim on October 10, 2012 at 8:53am

I am having the same problem. the error reads:

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

Big plane intersections are an obvious solution, but I would think that this is something that could be fixed in the next release.

▶ Reply

Permalink Reply by Anthony Buckley on October 11, 2012 at 3:15am

Hi everyone

I ended up cracking open the old component that used to work (i.e. was more forgiving with non-intersecting cases) and copied the code into a new component, updating everything to the latest syntax. I've tested it a little and it seems to be working fine. Please see attached.

Ant

Attachments:

PlaneCurveIntersectionAnt.gha, 10 KB

▶ Reply

Permalink Reply by David Schweim on October 11, 2012 at 11:28am

Thanks for the component. works great.

▶ Reply

Permalink Reply by Benjamin Baliti on October 19, 2012 at 4:10am

I am a beginner and have been experiencing the same issue. However when I try to load the component in grasshopper I receive 4 errors

"Object: PlaneCurveIntersectionAntC (level 1)
{
Exception has been thrown by the target of an invocation.
TargetInvocationException
}

Object: PlaneCurveIntersectionAntC (level 2)
{
Method not found: 'Int32 GH_InputParamManager.AddCurveParameter(System.String, System.String, System.String, Grasshopper.Kernel.GH_ParamAccess)'.
MissingMethodException
}

Object: PlaneCurveIntersectionAntC (level 1)
{
Exception has been thrown by the target of an invocation.
TargetInvocationException
}

Am I doing something wrong, or maybe perhaps using the wrong version of GH (0.9.0014)?

▶ Reply

Permalink Reply by Anthony Buckley on October 19, 2012 at 4:26am

Hi Benjamin

I'm also fairly new to scripting components so let me just rule a few lines or enquiry out. Your Grasshopper version is the same I was using. How about your copy of Rhino? I am using 64-bit Rhino 5 beta. There was a service pack released recently, have you installed it?

If its not anything to do with the above then I can investigate further. Anyone else any ideas?

Ant

▶ Reply

Permalink Reply by Arend on October 23, 2012 at 7:23am

There seems to be a problem with rhinocommon throwing a nullexception when curves don't intersect. Attached are the two test cases showing the bug, and a similar C# component that catches the errors and retun an empty list if the two don't intersect.

Attachments: