Archive for June, 2011

h1

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
Carl

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. 

h1

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)
Carl

h1

Linked AutoCAD File : Active-X / Proprietary Components Error on Reload

June 15, 2011

“Some elements were lost during import.  ActiveX and some proprietary componets cannot be imported”

1.  This error can arise from p-lines of infinite length, which are typically used as reference lines.  Remove these elements from the AutoCAD file and reload.

2. or ?

AutoCAD not my thing.  This one from the CADJockey sitting next to me.

Carl

h1

Revit Crash – Insufficient Space on the…………………C-Drive Error

June 8, 2011

If you get this error it’s because your system’s paging limit for the Virtual Memory Allocation is set to low.  Check out this link for accessing and changing the VMA setting.

http://docs.autodesk.com/REVITST/2010/ENU/Revit%20Structure%202010%20Users%20Guide/RST/index.html?url=WS73099cc142f487559df01610d821027e1-7fd2.htm,topicNumber=d0e1694
Typical responses to this type of limitation: Revit evaporates or locks up, or Revit gives you the memory warning and prompts you to save a recovery file, which more often than not will fail and the application will go into a recovery file prompt loop. If this happens just end the program and hope you haven’t lost to much work.

To get ahead of this I suggest you check your VMA and up the default limit substantially.

At my age I can use all the memory I can get!
Carl

P.S.  Insufficient drive space can also be due to too many temporary files on  the drive.  This type of problem is accompanied by a warning to free up space on the C-Drive or redefine Windows user variable TMP to be a folder on another drive.  To purge your TMP files use the Disk Cleanup utility in the Programs>Accessories>System Tools folder.  http://www.vistax64.com/tutorials/104637-temporary-files-temp-folder.html  Reboot after running the Cleanup routine.

 

h1

Introduction of bullets in text.

June 7, 2011

In Revit 2011 we received a minor text upgrade – Bullets and numbering.

During today’s class where I was presenting all of the options for text I stumbled upon this little gem and couldn’t help but share my surprise and realization that I could have used this feature on a project earlier in the morning.  Sometimes these little upgrades slip past the more experienced user but sure are worth using once found.

-Jake