BILT Speaker

BILT Speaker
RevitCat - Revit Consultant

Wednesday, 30 December 2015

Revit Octopus - RTC 2012 NA Competition Winner

Octopus Hotel, Hainan
Back in 2012 this drawing was the Innovation category competition winner at RTC North America (Atlanta).  It was meant to represent the design process (on yellow trace paper and in Revit) of the Octopus Hotel designed by PTW in their Shanghai office.  The initial design modelling was done in Sketchup and 3D Max, then 2D documented in Autocad.  Then we had to start really documenting it in Revit to make sure the organic shapes were buildable. . . . .
The first task to solve was the plan layout - making sure that each hotel wing (octopus leg) had regular radius curves with smooth transitions between concave and convex curves, with a minimum number of different shaped hotel rooms.  Trying to do that in 2D was painful - lots of reference planes/lines and aligning centre-points of arcs with each other, and plenty of calculations.  If anyone made a change to the layout you had to start all over again.
To improve this process in Revit, I decided to make a flexible component that would place a number of tapered hotel rooms along an arc.  Initially I tried a line-based generic component that required the user to click a start and end point - that worked fine for linear hotel rooms.
As soon as I tried radial arrays, it became a nightmare, as they are really hard to control with parameters.  As adaptive components had recently been introduced to Revit, that seemed to be the way to go - but then I realised that they do not allow the Array command.  'Repeaters' to the rescue!
All of this required a lot of complex fomulas and trigonometry, even with using Repeaters - particularly as I wanted the end user to be able to dynamically change and schedule room areas, widths and the radius.

Area calculations for segments
Eventually I managed to create an adaptive component that had two curves (concave and convex), forming a corridor double loaded with rooms.  This was fully parametric in terms of being able to stretch the start and end points and change the two radii as well as critical room dimensions.

This would have made the design process so much easier than relying on several different programs and yellow trace paper!  Creation of this component was fully documented in my handout for the RTC events in 2012 (Australasia and North America).  When I get a chance I will try to post some of the techniques on this blog.

The 2d planning was only the start of the challenges - each hotel room had a balcony that had curves in plan and in elevation, so that really challenged Revit's ability to create organic geometry - but we did succeed in building a convincing 3D model in Revit.

Octopus hotel wing


Of course, now you might be tempted to use Dynamo to build this sort of complex geometry.

Friday, 4 December 2015

Revit Stair Sketch Tool

I have noticed that most people who want to create a non-standard stair in Revit will resort to the old stair sketch tool.  This is a really bad idea for a number of reasons.  I only know of one good reason for doing so (more on that later).
The old Stair by Sketch tool was left in Revit as a 'safety blanket' for those worried about the new Stair by Component tools.  In reality the component stair tools are much better than the old tools despite the many glitches and shortcomings.  [Edit: in Revit 2018 the old Stair by Sketch tool has finally been removed]

So, what happens if you want to create a non-standard stair that cannot be done using standard components?  A tapering stair for example.  Well, the component stair has its own sketch tool:  the icon looks like a pencil with curvy line (highlighted below).  That means you can sketch just one component - say a run or landing (both have the sketch option, but Support does not).

Once you start a component sketch, you get three line types, much like the old stair sketch tools:
  • Boundary lines
  • Riser lines
  • Stair path

Once you start using these line tools, you will see that they work quite differently - each line has to be created (drawn or copied), unlike the old sketch tool that created all the lines when you placed the central run line.  This may seem like a retrograde step (pardon the pun) but it is no great hardship, particularly as there are so many other advantages.

I usually find it is easier and quicker to create a standard run or landing component that approximates what you ultimately need - then convert it to a sketch.

It will give you a warning that the process is irreversible.  Take heed, because once it is a sketch it will always be a sketch, unless you delete and replace with a component (and risk losing hosted elements).

Once a component is converted to a sketch, you need to select it in order to then edit the sketch - this seems like a needless step, but in fact it is logical.  It caught me out a few times, wondering why my converted component did not look like sketch lines.

Once you are in sketch mode, you need to remember that adjusting the central Stair Path line will not affect the riser spacing - it is just another line.  The Finish Sketch command is much more forgiving than the old sketch tools, which were very temperamental.  I will cover more detail on the rules of what the sketch command will or will not allow, in another post.

Stair by Component = Good;   Stair by Sketch = Bad

Why is it bad to use the old sketch tools?  Here are a number of reasons:
  1. Using the old stair tools means that you are missing out on new features like stair numbering - despite the shortcomings, they are useful.
  2. The old sketched stairs have the path arrow built into the stair, which means limited control on where and when they show up.  It also means very limited control on the stair arrow style.
  3. It is really bad news to mix old and new stairs together in the same project because the annotation can be extremely inconsistent between the two - particularly for stair path arrows.  This leads to confusion and messy drawings.  Refer to Stair Paths Arrows for more detail.
  4.  Stair by component gives much greater control and options for changing the number of risers, the height and location of landings etc.
  5. Stair by Component allows stair runs to go over the top of each other - useful for spiral stairs more than 360 degrees, or for stairs with 3 runs per storey.
  6. Sketching individual components (run or landing) allows other parts of the stair to remain as components, with all the benefits of that.  Stair by Sketch means the whole stair is one sketch.
  7. The list goes on . . . 

Reasons to use Stair by Sketch

There are a couple of reasons for reverting to the old stair tools, but hopefully these will be dealt with by Autodesk fixing the bugs in the component tools:
  1. "Show Hidden Lines" does not work on component stairs
  2. There are many shortcomings with the Stair Path tool for adding stair arrows, including:
  • Cannot copy and paste stair arrows between views
  • There is no "Tag all stairs" command for adding paths to multiple stairs at one go
  • Duplicating a view will not include stair path arrows unless you duplicate with Detailing, in which case you get all the other annotation.
The moral of this story is that the reasons for using Stair by Component sketching far outweigh the minor benefits of sticking with the old Stair by Sketch tools.  I wish that Autodesk would fix those bugs and remove the old tool so that people would stop using it.