Thursday, March 26, 2015

Revit mEp - Design Master

I've been hearing good things about this add-on for Revit from Design Master.


If you're doing electrical work then you ought to have a closer look at it.

It has a tab for HVAC but it appears to only support AutoCAD for that, for now?

Wednesday, March 25, 2015

SW Named Linestyles

Have you noticed the appearance of linestyles in your project that look like these?


This means that someone has begun using the Site Designer tools. Even if there are no Site Designer features in use the fact that they are there means at least one person has started a Site Designer command. If there are Site Designer created features then you'll also find related sub-categories under the Mass category.


Tuesday, March 24, 2015

But You've Been Trained

Tom Nichols wrote this paragraph within a blog post about what it is like being a professor. This part resonated with me because often people attend a training session so now they are trained and in some way that is equal with being fully competent now. Three days in training, five days...a month...

Tom Nichols writes:
... "It doesn’t work that way. Education (as opposed to training, a distinction almost no one bothers to make anymore) takes time. It requires reading, writing, discussion, and reflection. It is a cumulative process. You cannot liquefy it and pour it down someone’s throat in a day, no more than you can eat all of your meals for a year in a single week." ...

You've sent your staff to be trained. Does your plan recognize education too? It was/is your money and billable time...

You've been trained, are you focusing on your education too? It's your career...

Wednesday, March 18, 2015

Web Update 7 is Innocent

A quick follow up post. I was wrong. What I thought was caused by the update is actually caused by the Snap setting Snap to Remote Objects being off.

I must admit it is a bit mystifying since I never turn it off or at least I can't remember I time when I wanted to nor do I remember doing so. Regardless when support gurus Trey and Danny challenged me with their questions I found it was off.

Fwiw, I'd prefer that it didn't impact grid and level placement editing behavior regardless.

At least it prompted me to deal with a couple hours of windoze updates I'd been postponing.

Web Update 7 Killed Grid Level and Ref Plane Alignment

I was wrong, the update is innocent, sorry. The culprit is Snap to Remote Objects which was off.

Uh oh, I installed the recent Web Update 7 and now grids, levels and reference planes don't see each other like they used to. Existing grids and levels work normally. It seems to affect new elements when you attempt to place them in alignment with others. For example, try to sketch new parallel grids. Normally we see a green dashed graphic that indicates alignment with an adjacent grid end. I don't see this anymore. I also don't get the locked relationship between grids. Same for new levels.

If you copy them they'll recognize their alignment and behave normally unless you unlock that and alter them individually. Then they'll forget they can see (should see) each other. We can get around it, with grids for example, until they patch it by sketching a reference plane across the grid ends and dragging them so they touch the reference plane. The grids will start to behave normally as long as we don't separate them again.


Well at least a couple replies suggest I'm crazy but here's what's happening to me.


Tuesday, March 17, 2015

Be Careful Creating a Central File in 2015

A thread at Autodesk's Revit User Community Forum caught my attention yesterday. It seemed as though the culprit was something I've written about before, that user's were accessing the project via different shared resource paths. After digging in a bit deeper it turns out the issue, or at least an issue, is that Revit 2015 is more sensitive to how we navigate to the a shared resource.

This is what happens when I browse to a shared folder via My Computer and click on the Drive letter S:


This is what I expected to see (disregard the project name, I was experimenting with being logged in and out of A360 too):


A clue or warning you can watch for is what Revit displays at the top of the Save As dialog.


If you see the drive letter in the description then you'll likely end up with that as your path. I believe you should only see the folder the central file will be in if you are mapped correctly.

It is my habit to always use Synchronize and Modify Settings before closing the Central File, after creating it. As such I can see what the path that Revit captured is. When I notice that it is wrong, like the first image above, I can fix it, get the correct UNC path recognized instead by taking these steps (see the image that follows too):
  • Close the Central File (after noticing the wrong path reference)
  • Create a local file (before any other users start to work)
  • Use Synchronize with Central
  • Click Browse and click Browse again in the next dialog box that opens
  • Select the Central File by browsing to it via the shared resource path instead, type it in directly if necessary.
  • Click Open
  • Click OK (the correct UNC path should appear now)
  • Click OK (The path is fixed)

If you are creating a central file be very careful about how you browse to the project folder. Verify you have the correct path established before letting users begin working on the project.