[PLUGIN] Flowify v1.1.0 (updated 150327)
-
Excellent!
Frank Gehry will love it!
PS
You have also a "Flow" function inside Moi3D
(Ctrl + C, Ctrl + V between Rhino <--> Moi on the 2 ways) -
This looks very cool, thanks for sharing and also for the good tutorial.
-
Loving the haunted house example!
It's been a while since I used Rhino - is the operation of setting up the meshes the same as FlowAlongSrf?(Btw, nice example of Bezier Surface there - it's seem to be more versatile than I expected.
) -
this is amazing!! Thank you so much for this,something i could definitely use with my current project and save some long boring hours.
-
This looks amazingly useful!
tt_su's question about meshes is good.
How does this wrap textures? Are they projected in the same way as meshes?
-
The demonstrations and examples are impressive and inspiring. This offers completely new possibilities to deform objects specifically and flowing. "Fredo6_FredoScale Radial Bending" on the next level.
Will test it under SU8. -
CAUL, this is awesome thing! Thank you for sharing.
I tried some primitive case of 'panelization'. Everything went smooth except point A got split into A1 and A2. Is it possible to tweak the algorithm so it'd keep the same number of vertices?
Edit: I found 'flowify without cut' mode that solves this issue
BTW What exactly 'Aux' tools do?
-
@rv1974 said:
Edit: I found 'flowify without cut' mode that solves this issue
I was just going to suggest this
@rv1974 said:
BTW What exactly 'Aux' tools do?
The first Aux tool "Edge -> CLine" converts an edge to a construction line. If two connection edges intersect each other (if you pair your corners crosswise), then they split into four edges and that is not handled by the extension. The extension let you convert an edge to a construction line to handle this.
The purpose of the second Aux tool cannot really be explained in less than 2500 words. There will eventually be a tutorial with this tool playing a small part.
-
Caul
I tried to mimic your example and I am have a few problems.
- The IMPOSE GRID function does not modify my "Projection Surface".
- I am not getting any errors in the Ruby Console when initiating the IMPOSE GRID feature.
- I am receiving an error dialog message concerning the " Target grid".
@unknownuser said:
INPUT ERROR: Error while parsing the Target grid
The grid must conform to:- A cell consists of exactly four edges. Beware of collinear edge segments
- Connection edges must attatch to two adjecent corners
- The grid must have four corners
- Every row in the grid must have the same number of cells
- No holes
- I checked the Target Grid and it all seems to comply with the rules.
- I am not getting any errors in the Ruby Console
Attached is the skp.
Can anyone figure out why it's not working?
Although I believe I am following the instructions step by step... user error?
-
@tt_su said:
It's been a while since I used Rhino - is the operation of setting up the meshes the same as FlowAlongSrf?
It is very similar, in Rhino there are no explicit connection edges though.
@pilou said:
You have also a "Flow" function inside Moi3D
That was a nice summary, the projective version of Flow is actually coded and may end up in a later version of Flowify.
@duanekemp said:
Is v1.2 addressing texture mapping?
I will look into this, it would certainly be a nice feature.
-
@Cmd
You must draw the 2 lines' Extremities Start to extremities' Target!
-
Just as I thought..... USER ERROR Doh!!
Thanks
-
Very very cool. Great job!
-
These are the plugins that make SU more valuable! Great scripting Caul!
-
Thamk you very much, you are magician Caul. It's awesome. First test now
-
@caul said:
@rv1974 said:
Edit: I found 'flowify without cut' mode that solves this issue
I was just going to suggest this
Great and useful plugin sir! thank you so much!
i played a bit with it and it's really enjoiable, but i have a request if possible/not toohard to accomplish..
it looks like the "flow without" cut doesn't add triangles but unsfoften every edges.. can we have an option to preserve edge properties so that this tool could be more esily integrated in an organic/quadfacetools-friendly workflow?edit - attached example
-
@panixia said:
it looks like the "flow without" cut doesn't add triangles but unsfoften every edges.. can we have an option to preserve edge properties so that this tool could be more esily integrated in an organic/quadfacetools-friendly workflow?
+1e6
-
Is v1.2 addressing texture mapping?
-
@unknownuser said:
it looks like the "flow without" cut doesn't add triangles but unsfoften every edges.. can we have an option to preserve edge properties so that this tool could be more esily integrated in an organic/quadfacetools-friendly workflow?
Good suggestion! This feature is now introduced in v1.1.0.
-
wow! thank you so much! it works fine!
Advertisement