Hello, my friend who is using Rhino 8 has developed the code I am using, but when I try to attach the curve it crashes. And this appears
and this is the code
Vertical Random line facade.gh (19.4 KB)
I did not understand why did this happen, I hope someone can explain or help… thank you
That code depends on a curve that is not internalized.
And by the way, R8 .3dm files cannot be opened in R7.
I did not know that! but its a gh file not 3dm. and how to fix the curve issue? I just need to attach the curve from rhino to grasshopper
Post the R7 .3dm file. Or a simple copy containing only the curve.
curve.3dm (155.4 KB)
Here you go
Here is what I’m doing. I added a new ‘Crv’ param to the file, not connected to anything, and assigned the Rhino curve to it. I was able to determine that it’s a single line (2 control points) 55932.393187 units long
Before connecting it to the ‘Crv’ param that drives the code, I disabled some components.
So far, I am able to tell that the long line is extruded 100 units in Z. That surface is then divided into 55932 SubSrf surfaces. That’s all I’ve got so far. This is a methodical process of leaving a large part of the code disabled, then enabling components one by one until it crashes.
It looks like after Dispatch each subsurface is divided further, which is potentially a HUGE number
Curve/line is internalized in this GH file:
Vertical Random line facade2.gh (25.6 KB)
P.S. Yeah, it freezes up for awhile on the next SubSrf after Dispatch, which puts out 1.67 million surface fragments
P.P.S. The Entwine after Path Mapper has 268732 surfaces in two branches… Extrude after Entwine is very slow… Oh, wait, looks hung up at Repeat which might be due to a grafting error.
In general, the way to debug stiff like this is to drastically reduce the number at the first opportunity and make sure it all works and makes sense with far smaller numbers.
OK, Extrude completed in 4.2 minutes. Now Move is very slow.
oh thank you!! wow that was huge… many thanks!!
Looks a bit silly to me. Here is the end, zoomed way in on the geometry:
Here is the entire canvas showing Profiler times, around six minutes total?
I have stayed up last night trying to rescale everything because it was impossible to proceed after SubSrf as you said. So I rescaled the whole building and everything worked smoothly
I didn’t say that. Clearly, the code ran to completion for me without any changes, other than proceeding methodically with disabled components. Took a long time to complete.
it did not work with me, the laptop kept crashing no matter how much I disabled components and waited. But scaling the whole building and then attaching the curves has did it.