generative modeling for Rhino
So...as usual, i have a newbie question. I would like to generate two points on these two surfaces, that i can than, move around within the surface boundaries. So i will need one point, let us say, in the middle of upper srf, that i'll than connect to the other one. I will than make a line which will be used to create e tunnel like vortex between two surfaces. All of this should be moving-friendly :) so i should suppose to move around the whole vortex. is this even possible? heheh
p.s. oh, and another thing, can i create a circle form that is on the surface, shaped like surface, without having to use project option?
I think this will totally do it man, thanks! One question though, if i was to fillet and round the corners of the upper surface and vortex one, how do i do it? there's only FILLET CURVE option. It's not like in Rhino, where you click the edge and you fillet, simply as that :)
sorry to bother you again....don't know why, but the last step (sweep2) doesn't seem to connect with the mesh one!? i opened it with the original files you gave me. tried disconnecting it and than connecting again, tried enabling and disabling the preview .... what could it be?
The mesh component is there just to give a smoother display in GH. I don't know why it won't connect. You don't really need it. Leave it disconnected and turn on Preview in the Sweep2 component and the in the two Surf parameter components further upstream.
ok so i finally got it, the problem was that the surfaces were too much deformed :( that would be a problem in my case since i really need to work with some crazy curved surfaces :) i move some srf point around to see what happens, but didn't got to know why sometimes it sweeps2 sometimes it doesn't. the strange thing is that all other geometries are formed normally: there are two ellipse curves, there's a line connecting them.... so why won't it sweep damn it !?!
I've also noticed that Sweep2 is not always reliable and I don't know why.
Can fix some problems, but its still annoying that Sweep2 would need this workaround.
from my experience i noticed that the two surfaces need to be right curvature, not only but they shouldn't be intersected or at the same level. so try that...