To quote the help file,
“If multiple elements (such as walls and/or lines) are joined in a continuous chain, you can select the entire chain. The chain can include different types of elements.”
In order to accomplish this you need to highlight the element and then press tab to select the entire chain.
This functionality also works on repeating details.
Where this breaks down is when you try to do this with line based families. It just doesn’t work, although it seems like expected behaviour. I filed a suggestion for future product improvement to Autodesk and they responded with, you can do this. A few emails and videos back and forth ended up with Autodesk confirming what my near broken tab already knew. They did say that it should absolutely work so let’s hope to see if this will get fixed.
The Revit Jedi posted some great news about AutoTURN – they finally made a Revit version.
I used this on a Revit project a few years ago. Export the site to cad. Use AutoTURN. Strip the file down to just the turning lines. Create a Revit family. Link in the cad file. Trace the lines. Delete the cad file. Not the greatest workflow, but that’s the only solution there was at the time.
They will be having some live presentations and you can register for them at the AutoTURN website.
I know we’ll have a few designers that will be very happy about the news.
Last week I tweeted about how we’re dealing with family naming conventions. Not just Architecture, but all of the other disciplines as well… S/M and E.
I started with the prefixes based on the AEC(UK). Version 2.0 has their preferred prefixs omitted, but they were originally in version 1.0.
Read the full article…
A final 2013 version of the Level of Development (LOD) Specification came out on August 22.
The last few weeks I’ve been up to my eye balls with OmniClass and defining it in our content. With Omniclass on the forefront of my brain, this release was quite timely. I only had time for a quick flip through (I like pretty pictures) and I noticed there are still some gaps, but it’s a pretty good start for a framework. If they ever decide to pull the information out, instead of shoehorning it into the graphics LOD, then they’ll be seriously cooking – Heisenberg style.
I’m starting to wonder why it took me so long to hop on the twitter bandwagon. There is so much great information being discussed and shared amoungst some of the Revit community that you may or may not see in the blogsphere.
Luke from What Revit Wants posted how you could transfer just one View Template from a project into another project using Whitefeet Tools to find the element id.
Harry from Boost your BIM steps up to the plate and creates a macro for 2014.
Dima of db Stuff shared a post about the Revit Lookup Tool which you can use to find the view template element id.
I don’t know how many times I just wanted to have the ability to transfer just one View Template. Not all of them, just one. This is great stuff.