>
Documentation for “Insanely Great Stairs and Railings with Autodesk® Revit®” has been posted on the AU 2009 Website! Link here and another here compliments of Dropbox. Once you download the PDF file, you’ll find there’s a bunch of links right at the bottom of the cover page. The very last link is to the 100MB or so of datasets and sample files.
Disclaimer: you use one of these stairs in a real project you owe me a beer. And not a some crappy American beer designed to be consumed minutes after production and measured in volumes rounded to the nearest cubic kilometer.
I’m talking about one of these:
Preferably the bottle on the far left. Long story – but it’s JamesV’s fault. Buy me one of those and I’ll really tell you what I think about the 2010 UI. 😉
Arch | Tech 
>Artois?
>To quote a young Marlon Brando: "Stella!"
>Amazing modeling techniques, great job. Question though, Rule 2 on Page 8 says not to set the nested family to "shared". How has this setting broken your models before? I just read a post on Duct Duct Pipe that said you should do that. http://ductductpipe.blogspot.com/2009/08/schedule-parameters-from-nested-family.html.
>If you nest a component (which is set to shared) in a baluster family – and then attempt to use that baluster containing the nested/shared component in a railing – it'll only show one 'baluster' element. Which pretty much is broken. ;)Keep in mind – this is just when using the railing functionality with nested elements to distribute stuff along a path. Otherwise nesting with shared parameters in order to quantify assemblies is just fine.
>I know you're just trying to lure me out to Vegas…it's working!
>Is it the stair, or the beer thats luring you James?