Why does Exporting to DXF (any version other than 2013) fail, every single time?
First, we always get this error during the save. The save appears to finish OK in spite of the error.
But when you try to open the DXF using DWG Trueview, we get this error.
If we export out to 2013 DXF, the resulting file can be opened, but this doesn't do us much good.
TIA (using C3D 2013 with latest SP)
(No connection with Autodesk other than using the products in the real world)
IDSP Premium 2014 (mainly Civil 3D 2014 but also 3ds Max Design)
Win 7 Pro x64, 256Gb SSD, 300Gb 15,000 rpm HDD
16Gb Ram Intel Xeon CPU E5-1607 0 @ 3.00GHz (4 CPUs), ~3.0GHz
NVIDIA Quadro 4000, Dual 27" Monitor, Dell T3600
I just tried it with one of the tutorial files and it worked just fine. Exported to a 2010 dxf file and then opened it in C3D 2012.
Does it happen on other drawings?
Does it happen on other computers?
Can you share the file?
Happens with all of *our* drawings, that I have seen here.
Yes on other machines too.
Yes, I run an audit, purge, purge regapps, etc. on the DWG before trying the export.
I've also tried manually running AecObjExplode before the export.
I have managed to get it down to the 2004DXF in the past, but it's like an hour long process of trial and error - to the point of, I don't know what I did to get it to finally work.
Unfortunately, I can't share the DWG. But maybe I can strip enough of it out where I can. Give me a bit.
I just want it to work, or give me a reasonable explanation of why it can't. These vague errors do not help any.
I've had this happen also. I've heard of this being blamed on network speed or traffic and also on anti-virus software. But I've never seen anything conclusive about it.
Feels like a bug.
You know those commercials where "sometimes you just have to do what needs done"......
So I open the DXF in an ASCII editor and remove the GEODATA section, save the file, and it opens fine after that.
See attached TXT file for the contents of the GEODATA section.
If AutoCAD cant read the GEODATA section, then the DXF export command shouldn't be writing it.
Can you try it with one of the tutorial files? If it works fine there, then it must be something with "your files", or at least something that's different between your files and the tutorial files.
Brian, did you miss the email directly above your last reply? C3D is including data in the DXF that it can't understand when opening the file. That is a bug regardless if it's "our files" or not. Even in a worst case scenerio, where you might have a 3rd party routine creating non-C3D entities or something like that, the DXFOUT command should ignore items that cannot be read by DXFIN. Or better yet, DXFIN should ignore them, but that is anothe debate...
I'm quite sure it will work fine on the tutorial files, but unfortunately I can't send those to the client. Not trying to be rude, but it shouldn't take an hour to get a drawing converted to another format.
I think the key going forward is going to be --- using the "Select Objects" option in DXFOUT and physically selecting the objects on the screen, which will prevent DXFOUT from including all the non-graphical data, which isn't needed in this case anyway.
Thanks for your help and time on this!
Sounds like they need something like the WBlock option "Include Map Data?". Do you have the same trouble if you export to a binary file?
After further testing, using "Select Objects" doesn't help, it still adds the mysterious "GEODATA" to the DXF file. But it looks like if you run the command GEOGRAPHICLOCATION and remove this data before exporting, then the DXF file does not contain this section and it can be opened just fine.
So the GEODATA section is documented, but this was not part of the 2004 DXF file format, so why is DXFOUT to a 2004 version DXF including it?