export to dwg 200x limitations?

[Anonymous]

I have tried the "export to dwg" command and when on "simple" drawings behaves properly.

on some others though (dwg's with shortcuts/alignments/surfaces/corridors/xrefs in any combination) will not export any file. Are there limitations to it tha I should be aware of?

(I'm using AutoCAD Civil 3D 2013)

[ToddRogers-WPM]

You will need to Export the Civil objects out to LandXML.

[mathewkol]

Todd, I don't see how exporting to XML will help him export his dwg to a plain old autocad file.

OP, sometimes it's better to explode objects yourself then run the export to dwg command.  You need to explode them in the correct order.  Start with objects that don't have dependecies like section views and the sections, profile views and the profiles, then corridors, pipes etc.

[ToddRogers-WPM]

He didn't specify going to a plain old AutoCAD file.

[mathewkol]

I guess I didn't read the subject line correctly then...

[export to dwg...]

🙂

[Anonymous]

I don't know much about LandXML, so I 'll have to read a bit and see if it suits me.

But ok, sorry for not explaining, what I want is plain autocad 2004 file, to share with others.

and I am trying to avoid "explode" (which I'm currently using)

I update my dwg very often, so I have to provide them a backgound to work with, and that may happen once or twice a a day. Exploding takes too much time...

[ToddRogers-WPM]

You're going to have to go with Matt on this one.

[AllenJessup]

ExportToAutocad[release] should explode any Civil 3D objects that are in the drawing. It doesn't handle Shortcuts or Xrefs. You should also explore the AECOBJEXPLODE command.

Allen

[Anonymous]

this one works better (thank you very much!), but still I do have to do a series of manual arranging...

so I have to dig it a bit more for a satisfying result.

Perhaps, I should focus on something more specific.

Let's say I would like to export my Layout ONLY! to a dwg 2004 modelspace.

Any suggestions?