Forums >> Revit Building >> Technical Support >> Corrupted Links

NKramer

active

Joined: Tue, Oct 9, 2007
285 Posts

We are linking our details in from AutoCAD. However, we keep getting corrupted objects. It seems that this happens when we are linking in several files at once. We notice this when someone else goes to save to central, then we get an error message that reads

"Element 2367550 became corrupt at some time before this session. To continue with this project, save a recovery file. In the recovery file, this element will be deleted to fix the problem." (element number varies)

Then we have to dump all but one file (locals and central, just depends who did the most work since the last save), and then open that file with audit and detach from central checked. As the file is auditing a message comes up saying that Revit dumped the corruptd files and now you can work. Afterwords we can relink the files without any problems. People arent linking the same files or anything that I can tell. My only guess is that the person who is linking in the files isnt saving to central often enough and Revit gets confused over the number of new links that have been added...?

Any ideas, has anybody else experienced the same problem? know why this happens or how to work around it?

--

It turns out that this an issue with the 1700 build and hatches in AutoCad. The details we were having problems with were signage details with several solid hatches layerd over the top (dont know why they were layered but they were). So I deleted the hatches and redrew them. Aparently the 2345 build takes care of this, but my office doesnt want switch over because of some other instabilites with that build. I guess they fix some problems are create more...

Anybody know what the istability issues are with 2345 besides for the Y2K8 bug (which affects builds alll the way back to version 6 or so...? 

This user is offline

View Website

lorne17

active

Joined: Wed, Aug 29, 2007
417 Posts

It looks like they fixed teh Y2K8 Bug!

http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=9408083

We have been having the same issue with the hatches being imported from CAD.  Hopefully this update will fix all known issues with that and not cause anymore.

HTH,

Lorne

-----------------------------------

AutoDesk Revit Certified Professional

Denver, CO

Revit Architecture

This user is offline

jreding

active

Joined: Fri, Nov 9, 2007
18 Posts
No Rating

I am having the same problem when I save to central. I am not linking files from AutoCad. I'm importing some details but they are not linked.

 Any suggestions?

This user is offline

lorne17

active

Joined: Wed, Aug 29, 2007
417 Posts

I found they don't need to be linked.  Just have hatches to corrupt the file.  That's all I know.  As far as I can tell the new Y2k8 build fixed this issue.

Good luck, sorry I can't be of more help.

-----------------------------------

AutoDesk Revit Certified Professional

Denver, CO

Revit Architecture

This user is offline

NKramer

active

Joined: Tue, Oct 9, 2007
285 Posts

The new build masks but does not fix the problem. If you link the file or just attach it any hatch problems will show up as errors and still have the potential to crash your file or at the bare minimum they will bog your file down.

Long story short you have to impliment a new set of best practices for AutoCAD drawings that you plan on loading into Revit. In my experiece they are as follows:

1. Do not use nodes (Revit looks at them as a line and says that the segment is to small = error for eacj node)

2. All text must be MText (singlee line text shifts down, so the Revit output looks different from the AutoCAD)

3. Dont use RomanS (This may be more of a problem with our plotter, but when I print out it randomly skips letters)

4. All fonts must be true type (i.e. standard Windows fonts, or you have to convert them; Revit does not understand the ArchDiM AutoCAD font, etc.)

    a. All hatches must be of a scale > .25. If the scale drops below .25 then it show up in Revit as solid)

    b. All hatches should not be associative (sometimes Revit has a problem finding the limiting bounds of an associated hatch and freaks out)

    c. Hatches should not overlap. (We had corruption problems when someone layerd 4 hatches over each other, dont ask me why they did it but it gave us problems)

I am sure that their are more. If anybody else knows of other problems feel free to add to the list.

HTH

Nick 

This user is offline

View Website

Corrupted Files

0

Revit City Downloads Corrupted

6

Imported hatch patterns appear corrupted

3

Corrupted file

3

a corrupted element

2