algorithmic modeling for Rhino
Surface network curve is breaking when I add a 3rd curve into the U span. Is there a limit?
I tried the command directly in Rhino and it is working so not sure where it's breaking...any advice would really help :)
Tags:
Hi Stefano,
you didn't attach the 3dm file so the original curves won't load and the whole file fails to work.
It's typically a good idea to post just the minimal file anyway, ideally with all data internalised.
David, certainly! Here is the 3dm. I'm essentially starting from 2 curves to create a berm with graphpads to control ridge and cross profile. Any advice wellcome!
The error claims that "At least two curves are needed in the V direction"
When you inspect your V data, it turns out you have one list of two curves (that's all fine!) and second list containing only a single curve (this is why you're getting the error):
If those three curves are supposed to end up in the same surface, you need to make sure they are all part of the same list. Flatten might do the trick, but will also throw a spanner in the works if you want to make your file more complex. You should probably figure out why the third curve ends up in a different list and apply the correct tree transformation to remedy that.
David,
Thanks for your reply. I flattened the curves into a list but it's still giving a null return. I'll have to do some more investigating.
Are those curves in the right order after flattening? The Rhino command does a lot of cleaning up that the component does not do.
David,
You were completely correct. The order of the curves in the list affects whether the surface network will compute or fail. Thank you for your assistance!
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