Hide Workset Backup Folders

If you ever work on a project where there quite a few central files it can be bothersome that the _backup folders that Revit uses are presented first in the dialogs that provide access to files. I've found that I can use the "Hidden" file flag to get rid of them assuming I can live with my Folder View settings assigned to hide hidden files and folders.

In the properties of the Workset project's backup folder I check "Hidden".

Then in the settings that govern the display of files and folders in Windows Explorer I use the "Don't show hidden..." option.

Personally I find I need to be able to see hidden files or folders fairly often so it ends up being a bit annoying when I've made the change. I tend to flip back and forth and decide how long I'm going to be working a certain way before committing.

Something to consider...

One Minute with a Pipe Trap

Placing a pipe trap can be counter-intuitive or maybe just awkward until you "know how". The pipe trap family is built with the origin at the vertical or riser connection. That means you need to attach it to the bottom of a riser, the bottom of the pipe that is leaving a sink for example. Want to watch? It's just about a minute...

If you'd like to avoid placing pipe traps entirely you can consider incorporating them into plumbing fixture families that use them. Just do all the subtle plumbing work under the counter in the family and put the connectors at the wall face. I wrote a post that discusses the concept of rough-in families if you're interested. These are the links:

First mention of Rough-in Families
Follow Up Post

Tag Slope of a Ramp

We can apply the Spot Slope annotation to a ramp but it isn't very useful because, while Revit does acknowledge the ramp element, when you attempt to tag it you see [no slope] (image using 2014).

Alfredo replied to my previous post with a tip in his comment:

If you first place the spot slope tool on a floor and then move the slope annotation to a ramp, it works!

In this image I've dragged a slope annotation from a floor element over to a ramp element and it recognizes the ramp's slope!

Definitely quirky and subtle but at least it is possible after all. A word of caution, it will probably be necessary to check the slope value before printing, for example if Revit regenerates information because the ramp is altered. The tag could could start to report [no slope] again. Fwiw, in my casual testing so far it hasn't broken the slope value even after altering a ramp's parameters. Your mileage may vary...

Revit 2014 New Categories in Schedules

Earlier this month I mentioned that we can create schedules for grids and levels. Those two categories are just a few of the categories that a schedule can see now.

These additional categories: Generic Models, Entourage, Structural path and area reinforcement, Structural Fabric Area, Structural Beam Systems, Detail Items, Pads, Levels (see previous post), Grids (see previous post), Architectural Columns and Roof Soffits.

In addition to new categories we can also include the parameters “Phase Created” and “Phase Demolished” in our schedules of model elements. It has been frustrating that such an important aspect of Revit has been overlooked for so long in schedules. Glad to see it is overlooked no more...

Our Model is Clash Free

Offering a "clash free model" is a bit like the car ads on television that offer a 100k car for $299/month. When we read the tiny print we realize that the monthly cost is more like $1600/month and mere mortals won't qualify for the financing terms. Like the car ads, we have to carefully declare/define what a clash is. What sort of clashes are acceptable (and therefore not considered a clash) and those that are not (and therefore are a clash).

One simple example, pipes pass through walls. If they don't cut a hole in every wall at every location where a pipe intersects with a wall then technically we've got a clash. If it is a poured concrete wall that requires a sleeve it is a bigger deal (even bigger deal if precast) than a wood/metal framed wall with gypsum wall board. By the time we are done defining clashes our client and/or team will feel like they are getting "nickel and dimed" to death. ...and that's just for our work...

We can't offer a clash free model if everyone else working on the project isn't working toward that goal themselves. Our model might be "perfect" (according to our fine print) but if they aren't coordinating their work with ours...and vice versa...we'll still have clashes. It's not a one way street.

It is also a moving target as a project moves through design phases. Are we promising "clash free" when people start swinging hammers or is it clash free within two weeks after receiving an architect's model, at the end of each design phase?

"Clash Free" - It's a worthy goal and one every client and project team would love to achieve. It's not possible without considerable commitment by everyone and can't be achieved in a vacuum by one part of the team. In my view someone casually offering "clash free" suggests to me that they may not have enough experience yet. Anyone who has been part of weekly clash review sessions can attest to it not being a trivial matter.

It seems to me that's just the sort of promise that keeps lawyers busy...

Three Minutes with Floor Sloping

I wrote a reply to a thread at RevitForum.org the other day so this is really just an echo. In the context of choosing a method for sloping floor slabs (or roofs for that matter) see which approach best fits your current situation.

1) Slope Arrow - This is very effective when you know what sort of offset is required from known points but they are not necessarily at the start and end edges of the slab or in the same direction as any slab edge. Slope is defined by the location of the tail and head "endpoints" of the slope arrow. Revit will slope the entire floor according to the offset/slope parameter values you provide, between those points. It is perhaps the most versatile method other than shape editing but it is also a bit harder to become comfortable with.

2) Define one edge as slope defining - This is very easy for slabs that slope consistently overall in one direction, from one edge, and you don't really care where the other edge "ends up", it is what it is. You just pick one edge, set a slope. It is just like roofs except we are limited to one edge defining slope with floors.

3) Defines Constant Height - This too is very easy when the start and end edges of the slab also define the floor's lowest and highest elevations (and what we see as the slope value isn't the priority). You just set two parallel floor sketch lines to the appropriate elevation values, whatever values define the required offset.

Fwiw, for structural floors/roofs - Pick Supports (shape editing) - This will slope a roof according to the structural elements you select.

I took a few minutes to record a video of each approach, embedded here. It also touches on using the cantilever settings to extend the edges of a floor slab beyond the structural support members.

Point Clouds in Revit 2014

The underlying engine for Point Clouds has been redesigned and implemented in Revit as well as in other Autodesk products. This effort is the result of integrating other technology acquisitions Autodesk has made (Alice Labs primarily and RealViz) in the past year or so. You’ll also want to check out Autodesk ReCap when you get a chance, image below.

The new point cloud engine uses RCP/RCS formats. The RCP format is a project file while an RCS file is a scan file. A RCP file is a group of multiple RCS scan files. If you have raw data in other acceptable formats Revit will index it in the background and let you know when the indexing is complete. It is also possible to run the indexing apart from Revit using Autodesk ReCap which is included as part of the Building Design Suites (image above).

There is a command line approach available too, using the “AdPointCloudIndexer.exe”. This application is stored along with other installation data in the Program folder. Ben Malone (BIMopedia) and Luke Johnson (What Revit Wants) wrote about this on their blogs shortly after 2014’s release. This is a link to Ben’s original post.

We can now control the colour mode for each point cloud import using Visibility/Graphics.

They enhanced Revit’s sensitivity to points and planes within the point cloud data. This should make it easier to sketch model elements using the underlying cloud data. Revit will detect planes that are perpendicular to the current work plane and very close to the cursor. Zooming in the view will cause Revit to reset the view and it will be necessary to detect a plane again. Snapping directly to point cloud data is a low priority in snapping order. Planar snaps are the initial focus for detection. You can use the TAB key to cycle through other possible snap options.