Thursday, April 30, 2009

Fluid as Fashion

Just thought this was beautiful:

ambiancepaint

The making of fashion for walls (although it has nudity, watch it full screen if you can – the video is small):

Wednesday, April 8, 2009

A Rhinoceros with Fins on Stairs

I was asked today to do a short tutorial on a little known yet valuable command in Rhino called Fin.

Fin, according to the help manual, “Creates a surface by extruding a curve on a surface, normal to the surface.” The practical example below will use the fin command to create stair a simple staircase based on bent geometry.

Problem: This technique will not work with an applied UV curve nor geometry which has been oriented to a predefined surface; in both instances the threads on the staircase become skewed. When offsetting a polyline which has been through bend, etc. the offset will not be fully realized, so offset/loft wont work either.

Also note that this is not for wild, topological stairs (which may or may never be used/built/whatever), but is for using very controlled geometries to create stairs which someone on a cane might use.

1. Create staircase geometry (lines). JOIN them all together as one line.

image

2. Manipulate by the ROTATE/BEND/TWIST commands to desired state.

image

3. Use interpolated curves along the top edge of the stairs, so that the curve your creating follows the curve of staircase. Copy this new curve vertically above and below the stair geometry. Connect these two new lines with single straight line. SWEEP2 the two curves and the straight line to create a surface parallel but larger than the new staircase geometry.

image

4. FIN the staircase curved polyline. Select the surface created in step 3 as the surface as the “base surface.”

image

5. Erase/Delete the construction curves and surfaces to complete staircase.

image

Also know that you can build stairs using Grasshopper, if that’s your thing.

Leave questions in the comments-

Tuesday, April 7, 2009

A Short Criticism of RealFlow

[image[27].png]Just as fitting a round peg through a square hole can yield obstacles, using particle simulation software to model architectural environments can sometimes prove aggravating. I have a few criticisms:

1. The OBJ export always leaves holes in the mesh (same with the LWO export). Even after using extremely fine polygon sizes and using the fill all mesh holes script in Rhino, the model still has holes. Needless to say, you can’t send it through for rapid prototyping…

2. When you insert a mesh, you can’t turn off the mesh for further particle creation: every subsequent scene exports the corresponding mesh, which can take forever. To fix the problem, you could delete the mesh, but then you loose the node parameters set up for both the mesh and the fluids inside the mesh. If there was a way to temporarily “turn off” the mesh object (a la Rhino/AutoCAD/etc.) it would essentially solve the problem. I have a solution for this, but its not very elegant. I’ll try posting it in a later post.

screenshot.2

3. RealFlow has the elegant interface help solution which allows for you to highlight a node parameter  and press F2 to pop up a short help summary of the parameter. However, if you hit F1 a tiny window pops up and, upon closing said small window the whole program crashes.

4. When you close RealFlow, the program acts like its crashing. Not a bid deal, but it makes you feel uneasy about using the software for in-production work.

 

Monday, April 6, 2009

RealFlow and Architecture

imageI’m exploring the use of Next Limit’s RealFlow software for creating fluid, hyper indexical architectural environments. Although such an approach has been done before, I’m trying it out all the same. I think the idea of fluidity and the spontaneity of the Montessori method have too much in common to not try to exploit such a technique.

Modeling architecture in RealFlow is like dating a really crazy girl: sure its fun (for awhile), sometimes it’ll blow your mind, but often time the culmination of the consequence (which is really what Real Flow outputs) is frustrating. Therefore, I’ll be posting up some tutorials and advice to help out anyone else who might be interested in creating the same sort of effect without so much of the heartache.

imageIn Real Flow, the user sets up parameters which then get pushed through an animation and the output is a single frame, selected by the architect, meshed for export, and moved into a modeling software. For using RealFlow in Rhino, see the RealFlow Import tool created by David Rutton (download here).To control the export, access export central by pressing F12. Then simply check the mesh file types that you want to generate when you rebuild the meshes. See a video about file export here.

 

To move about the modeling environment, hold down ALT and use the mouse to move about (similar to MAYA).

There are four main Nodes (or manipulators) in RealFlow: objects, daemons, meshes, and emitters: objects are rigid/soft bodies, daemons influence particles during animation, emitters emit particles, and meshes mesh the particles according to very specific parameters. There are four main parameters (among sixty or so) which are key in controlling the fluid mesh: polygon size, filter->relaxation (after filter method is set to “yes”), blend factor, and radius (thanks Gnomon Workshop). All values are scale dependent. Change and rebuild the mesh to see the results.

Other than that, I feel that the interface is fairly simple, comparable to programs like Google SketchUp or the new Rhino OSX interface. You can script fluids, but with what I am working on this would be overkill.

Anyway, here’s a few screenshots to give you an idea of the software’s potential:

Untitled (3)

Untitled 01

Untitled 02

I know this is brief, so if you have any questions or something to add, post it in the comments-