Tag Archives: Civil 3D 2011

Missing language pack fixes compared

Having tried out the cleanup fixes from both Autodesk and Owen Wengerd, they both appear to work fine. Here are some points of comparison:

  • Owen’s utility will work with any AutoCAD variant from 2007 on; Autodesk’s fix is currently restricted to Civil 3D 2009, 2010 and 2011. As this problem is definitely not confined to Civil 3D, and may need to be dealt with by non-Civil 3D users, that could be the dealbreaker right there.
  • Owen’s can be installed by anyone by simply copying a file and loading it when needed or in the Startup Suite; Autodesk’s requires admin rights to either run an installer program or manual replacement of a program component, depending on the release.
  • Owen’s loads and runs as the user requires; Autodesk’s runs automatically when opening and saving a drawing.
  • Owen’s provides some information about what is getting cleaned up; Autodesk’s operates in total silence.
  • Owen’s utility can take a while to scan through everything in a complex drawing; Autodesk’s appears to take no longer to open the drawing than normal. To give you some idea of the times involved, in one test in Civil 3D 2011, opening a blank ( but 2.2 MB!) drawing based on the Civil 3D template took 3.6 s with or without the fix; Owen’s cleanup took 0.7 s. In another test on an oldish PC with AutoCAD 2010, cleaning up a drawing with 2.8 MB of real content took Owen’s utility about 15 seconds.

For my purposes, Owen’s utility is what I need, because the users who need to clean up these drawings use AutoCAD, not Civil 3D. I’ve set up a batch process for these users, which opens each selected drawing, runs Owen’s utility and saves the drawing. However, I suggest Civil 3D users install the relevant updates and patches anyway, as they fix more than just this problem. In addition, in Civil 3D 2011 without the Autodesk fix, one of the problems fixed by Owen’s cleanup (a AeccDbNetworkCatalogDef one) is then immediately recreated by Civil 3D.

The upshot is that Civil 3D users should at least apply Autodesk’s fixes; everybody else should use Owen’s.

Using Owen’s fix, it is interesting to see what it reports as being the problem in particular drawings. Here’s what one of my non-Civil 3D problem drawings shows up:

Command: cleanlanguage
Scanning drawing for corrupt objects...
Corrupt object AecDbScheduleDataFormat<2F84> CLEANED
Found 1 corrupt object

Here’s what the Civil 3D 2011 ANZ template shows up when cleaned:

Command: cleanlanguage
Scanning drawing for corrupt objects...
Corrupt object AeccDbNetworkCatalogDef<8B7> ERASED
Corrupt object AeccDbLegendScheduleTableStyle<1619> CLEANED
Corrupt object AeccDbLegendScheduleTableStyle<161B> CLEANED
Corrupt object AeccDbLegendScheduleTableStyle<161A> CLEANED
Corrupt object AeccDbLegendScheduleTableStyle<161F> CLEANED
Found 5 corrupt objects

It looks like every Civil 3D 2011 drawing based on these templates has been going out corrupt in 5 different places. Hopefully, Autodesk will quickly get on to fixing up the Civil 3D template situation, and will incorporate the automated open/save cleanup in future updates to AutoCAD itself and all the other AutoCAD-based verticals.

Partial fix for language pack problem

The Civil 3D group within Autodesk has moved impressively quickly in providing a partial solution to the language pack problem I described earlier. What has been provided so far is a set of patches for Civil 3D 2009, 2010 and 2011 that allow Civil 3D users to remove the spurious language pack flag by opening and re-saving the affected drawings. I have not yet tested this, but I am informed that it works.

What’s left to do? Obviously, not all recipients of these drawings are going to have Civil 3D. In fact, prior to isolating Civil 3D as one definite source of the problem, I had spent a lot of time helping out AutoCAD users clean up language-pack-infected drawings, using awkward and dangerous copy-and-paste methods. So Autodesk has AutoCAD and all its vertical variants to work through yet as far as a cleanup mechanism goes. Also, the problem needs resolving at the source end. All “infected” templates (in Civil 3D and any other verticals that may have the problem) need fixing and distributing to users as quickly and effectively as possible, in order to reduce the number of drawings being created with the problem. I know individual users can do this for themselves, but large numbers of users won’t do so if left to their own devices, causing problems for everyone else. As the originator of the problem, Autodesk has a duty to do its very best to resolve it.

Thanks, Autodesk, for quickly getting started on fixing the problem and providing a partial solution in a timely manner. I hope you can provide the rest of the solution equally efficiently.

Civil 3D 2011 ANZ comes complete with “virus”

If you install Civil 3D 2011 using the ANZ (Australia/New Zealand) profile, when you start it up for the first time, you will see a large warning indicating that the drawing requires an Asian language pack to be installed. It also warns that this is a symptom of the acad.vlx virus:

Language Pack warning

Now I know that in this case it’s not an actual virus causing the problem, but rather the ANZ template drawing being “infected” with this Language Pack requirement. I have had to deal with quite a few incoming drawings in this state, and that’s painful enough without Autodesk also infecting every Australasian Civil 3D drawing with the problem. Other profiles may be similarly infected, but at the moment I don’t know. Edit: Matt Anderson reports that the problem occurs on US systems too.

Autodesk, I suggest that as a matter of great urgency you create a clean ANZ template file, post it as a hotfix and warn all your Civil 3D customers of the SNAFU. Neither “install the language pack” nor “turn off the warning” are adequate workarounds. Your customers do not want to send out or receive any drawings in this state.

Beyond the immediate issue of Autodesk shipping software that on first use warns the user that they may have a virus (and encourages the creation of drawings that spread that warning far and wide), I would appreciate some assistance in dealing with “infected” drawings, whether in Civil 3D or plain AutoCAD.

First, I need to be able to detect such drawings using LISP so I ensure they are rejected rather than allowed into our drawing management system, and this detection will need to work in releases at least as far back as AutoCAD 2004.

Second, I need a mechanism of cleaning up such drawings. The only thing I have discovered that works so far is the manual, time-consuming and dangerous process of recreating the drawings by starting from scratch and Copy/Paste in each layout. With big jobs using nested xrefs, this is fraught. I need to be able to provide a LISP-based cleanup mechanism that I can set up to work in batch mode on a set of drawings.

I would be grateful for any clues anyone might have about the above detect & cleanup needs.

Edit: see the comments for further important information.