Please Just Say No to 2D Only

If you make a Revit family and it is meant to represent something real, tangible, please don't make it 2D only. In 3D your family doesn't exist and that is usually a bad thing. Everything we put in a building is three dimensional, even wall paper has thickness. If you aren't prepared to model it faithfully in three dimensions, at least use a generic box form that is at least dimensionally consistent with the thing you are representing. If you are documenting clearance zones make it 3d too. You can't use Interference Check meaningfully if it is just lines on the floor.

Resist the temptation to just make it 2D.

Hacking at Railings Again for 3D Grids

An exchange at RevitForum.org discussing 3D grids for 3D views or exporting to Navisworks prompted yet another "hackalicious" thought for Railings. I posted a VIDEO or this video so you can see and hear me discuss the concept. If you want to cut to the chase you can download the example project file (just scroll to the railing section on the page).

Aaron Maller shared some images (in the RFO thread) and concepts behind the line based families they've been using. Seeing them and reading the other posts made me think of railings yet again, because they don't mind curved paths and multiple segments. That and I'm not good with math that involves letters, weird signs or code.

By the way, several Dallas area based RFO members (Dan, Jose, Bob, Tanner, Aaron and me) got together for dinner last night and I mentioned it to Aaron so naturally I ended up writing this post tonight. We went to Taverna by Lombardi. Dan found it because I mentioned I was in the mood for risotto (yum!). Thanks to Dan for getting it organized! Sorry, I digress...

The first thing I did was create a baluster family to show a grid name, using 3D Text. Then I created a profile for the "railing", just a thin rectangle "kick plate" to "trip" over in the model. Once they were loaded into the project I created a new type for each Grid name, you'd need a type for every grid name in the project.

With the the types established I'm ready for railing types. I just created a new railing type for each grid as well. Then it's click click click... adding the matching baluster type to the railing type. Yep, this is the tedious part. It's more fun once you get to sketch the grids...define "fun" though?

Like I said railings don't mind curves so here's a curved grid added in.

Last image is using "nicer" grid stands to identify them, more like the example Aaron showed at RFO.

Listen and Watch my video here?

In actual use, I'd start in a empty project file and link in the project file that has the governing grids in them. Then use Copy/Monitor to create equivalent Revit grids and put the 3D grids (hacked railings) on top, at each level of the bldg. Copy/Monitor let's me open my 3D grid file any time and see if there are any changes I need to be aware of. I just have to provide a new export to .nwc (or .dwg) any time there is a change, and pass along the new file.