Troubleshooting - Start an Email or Forum Post

I find it helpful to resolve an issue by starting to write an email or forum post (or a blog post) to ask for help or complain about it. Trying to write an explanation for what is happening so someone else might be able to help me focuses my thoughts. Very often I find it isn't necessary to finish writing.

The answer presents itself during the writing.

Next time you're puzzling over something, consider writing down what you think is wrong and the solution may arrive as you type.

Worth mentioning that a short break can also help a lot. Grab a beverage, talk to someone else, or stretch your legs; or all the above. The change gives you chance to work on the problem in the background of your attention.

Revit Coordinate Systems Video

A lengthy exchange at Autodesk's User Forums about this subject reminded me that I've meant to create a short video to describe how they relate to each other for quite awhile. This morning I saw our cutting boards drying next to the sink and realized they could serve as metaphorical coordinate system planes (Project and Survey) work in Revit. I am curious if readers find it helpful.



The original post at the forum dealt with a few projects that had been modelled very far from Revit's Internal Origin/Startup Location. I looked at one of the project files and found the Survey Point and Project Base Point had been moved very far away while unclipped. The modelling started there, really far far away. They started to experience some of the negative symptoms that can occur and started looking for solutions...thus the original post. The short answer is they needed to move their model closer to the origin. No other way around it.

Clipped or Un-clipped - That is the Question

The question asked: "Steve, should we leave our coordinate system icons clipped or un-clipped?"

My Answer: As we know, the Project Base Point (PBP) and Survey Point (SP) can be un-clipped. If they are untouched we'll find them clipped.

When these are clipped the symbols for each of these are attached to the coordinate systems they belong to. That means moving either while clipped will alter the coordinate system. If this is done unintentionally, or by someone who does not realize they have been adjusted intentionally already, the coordinate system(s) will be changed.

Therefore I'd say it is not unreasonable to leave these in their NOT clipped or un-clipped state at all times, especially after they have been adjusted intentionally to align models or survey data. If they are not clipped then accidental movement of these icons do not alter their related coordinate systems. It merely changes the symbol's position relative to their coordinate systems.

I regard these symbols as markers or annotation when they are not clipped. In this state they are harmless to our coordinate machinations. Clipped they pose a danger to our careful adjustments to align models and site information.

My opinion: Keep them Not clipped, un-clipped.

Add a Comment using Synchronize and Modify Settings

Whenever we need to use Synchronize with Central (SwC) I advocate for using the button for Synchronize and Modify Settings every time.

Doing so allows Revit to present us with the Synchronize with Central dialog.

I encourage everyone to take a moment and type a brief description in the Comment field provided. What motivated you to use SwC just now? That's the gist of what should be recorded there. I find that people are more receptive to making a habit of it once they see it can prove to be very useful to just about everyone working on the project.

We can review the comments anytime we choose to, even if we don't have a project open yet. That means that anyone who can at least fire up Revit can review project comments even if they don't really need to do any work in Revit.

Yes, the Show History button on Collaborate ribbon is awake even if no project is open. Click Show History, browse to the location of the relevant Central File and click Open. The comments are presented to us like this.

I doubt it is hard to imagine how having everyone on the project team recording comments (time stamp and username are stored automatically too) can be helpful for diagnosing issues, checking the status of tasks, and even a quick review of user activity on a given project file. It will also become obvious who isn't playing along pretty quickly.

