Big MAJOR SCARY problem with linked DWG's...

[hand471037]

I've never had this happen before. In the past we've made extensive use of DWG linking in Revit. We've been able to make changes to the DWG files before, and have those changes correctly reflect into Revit. For over a year now. But now, sometimes when we make a change in the AutoCAD file, next time you open up your Revit project the imported & linked instance of that file will have it's layers corrupted. It's like everything has been randomly 'shuffled' between all the layers, things are showing up that were turned off, things are on the wrong layers altogether, PLEASE HELP!

This is starting to become a cronic problem; I just did a test run and it's occuring on all our machines. As far as I know we haven't changed anything with either our AutoCAD setup or with Revit. This is happening on three different machines. We are using AutoCAD 2000 & Revit Build 20030415_1500. This just started happening, as far as I know it was fine a week ago. It's not completely consistant; there are times where they come in properly. No one is running anything special in AutoCAD. If we delete the corrupted import, and then re-import, everything is fine. Until next time we make changes in the DWG & the fact that you have to redefine the visibility settings for that project.

This is gonna be a HUGE problem for us... ****. :(

[mlgatzke]

Jeff,

Just a thought, but have you run AUDIT on your AutoCAD drawing? AutoCAD can sometimes corrupt it's own drawings - especially the larger and more complex ones. From the Command Prompt type "audit" and answer "Yes" when you are asked whether you want errors repaired.

This may solve your problem.

[christopher.zoog51272]

I've never had this happen before. In the past we've made extensive use of DWG linking in Revit. We've been able to make changes to the DWG files before, and have those changes correctly reflect into Revit. For over a year now. But now, sometimes when we make a change in the AutoCAD file, next time you open up your Revit project the imported & linked instance of that file will have it's layers corrupted. It's like everything has been randomly 'shuffled' between all the layers, things are showing up that were turned off, things are on the wrong layers altogether, PLEASE HELP!

This is starting to become a cronic problem; I just did a test run and it's occuring on all our machines. As far as I know we haven't changed anything with either our AutoCAD setup or with Revit. This is happening on three different machines. We are using AutoCAD 2000 & Revit Build 20030415_1500. This just started happening, as far as I know it was fine a week ago. It's not completely consistant; there are times where they come in properly. No one is running anything special in AutoCAD. If we delete the corrupted import, and then re-import, everything is fine. Until next time we make changes in the DWG & the fact that you have to redefine the visibility settings for that project.

This is gonna be a HUGE problem for us... ****. :(

Wow, this same thing happen to one our users last friday, i tried a few things and when that didn't work, i just chalked it up to user error and i told him i would investigate it further when i had more time. Guess I better get back on it.

It was the same thing, certain objects appeared on the wrong layer, even though they were on the right one in acad 2000.

I'm going to try to audit and maybe reload it. I'll be sending the file off to support tomorrow. :?

[hand471037]

No dice on the audit. I'm a Fashist Feind when it comes to keeping the DWG's in proper shape. comes from learning AutoCAD on a 486. ;)

so they have been audited. Any other ideas?

[Martin P]

Is it blocks and xrefs in the dwg that are going onto the wrong layers, or just basic lines and circles? If its blocks I'd explode them, bind the xrefs, explode them - not pretty though :o( and if it is simply linework text etc - I would maybe try deleting the links and reimporting them? - losing all the layer settings is a bit of a killer though, maybe somebody at revit could do something about that with a log file kind of thing to make all the settings come back???

Sounds pretty nasty though, I have had problems with linked dwgs also, If I import them at any scale other than 1:1 they will re-scale sometimes to be tiny, or large. Reported it but they said it was something to do with our network settings or something else (other than revit)????

[sbrown]

Please send in your data, we have had so many dwg problems since revit was purchased and the dwg import supposedly became "real dwg"

Here is our list of issues
1. Import lineweights no longer respond as specified in the import dwg settings.
2. changing the object style of a layer no longer changes the line type of the dwg(random, seemingly)
3. beware that if you link a site plan from a civil engineer that you have to scale up 12 times or switch to feet (or any file you have to scale upon import) instead of autodetect then you import another dwg at auto detect, then reload the site plan, it will scale back down, basically scaled links don't remember you scaled them, you need to set the scale and reload each link individuallly with the appropriate setting.
4. imports into detail component families just plain stink. try importing a pella window jamb into a detail family, then insert it into your project and mirror it, woooo the lines get all messed up and if you mirror back it won't look right either. ok so now you decide well I'll just explode it, wrong, now the component just sucks system resources, regening and regening then try to move a line or edit it in some way and you'll be off to the coffee pot.

Come on autodesk we need dwg compatability that works!!!!

[hand471037]

OK, so I've got a few more things to add to the mix of this bug:

If we make simple changes to the DWG's, it doesn't seem to trigger the bug.
If we make major changes to the DWG's, like deleting/renaming/moving about lots of layers, or cutting and pasting major bits from other drawings, it can (but not always) trigger the bug.
Audit, Overkill, and other DWG clean-up commands don't seem to trigger the bug.
Since we've upgraded to the latest build (20030716_1400), the bug seems to have gone away. But I'm keeping my fingers crossed!
:roll: