Archive for the ‘Warnings’ Category


Revit 2014 performance with VMware

July 27, 2014

I’ve been running Revit on a Mac for some time now. I run it though VMware Fusion and every once in a while things don’t go as smoothly as I would like. Revit 2013 for example had such poor performance I skipped using this release in it’s entirety.  2012 worked just fine and I was elated to find that 2014 worked just as well as 2012.  For the most part I attribute the hit in performance to the emulated video drivers that VMware provides.  Autodesk Revit does not recognize this generic driver as an acceptable video card to run Revit with the “Use Hardware Acceleration” setting.

At some point I played with tweaking the Revit.ini and possibly another file to override some of the settings.  I don’t recall exactly what it was but it made performance even better.

Now, just recently Revit 2014 issued Update Release 3 and I figured no harm could come from what will likely be the last update for 2014.  Well, I was wrong.  I installed it and started working on projects but the program took another performance hit.  Zooming, panning, selecting were all slower.  This lead me to think that my Revit.ini was reset to factory settings.

After digging around for a few minutes on the internet I ran into this post on the What Revit Wants Blog. I followed the instructions to rename the specified file and bam! the performance is now back. I can even turn on “Use Hardware Acceleration”.

I will likely try the same settings for Revit 2015 in the near future.

Your results may vary, I am currently using:
OSX 10.9.4
VMware Fusion 6.0.4
Revit 2014 UR3
Windows 7 Pro Service Pack 1

Revit 2014 hardware acceleration


Ribbon issues for Revit 2012 after installing .Net4.5 (that installs with Revit 2014).

April 18, 2013

After installing .Net 4.5 which is installed with Revit 2014 I experienced some crippling ribbon issues. I could no longer edit sketches of various family types including floors and in-place families.

Before you try to re-install (which will not fix this), this easy to apply Hot-Fix will fix the issue promptly 2014INSTALLdotnet.

Make sure to read the Read-Me on how to apply after having service pack 2 installed.


Grid Guides – The Great Revit Cover up

October 15, 2011

Grid Guides are a nice sheet layout tool even if somewhat limited, since you can’t change the graphic attributes of individual lines.  They also have another annoying habit in 2011.  The grid guide will conceal shaded regions, raster images and detail lines in your viewports.  It doesn’t affect printing when the guides are on and you send a file to the printer or produce a pdf.  It just makes your sheets look like sh!!t.  Consequently you have to turn them off and on during production.  Big Pain!

Seeing things (NOT!)


Revit Fails to Update the Central File

June 30, 2011

Ever get this message?  “”Revit cannot reconcile the differences between your local and the central file”  Well we have, here at Breckenridge.  Patrick at CADsoft offered the following steps to aviod this situation as well as dealing with it when you encounter this message:

1. Make sure no one EVER edits a Central file directly, once local files have been created. If you do, you will need to recreate all the local files from the new Central file.

2. Make sure that everyone in your team is saving and syncing to Central at least every 30 minutes. If you have a very large project (over a few hundred MB), you may want to have a schedule when people save, like, so-and-so saves at 1/4 past and 1/4 till every hour and so-and-so saves at half past and on the hour every hour. This will keep you from having to wait on each other when the sync process is going on.

3. If the Revit cannot reconcile the differences between your local and the central file error pops up, immediately stop working on all your local files. If you have a lot of work done on a particular local file that you don’t want to lose, you might choose to create a new central file from it. You will then have have other users create a local file from the new central.

4. If there are new elements or work you don’t want to lose in one of the local files, you may be able to cut and paste elements into your local and then sync up to central.

Autodesk recommends that everyone in your team create a new local file from Central every single day. I don’t find that necessary, but doing it at least once a week will prevent any corruption from creeping into your project.”

Thanks Patrick, I deemed these words of wisdom worth sharing with the SARUG members.

On our end we believe this error resulted from limited operating RAM on the computer where this occured.  The system only has 3 gigs of RAM and had been returning memory limit errors that increased as the project file size grew.  The other A.I.T. working on the file has 4 gigs of RAM and had not been getting any memory warnings or error messages.  Fortunately the local file from the offending machine was intact so the data wasn’t lost.  The changes just have to be painstakingly found and recreated in the central file.

One caveat:  Ideally you would want to open the local file and the central file in the same instance of Revit and just do copy / paste operations to transfer the data; however, you cannot open a local file and the central file in the same instance of Revit.  But you can create another central file with a different name from your local file and open both central files within the same instance of Revit.  You only need to have sufficient RAM on the system to hold both versions.   

Best of Luck

P.S. 7-12-11 

Steve Stafford is a regular reader of the SARUG Blog and recently posted some additional advice on this subject at his blog (Revit OpEd) that you should read.  Thanks Steve for monitoring the blog.  Your comments are always welcome. 


Revit Russian Roulette!!

June 17, 2011

Dimensions that bridge between a linked AutoCAD file and your Revit model can be like playing Russian Roulette. You can get away with small changes but at some point Revit will go BANG! and delete all your dimensional references that bridge between the ACAD file and the Revit Project File when you reload that revised ACAD file.

It’s best to construct a model or graphic reference in the Revit Project to dimension to. Then changes in the reloaded ACAD file will be visually apparent without deleting control dimensions in the project and should be easy to ID and then revise.

A linked Revit project file may also present a problem with bridging dimensions.

This warning approved by the N.R.A. (National Revit Association)