I also recommend that we never use the other button for Synchronize Now (that's why I put the red X on it in the image above). It doesn't present the dialog so there is no opportunity to store a comment and equally important is that is does not relinquish User Created worksets automatically.

If you pay close attention you'll notice that all of the other kinds of worksets are automatically checked when the Synchronize and Modify Settings dialog is open. Those other worksets are relinquished with Synchronize Now, not User Created worksets though. If you use Synchronize Now and you've ever been accused of retaining ownership of these worksets...that's likely why.

If it helps:

Green Arrows in Circle SwC = Good!!
Lighting Bolt SwC = Not Good!!

If you're interested in taking a peek at Kinship's features you'll find that these comments can be reviewed at will with just a browser.

Revit Viewer and Worksharing

Reading a thread at Autodesk's Revit Community forum David reminded me of the quirky issues related to the Viewer when worksharing is being used. If someone launches Revit Viewer and then tries to open a project that has enabled worksets they'll get this warning.

When the file is opened and they try to print, export or save they'll get this warning even though they haven't DONE anything...but Revit has made changes to the file in order to create a new local file.

Okay, let's follow the instructions in the first warning message. We'll open the project using Detach from Central. Sorry, "Do not pass Go, do not collect $200". That process also changes the file. Still no export, save or print for you!

The ONLY way we can use Revit Viewer to open a project with Worksets enabled is to open the Central File itself, by un-checking the option to Create New Local. This means that user is now working on the real central file with Revit Viewer.

If you do this you will likely encounter several of the messages shown in the first image. The projects I've done this with all have linked files and it seems to pop up for each link (RVT) used and once more if there are any linked/imported DWG files.

To the good, they won't be able to synchronize their work nor will it prompt them to Save when they close the file. They won't be able to edit much of anything though because they can't borrow elements. The notion of using Revit Viewer to poke around the model, do some experimental stuff within the model is off limits to Viewer mode. We are able to print or publish to DWF, because those formats don't create an editable version of the data/model.

It seems to me that the notion of Revit Viewer for workset projects is fundamentally flawed, if we're thinking of it as a way for Project Managers to poke around, do anything other than JUST LOOK at views. If we'd like them to be able to cut a section view or hide things, do anything that requires temporarily borrowing something, that's all off limits to the Viewer.

For that we'll have to show them how to use Detach from Central AND to be careful not to save that file overwriting the original project.

Create a Local File - How Often

Every time...

I no longer reuse Local Files. My attitude and habits have changed a little over the years. I wrote this POST in 2008 and then THIS on in 2011. I've touched on the subject many times within the context of other workset related posts.

I treat my Local File as ephemeral...temporary... I make use of the Open File option Create New Local each and every time I start working on a project again; yes even if I just stopped working earlier to have lunch or join a conference call.

Revit 2017 - Enabling Worksharing

The process for enabling worksets has changed with this release because Collaboration for Revit (C4R) has been incorporated into Revit directly. This allows someone to subscribe and begin using it quicker. They might even be able to do so without any (or much) EyeTee intervention.

The first evidence that there is something different is on the Collaborate ribbon tab; there is a Collaborate button next to the disabled Worksets button. There is a new Communicate panel too.

In the past enabling worksets began with clicking on the Worksets button but now we start by clicking on Collaborate. This takes us to the fork in the road necessary to permit sharing the project via A360/C4R whether we are able to use it or not, just in case. If the file hasn't been saved before clicking Collaborate we get a message asking us to do that.

Then the Collaborate dialog appears asking us to specify which method of sharing the project we need; Collaborate within your network or Collaborate using A360.

When we choose Collaborate within your network Revit enables and creates two User-Created Worksets called Shared Levels and Grids and Workset1 (like in the past) but it doesn't open the Worksets dialog (like it used to). This allows us just to get on with our work using the Active Workset (Workset1 by default). If we need to create additional worksets then we'll find the Workset button is enabled, just click it to open it (Workset dialog, as in the past.

The Communicator button is tied to using C4R. It is a separate window (dialog) that can display information about your project team activity, if you're sharing the project using A360. Imagine concepts from Worksharing Monitor combined with Instant Messaging features and that's what you've got. FWIW, it used to be able to dock inside the Revit UI but it doesn't do that now. If you've got two or more monitors you'll probably prefer it on one of them instead anyway. This is what it looks like if I'm not logged into A360 and not using it to share this project.

At some point we'll need to Save the file and like in the past we'll be warned that this is the first time we've done that since we enabled worksets; click Yes.

Remember, if you'd like to set the default Open option to Specify remember to use Save As instead of Save. You only get a chance to do that with Save As. This allows us to choose which Worksets Revit should load before it opens the project entirely. This can have a significant impact on how long it takes to load a project.

At this point we are still working in the Central File, which isn't practical to share the project nor is it advisable. I can determine that by looking at the Save icon on the Quick Access Toolbar (QAT), it is disabled and the Synchronize and Modify Settings button next to it is enabled. The project's file name listed on the Title Bar doesn't include my user name either. By the way, we need to SwC to relinquish our ownership of the User-Created worksets properly. The only way to do that is to use SwC (Synchronize and Modify Settings), via the dialog that appears. The Synchronize Now button does NOT do that.

Now that worksets are enabled and relinquished we need to close the project so the team can get started by creating their Local Files. When I browse to the Central File to start work I need to make sure that Create New Local is enabled and double check the Open option is assigned to Specify.

Remember doing so will cause this dialog to appear before Revit begins opening the project further.

Okay, now get to work; in your Local File!

Warning Messages and Profile Families

Profile families are loadable (component) families but they don't exist on their own in projects. They are either used to create solid and void forms in the family editor, in-place families in projects or applied to System Families in projects. For example, a Railing, Sweep, Reveal and Floor Slab Edge can all use a Profile family.

Occasionally I'll get a generic sort of warning regarding the system family I'm trying to make, telling me "Sorry Steve, I can't make this thing for you".

Quite often the reason Revit is complaining is because I was sloppy making the Profile family. You may recall I've written about good sketches and bad sketches in the past.

Regardless the error message could certainly be written better; to mention that such an error may be related to a profile that isn't created properly. At this time, the error trapping process may not be able to reach deeply enough into the sketch mode process, for example like we use to create a Floor Slab Edge. Regardless, there is no reason the error message couldn't mention a common culprit, something to prod us to look more deeply for.

Technically the error is in a component family and then evaluated as part of a system family that references it. In a sense it is too far removed from the active operation for Revit to properly recognize what's wrong precisely. Therefore I think it would help if, while saving a profile family type, Revit tested it for proper closed boundaries to help us catch errors while editing the family. Revit does this when we attempt to finish a sketch for a solid or void form. Perhaps it could be a button on the ribbon? Something like Test Profile.

Help us help you Revit!

Did you Load a Family - Synchronize NOW

ALWAYS use Synchronize with Central (SwC) immediately after loading new families or types (or duplicating system family types). Don't place any instances until you have!

This post is tagging on two earlier posts on the subject of loading content, restating the punch line to emphasize it on its own. If you're inclined to just take my advice just reread the first two sentences and behave accordingly. If you're a bit curious, need more convincing, you can read the FIRST and SECOND posts for more background info.

Purchase Advice for a Fellow Revit User

I received a message the other day asking me for advice; that classic conundrum Mac or PC? I don't have a Mac and rarely get to use one. I do know quite a few people who love their Macs, likewise for PCs. I thought I'd share some of the message here and see what sort of comments it might spur, advice or otherwise.

He writes:

I am hoping to get some advice from a fellow a Revit user about a pending purchase decision.

I have been using Revit now for almost 4 years, even somewhat addicted in spite of it's occasionally awkward ways. A client has offered to buy my next computer and has offered up a spec for an Intel PC. I'm using a 2009 iMac w/ 8 GB RAM, Intel 2 Duo 2.93 with 6 MB L2 NVIDEA MCP79. I run Revit using Parallels. I recently found out about maximizing the RAM in parallels and accessing the 2nd core processor and it has helped to speed up Revit.

I was having some performance issues (slow response) using materials palette. It could take 30-40 seconds to open up and I did have some wicked crashes. But after making the adjustments I have found it quick, responsive and stable. I was having 45 minute restarts but now it works smoothly. I have heard of people running bootcamp but I can't at this point because my partition is too small and I'm not eager to reformat my current setup.

I'd prefer to stay with a Mac but I get that Revit doesn't run on the Apple OS. Should I stay or should I go?
Btw, I also got a quote for a Boxx PC but it's expensive.

Looking forward to your thoughts.

What say ya'll?

Type Catalog - Family Type Parameter and Missing Spaces

This is for the Department of I could kick myself or Dept. of why can't I remember this.

These are two images of the same Type Catalog, one works and the other doesn't. The key location of the issue/difference is marked in yellow. This first one won't work.

Two little spaces on either side of the colon, like this: Family Name : Family Type.

Note to self, remember this next time around knucklehead!

Worksharing Display - Owners

The first thing I do when a project is open, to get a sense of things going on around me in the model, is to toggle on Worksharing Display - Owners (see image). That gives me a quick snapshot of who else is working on things around me.

If I see a color on anything I thought I'd start working on then there is no point attempting to edit those, I'll just get a warning from Revit in response. The mere presence of colors indicate other people are around, in this context. Hovering over one element brings up a larger tool tip than the usual information we get, including which person is currently editing it.

I use the Worksets option for Worksharing Display just to see if things are obviously assigned incorrectly. Again, hovering over any element tells me what workset it is assigned to in either the normal tool tip (first thing displayed, unless Design Options are involved too) or the expanded one for Worksharing Display.

I think most people forget about or overlook the Gray inactive worksets option too. That helps me cope with my nemesis Active Workset because it reminds me which workset is active because the things around me are either bold or not (see image).

Prompted by a reply to a thread at RFO.

Worksharing - Loading Content Part 2

In my previous post I recommended a point person be assigned to manage the loading of content for a team. That might sound like a beauracratic minded recommendation. Not me at all. It is more a matter of self preservation, wishing to avoid having to fix the resulting duplication before it becomes a bigger problem. As such there is a another minor measure we can take to help catch the issue when it occurs and fix it.

Always use Synchronize with Central (SwC) immediately after loading new families or types (or duplicating system family types). Don't place any instances.

If we can't get a single person to manage this loading then using SwC immediately afterward will increase the odds that a warning message will appear as soon as the transaction is completed. This does assume that we all develop this habit. If the warning appears than we need to examine the new family(ies) and or type(s) in the Project Browser and resolve the issue.

The goal is to avoid creating the duplicates and even more importantly using them in the project.

Who's Your Daddy? Logical Relationships in Revit MEP

This is an echo of a post from October 2011. I emphasize this concept in every session I do that is focused on Revit MEP and I think it's worth stating again.

Revit MEP elements, like electrical panels and receptacles or HVAC equipment and diffusers, have a Parent - Child relationship. Revit calls this a Logical Relationship. In contrast the physical relationship is described with duct/pipe but there is no equal for electrical systems. It could be with conduit or cable tray but no such relationship exists yet.

The other day we were chatting about this in class and I blurted out "You know, like who's your Daddy?" I was kidding but one of the guys said that it will actually help him remember to start with the "child" part of the relationship. For example, you start with a receptacle and create a power circuit (system), then choose the Daddy, the electrical panel it gets power from. This relationship continues up through the grandparents, great grandparents etc. When everything is assigned correctly you can see this family tree in the System Browser.

So if it helps, when you are creating relationships between elements with Revit MEP, just remember "Who's your Daddy"! START with the child and then assign the Daddy.

Preserving the Active Workset

The Active Workset is a user setting. We can each work using a different Active Workset.

However there is a circumstance where I can affect what the Active Workset is for others.

When I Synchronize with Central (SwC) my Active Workset will be the one any user that OPENS the project afterward will see. That is true until another user uses SwC. Then anyone who creates their local file after them will inherit their Active Workset...and around the bush we go.

It's important to remember to check the Active Workset as soon as your Local File opens.

Keep in mind that other users that are already working in the file will not see a change, their own preference will remain the same. It affects anyone who creates their local file later.

We can agree as a team to always use SwC with a specific Active Workset in play. I can't really expect that to happen every time if I have difficulty remembering to set the Active Workset correctly for my own purposes. I just try hard to remember to check the Active Workset setting before creating any new elements AND especially as soon as I get my Local File open.

We can also remember to take advantage of the Gray Inactive Worksets feature (see image above) to help make it more obvious that we aren't using the correct Active Workset.

Withdraw your Editing Requests

In the past I wrote about how you can become the unwitting or accidental borrower of elements when you create an Editing Request but then close your local file before the request is resolved.

Therefore it is a good habit to Retract (withdraw) any Editing Requests you create before closing your Local file. If you form a habit of creating Editing Requests then also form the habit of Retracting any that are still pending when you leave for the project for any reason.

This is not a request...

Type Catalog - Just say NO to Load Into Project

If you are working on a family that uses a type catalog then these two buttons are bad!

Bad buttons!

Youz buttons are buttons non grata.

The same is true for the Edit Family button and right-click Edit Family option. Don't use them on families that use a Type Catalog because all the types that are in use get loaded into the version of the family that opens in the Family Editor. That's kind of counter productive.

Revit 2016 Trial Versions - Do Not Install the Wrong Version

A post of caution - If you are tempted to download a trial version of Revit 2016 please keep in mind that it comes in three trial flavors:

• Revit
• Building Design Suite (BDS) Ultimate
• Revit LT

Let's imagine you're anxious to check out the new release and just download and install a version that you don't already have a license for with the expectation that you will just activate it for your particular license later.

PLEASE DON'T DO IT!

If you do install a version you don't own then you'll get to REMOVE that version and INSTALL the version you really need instead.

The installation is perhaps the least of it since the download time (the installation files are large) can be significant so I'd be really sad if I downloaded BDS Ultimate thinking I could just install it and then authorize it against Premium.

NOPE... uninstall, download correct version and install. I'd be wailing and gnashing my teeth...

Don't go there, wait for your correct version to become available to you via the subscription center. Forewarned is four-armed (as I read recently)...

Username and Local Files

Revit knows who we are based on a simple piece of data, the Username entry here (Application Menu (Big R) > Options). That is usually defined by who logs on the computer. If we log on our computer, then open Revit AND change the Username...Revit preserves this alternate username until we change it again. If we never change this value then Revit just uses the computer's log on username identity. When we change it Revit captures and preserves it for this particular person's log on credentials on the computer.

Using Worksets (Worksharing) this username provides our unique identity to Revit, the Librarian (not to be confused with the TV show or movies). We can't just arbitrarily change our username while we are working in our Local File. If we do that we'll be greeted with an unpleasant message when we attempt to use Synchronize with Central.

We can become convinced that changing the username is permissible because Revit doesn't complain until we attempt to use Synchronize with Central. It's also easy to think it is reasonable because when the file contains changes that have not been synchronized yet we see this message when we attempt to change the username. When Revit complains and offers the reason that changing the name isn't going to work it implies that there might be an acceptable circumstance.

Fwiw, we CAN change our username freely if we are working in a central file (discouraged). However we won't find that very fulfilling if other users are also working on the project via their own local files. We'll be advised by Revit that it is necessary to use Save As to create a our own Local File first, when we use Synchronize with Central.

We CAN assume any username identity, we just have to change the Username parameter before creating a new Local File.

Damn Revit's Worksets and Worksharing features are fussy!

Echo David Light - Autodesk Revit 2015 R2 Info

This is an echo of what I read on David Light's blog this morning. He's working with Autodesk now and it clarifies which version of the latest release you need to use according to the type of licensing you are using, thanks David!

David writes:

I got some useful information from our Enterprise Support team which I want to share. Its certainly worth being aware of this….

• Autodesk are pleased to announce new Update releases for Revit 2015.The following files will be available for download via the Autodesk Application manager: 2015 R2 (includes UR4 and the latest Hotfix) - Subscription Advantage Pack customers
• 2015 UR4 for regular customers where the license registration is not tied to a subscription contract

Please Note: You have to choose from either 2015 R2 or 2015 UR4 as they cannot be installed alongside each other. If Revit 2015 has not been registered , then you will not be presented with either update.

• Revit 2015 R2 w/ ENU docs - is available via the Subscription Center under downloads

By 6pm EST, September 19th:

• Revit 2015 UR4 w/ ENU docs - will be available for download via AKN (.com). All remaining languages for download via Application Manager, documents in Subscription Center and AKN, will be published within the following week.”