Scripting in dotNet would be the way I would advise you to generate this efficiently. To help you along, a Brep is a form of surface, and this function RhUtil::RhinoCurveBrepIntersect from the SDK will calculate your Brep intersection for you, you don't require a surface to do this.
Cheers, Jon On Dec 12, 10:46 pm, phildavis17 <[email protected]> wrote: > I am having some trouble working with really large data sets. I need > to run a curve/surface intersect which will generate hundreds of > thousands of points, and, as you can imagine, it's not going so > smoothly. I tend to get error messages about writing to protected > memory. > > Is there a clever way to accomplish an intersection that generates an > arbitrarily large set of points without crashing? > > Things I have tried: > > 1. Scripting. I have a little experience with VB.net, but none > scripting for rhino. When I tried to run the intersection in a > script, rather than a Grasshopper node, the script seemed to think > that the list of OnSurfaces i was passing it was in fact a list of > OnBReps, and I couldn't get it to change its mind. I would not be > surprised if I were doing something wrong, but I can't for the life of > me figure out what it is. > > 2. Breaking the list of curves up. I have had some success with this > method, but there is no way to know how many times the list will have > to be split up. This definition will be applied to projects of wildly > differing complexity, and once I set it up for the current project, > it's only a matter of time before I have a project that is too big for > it. I would prefer not to have to change the definition for every > project, and my colleagues, who also need to use this thing, are not > very familiar with Rhino, so expecting them to tweak the definition is > not an optimal solution. > > Any thoughts?
