We get this call all the time. A Revit user has a view that is showing some of their section marks but not all. Revealing hidden elements reveals no hidden section marks. Other views show the same mysteriously absent section marks, and of course, the section views exist in the Project Browser.
This is because of a frequently overlooked unique property of section views. When you create a section, the scale of the view in which you create the section initially sets the default scale beyond which the section mark will be hidden. In other words, if you create a section in a plan whose scale is, say 1/2″=1′-0″ you won’t see it in any views whose scale is 1/4″=1′-0″, 1/8″=1′-0″, etc.
To fix it, either select the section mark in a view that you can see it in, or navigate to the section view itself and in the Properties palette change the “Hide at scales courser than” value to a smaller scale. I usually go with 1″=400′ myself – I can always hide a section mark “By Element” or “By Category” if I don’t want to see them in a view.
Recently, while digging into a really cool 3rd Party add-on for Navisworks (iConstruct – I’ll be posting more on this amazing tool later), I discovered a rather disturbing feature/limitation/defect in Navisworks. After a bit of Googling I found it mentioned in several forum threads, so this may not be news to hard-core Navisworks users, however…
It only took 3 years, but I finally got around to updating (re-writing, actually), the Worksharing Whitepaper originally posted back in 2011. Up to date for Revit 2014 to include Worksharing Display modes, disabling worksets, central file maintenance as well as setting up a workshared project and worksharing workflow. Get it here.
Have you noticed that selecting certain types of objects in Revit 2014 has changed in some subtle (and not so subtle) ways? Selecting objects like walls (in elevation or 3D), floors, links, pinned objects, etc. may seem to have become more difficult or in some cases downright impossible. Believe it or not, this is actually an improvement that was added to Revit 2014 that, if you haven’t been paying close attention, you may not have realized you have total control over.
I’ve just completed a white paper on the rendering process for Revit models imported into 3ds Max Design, focusing on the lighting settings you need to create exterior and interior still images, including nighttime scenes. I’ve also included a section on best practices for rendering output for both still images and animations, including a section on how to use Video Post to combine mulitple animation sequences into one continuous longer animation complete with transitions. Get your copy here!
I run across this a lot in tech support calls – a feature that was added to Revit 2014 that a lot of users are apparently not aware of. Temporary View Properties.
Frequently in diagnosing or resolving issues with a project, I have the user make lots of changes to a view’s properties. And when we’re done, they’d like to get the view restored back to it’s original state. With Temporary View Properties, it’s simple. Simply select the Temprorary View Properties button in the View Control Bar at the bottom of your view window, and enable temporary view properties. You’ll get a purple border around your window to indicate that they’re enabled. When you’re done jacking around with your view, click the button again and restore your view properties. Viola – all better!
It’s alive in The Lab! On November 20th, Autodesk Labs released the LEED Daylight Analysis add-in for Revit 2014 (Service Pack 2 required). It’s available for free for the time being, but I suspect you’ll need subscription at the very least at some point, or more likely since it’s utilizing the cloud rendering service you’ll burn Cloud Units to use it. It generates a color-coded image in your current Revit view, as well as a Room Schedule with the LEED Daylighting data generated for each room in your project.
Again, it’s free for now. Go to the “Beyond Construction” blog to read about it and download it…
Have you ever tried to get a brick material to map correctly to an arched lintel, or something similar? This seemingly impossible task is explained in the Revit Kid’s blog - it can be done!
Every now and then you run across something in a software application that just makes you wonder what kind of drugs the product designer involved was doing at the time it was developed. For example, who was the guy at Microsoft who decided it was a GOOD idea to turn off file extensions by default? And more importantly is he or she still employed?
Or did they maybe go to work for someone else? Could it be? I’m beginning to wonder…
Full disclosure here before I begin. Paul Aubin is a very good friend of mine. He and I have collaborated on several projects over the years and we’ve also co-authored a book together.
That said, I have to report that he has outdone himself with his latest effort – of the same title as this post.
What’s even better is that he’s done it while addressing a need that has been festering in the Revit world for a long, long time. Do you want to REALLY learn how to create custom families the right way? Read on…