dgorsman wrote:The core console has been reported as not-quite-ready for primetime yet, so I would love to see a KILLALLAEC tool implemented when it is ready. Its the perfect host for such a tool.
It must also preserve all existing Sheet Set data. Once those files get infected, that's it, you're screwed.
Unless you wish to recreate the now destroyed data.
The AEC content in the core AutoCAD system is in response to user requests to make the different verticals more compatible. By basing that material off a common content base it allows features in ACA, AutoCAD MEP, Mechanical, Civil3D etc. to be viewed with straight AutoCAD without requiring a bazillion object enablers to be developed, distributed, and installed. So it *does* serve a purpose.
My main complaint isn't with the purpose but the implementation. AEC data "gremlins" infest the drawing files with surprising ease. Whenever a drawing with AEC content is opened or XREF'd, the AEC enablers are loaded in AutoCAD at the application level. They then proceed to look at *every* open drawing and if there is no AEC data in those drawings it proceeds to add a basic skeleton of content (hey, we are working with AEC anyways so it shouldn't hurt, right? Uhm... IT DOES because we are NOT working with AEC content most of the time.). Now when those infested drawings are opened or XREF'd later, since they have the basic AEC data skeleton AutoCAD figures the required AEC enablers have to be loaded, propagating the content to even more drawings. The export-to-autocad functions don't remove this basic header data which is mostly what determines if a drawing contains AEC content or not. What is needed is a means to "kill it with fire": rip out not just the in-drawing objects but the header data as well.
The core console has been reported as not-quite-ready for primetime yet, so I would love to see a KILLALLAEC tool implemented when it is ready. Its the perfect host for such a tool.
AEC content removal works best in the AutoCAD variant that created that content (power to the author, not you the recipient): between object enablers, Proxy setting, rountrip objects (for newer content) and more I would be surprised if there is a perfect cure for outsiders.
95% of the time, it works fine for us here sicne we started using it in R2008: missing an OE seems to be the problem with the 5% for far.
So AutoCAD support lied to me when then said it only removed info used by the other programs, that is not surprising.
I know they were lying when they said the PDF size increase was to do a quality improvement.
I must have left out the “-“ when I tried it in 2012, and got the unknown command reply.
Surprise, Surprise, Surprise, I’m back to “there is not one feature I like or well use in 2013. :robotmad:
That command has been around for a while but regardless, good luck with that. It only works half-assed.
Example: If you have a sheet that is a member of a sheet set that contains AEC data, you can use this command to remove the AEC data contained within that file. AEC data can be inherited from another drawing, model space or paper space via xrefs or fields.
If you use this command on such a drawing it will destroy all references to the sheet set data making the resulting file virtually useless.
FYI: Here is what help has about it.
Access Methods
Command entry: -EXPORTTOAUTOCAD or AECTOACAD
Summary
You can create a new version of a drawing file with all proxy AEC objects exploded into basic objects. The new version of the drawing loses the intelligence of the custom AEC objects, but the resulting basic objects can be displayed and accessed in earlier product versions when object enablers are not available.
This command is used with drawings created in AutoCAD Architecture and previous releases.
List of Prompts
The following prompts are displayed.
Export options [Format/Bind/bind Type/Maintain/Prefix/Suffix/?] <Enter for filename>: Enter an option or press Enter to specify a file name
Enter for Filename
Creates a new drawing file with the specified name.
Format
Determines the drawing file format for the resulting drawing file.
Bind
Determines how xrefs are treated when creating the new drawing.
YesBinds all xrefs to the drawing. Layers and other xref-dependent named objects are merged into the new drawing.
Maintains the xrefs as links to other drawings.
Bind Type
Determines how xref-dependent objects are treated when the Bind option is turned on.
BindMaintains the names of layers and other xref-dependent objects when binding xrefs.
Merges the names of xref-dependent objects into the new drawing without including the original file name.
Maintain
Determines how blocks within custom AEC objects are treated.
YesExplodes all block instances within custom AEC objects into basic objects. The resulting basic objects revert to their original properties rather than the properties of the block definitions.
Does not explode any block instances within custom AEC objects. The properties of the block instances are determined in the usual way, depending on how the objects in the blocks were created and the property settings of the layers on which the blocks are inserted.
Prefix
Specifies the prefix to be added to the current drawing file name.
Suffix
Specifies the suffix to be added to the current drawing file name.
?
List Settings
Lists the current settings for the command.
Even that I now know how to it will be causing me to waste hundreds of not thousands of man hours removing AEC/proy CRAPhic, I glad I foubd –exporttoautocad.
So far it is reducing my file size by about 40%, that right 40% of my file are useless AEC info that is only used for costumers with stuff like AutoCRAP Architecture or Civil 3D.
Apparently for some time now Full AutoCAD is not just AutoCAD, it has all features for the 11 other AutoCAD products in it. They thought they were not active and ether was not adding AEC info into the drawings, or thought we never notice. But guess what they have been, and we have noticed. :manmad:
I’m 100% sure they only added this for their own use/convenience, as opposed to doing something for their COSTOMERS! :manmad:
But there it is command –exporttoautocad, basically with this little program you can export to create a new DWG that is free of AEC/Proxy junk.
There a few options to modify the end result, format, bind, bind type, maintain, prefix, and suffix.
Even after reading the help on it i don’t know what bind does? I know what it says, but can’t see a difference in the files it creates.
Here is the commend string I wrote for it.
^C^C-exporttoautocad;f;2010;B;n;M;y;S;-Apr2012;P;.;
I look forward to any feedback.
LOL, The only single good thing in 2013 was hidden and is only a work around for their mistakes.
dgorsman wrote:The core console has been reported as not-quite-ready for primetime yet, so I would love to see a KILLALLAEC tool implemented when it is ready. Its the perfect host for such a tool.
It must also preserve all existing Sheet Set data. Once those files get infected, that's it, you're screwed.
Unless you wish to recreate the now destroyed data.
The AEC content in the core AutoCAD system is in response to user requests to make the different verticals more compatible. By basing that material off a common content base it allows features in ACA, AutoCAD MEP, Mechanical, Civil3D etc. to be viewed with straight AutoCAD without requiring a bazillion object enablers to be developed, distributed, and installed. So it *does* serve a purpose.
My main complaint isn't with the purpose but the implementation. AEC data "gremlins" infest the drawing files with surprising ease. Whenever a drawing with AEC content is opened or XREF'd, the AEC enablers are loaded in AutoCAD at the application level. They then proceed to look at *every* open drawing and if there is no AEC data in those drawings it proceeds to add a basic skeleton of content (hey, we are working with AEC anyways so it shouldn't hurt, right? Uhm... IT DOES because we are NOT working with AEC content most of the time.). Now when those infested drawings are opened or XREF'd later, since they have the basic AEC data skeleton AutoCAD figures the required AEC enablers have to be loaded, propagating the content to even more drawings. The export-to-autocad functions don't remove this basic header data which is mostly what determines if a drawing contains AEC content or not. What is needed is a means to "kill it with fire": rip out not just the in-drawing objects but the header data as well.
The core console has been reported as not-quite-ready for primetime yet, so I would love to see a KILLALLAEC tool implemented when it is ready. Its the perfect host for such a tool.
AEC content removal works best in the AutoCAD variant that created that content (power to the author, not you the recipient): between object enablers, Proxy setting, rountrip objects (for newer content) and more I would be surprised if there is a perfect cure for outsiders.
95% of the time, it works fine for us here sicne we started using it in R2008: missing an OE seems to be the problem with the 5% for far.
So AutoCAD support lied to me when then said it only removed info used by the other programs, that is not surprising.
I know they were lying when they said the PDF size increase was to do a quality improvement.
I must have left out the “-“ when I tried it in 2012, and got the unknown command reply.
Surprise, Surprise, Surprise, I’m back to “there is not one feature I like or well use in 2013. :robotmad:
That command has been around for a while but regardless, good luck with that. It only works half-assed.
Example: If you have a sheet that is a member of a sheet set that contains AEC data, you can use this command to remove the AEC data contained within that file. AEC data can be inherited from another drawing, model space or paper space via xrefs or fields.
If you use this command on such a drawing it will destroy all references to the sheet set data making the resulting file virtually useless.
FYI: Here is what help has about it.
Access Methods
Command entry: -EXPORTTOAUTOCAD or AECTOACAD
Summary
You can create a new version of a drawing file with all proxy AEC objects exploded into basic objects. The new version of the drawing loses the intelligence of the custom AEC objects, but the resulting basic objects can be displayed and accessed in earlier product versions when object enablers are not available.
This command is used with drawings created in AutoCAD Architecture and previous releases.
List of Prompts
The following prompts are displayed.
Export options [Format/Bind/bind Type/Maintain/Prefix/Suffix/?] <Enter for filename>: Enter an option or press Enter to specify a file name
Enter for Filename
Creates a new drawing file with the specified name.
Format
Determines the drawing file format for the resulting drawing file.
Bind
Determines how xrefs are treated when creating the new drawing.
YesBinds all xrefs to the drawing. Layers and other xref-dependent named objects are merged into the new drawing.
Maintains the xrefs as links to other drawings.
Bind Type
Determines how xref-dependent objects are treated when the Bind option is turned on.
BindMaintains the names of layers and other xref-dependent objects when binding xrefs.
Merges the names of xref-dependent objects into the new drawing without including the original file name.
Maintain
Determines how blocks within custom AEC objects are treated.
YesExplodes all block instances within custom AEC objects into basic objects. The resulting basic objects revert to their original properties rather than the properties of the block definitions.
Does not explode any block instances within custom AEC objects. The properties of the block instances are determined in the usual way, depending on how the objects in the blocks were created and the property settings of the layers on which the blocks are inserted.
Prefix
Specifies the prefix to be added to the current drawing file name.
Suffix
Specifies the suffix to be added to the current drawing file name.
?
List Settings
Lists the current settings for the command.
Even that I now know how to it will be causing me to waste hundreds of not thousands of man hours removing AEC/proy CRAPhic, I glad I foubd –exporttoautocad.
So far it is reducing my file size by about 40%, that right 40% of my file are useless AEC info that is only used for costumers with stuff like AutoCRAP Architecture or Civil 3D.
Apparently for some time now Full AutoCAD is not just AutoCAD, it has all features for the 11 other AutoCAD products in it. They thought they were not active and ether was not adding AEC info into the drawings, or thought we never notice. But guess what they have been, and we have noticed. :manmad:
I’m 100% sure they only added this for their own use/convenience, as opposed to doing something for their COSTOMERS! :manmad:
But there it is command –exporttoautocad, basically with this little program you can export to create a new DWG that is free of AEC/Proxy junk.
There a few options to modify the end result, format, bind, bind type, maintain, prefix, and suffix.
Even after reading the help on it i don’t know what bind does? I know what it says, but can’t see a difference in the files it creates.
Here is the commend string I wrote for it.
^C^C-exporttoautocad;f;2010;B;n;M;y;S;-Apr2012;P;.;
I look forward to any feedback.
LOL, The only single good thing in 2013 was hidden and is only a work around for their mistakes.
dgorsman wrote:The core console has been reported as not-quite-ready for primetime yet, so I would love to see a KILLALLAEC tool implemented when it is ready. Its the perfect host for such a tool.
It must also preserve all existing Sheet Set data. Once those files get infected, that's it, you're screwed.
Unless you wish to recreate the now destroyed data.
The AEC content in the core AutoCAD system is in response to user requests to make the different verticals more compatible. By basing that material off a common content base it allows features in ACA, AutoCAD MEP, Mechanical, Civil3D etc. to be viewed with straight AutoCAD without requiring a bazillion object enablers to be developed, distributed, and installed. So it *does* serve a purpose.
My main complaint isn't with the purpose but the implementation. AEC data "gremlins" infest the drawing files with surprising ease. Whenever a drawing with AEC content is opened or XREF'd, the AEC enablers are loaded in AutoCAD at the application level. They then proceed to look at *every* open drawing and if there is no AEC data in those drawings it proceeds to add a basic skeleton of content (hey, we are working with AEC anyways so it shouldn't hurt, right? Uhm... IT DOES because we are NOT working with AEC content most of the time.). Now when those infested drawings are opened or XREF'd later, since they have the basic AEC data skeleton AutoCAD figures the required AEC enablers have to be loaded, propagating the content to even more drawings. The export-to-autocad functions don't remove this basic header data which is mostly what determines if a drawing contains AEC content or not. What is needed is a means to "kill it with fire": rip out not just the in-drawing objects but the header data as well.
The core console has been reported as not-quite-ready for primetime yet, so I would love to see a KILLALLAEC tool implemented when it is ready. Its the perfect host for such a tool.
AEC content removal works best in the AutoCAD variant that created that content (power to the author, not you the recipient): between object enablers, Proxy setting, rountrip objects (for newer content) and more I would be surprised if there is a perfect cure for outsiders.
95% of the time, it works fine for us here sicne we started using it in R2008: missing an OE seems to be the problem with the 5% for far.
So AutoCAD support lied to me when then said it only removed info used by the other programs, that is not surprising.
I know they were lying when they said the PDF size increase was to do a quality improvement.
I must have left out the “-“ when I tried it in 2012, and got the unknown command reply.
Surprise, Surprise, Surprise, I’m back to “there is not one feature I like or well use in 2013. 
That command has been around for a while but regardless, good luck with that. It only works half-assed.
Example: If you have a sheet that is a member of a sheet set that contains AEC data, you can use this command to remove the AEC data contained within that file. AEC data can be inherited from another drawing, model space or paper space via xrefs or fields.
If you use this command on such a drawing it will destroy all references to the sheet set data making the resulting file virtually useless.
FYI: Here is what help has about it.
Access Methods
Command entry: -EXPORTTOAUTOCAD or AECTOACAD
Summary
You can create a new version of a drawing file with all proxy AEC objects exploded into basic objects. The new version of the drawing loses the intelligence of the custom AEC objects, but the resulting basic objects can be displayed and accessed in earlier product versions when object enablers are not available.
This command is used with drawings created in AutoCAD Architecture and previous releases.
List of Prompts
The following prompts are displayed.
Export options [Format/Bind/bind Type/Maintain/Prefix/Suffix/?] <Enter for filename>: Enter an option or press Enter to specify a file name
Enter for Filename
Creates a new drawing file with the specified name.
Format
Determines the drawing file format for the resulting drawing file.
Bind
Determines how xrefs are treated when creating the new drawing.
YesBinds all xrefs to the drawing. Layers and other xref-dependent named objects are merged into the new drawing.
Maintains the xrefs as links to other drawings.
Bind Type
Determines how xref-dependent objects are treated when the Bind option is turned on.
BindMaintains the names of layers and other xref-dependent objects when binding xrefs.
Merges the names of xref-dependent objects into the new drawing without including the original file name.
Maintain
Determines how blocks within custom AEC objects are treated.
YesExplodes all block instances within custom AEC objects into basic objects. The resulting basic objects revert to their original properties rather than the properties of the block definitions.
Does not explode any block instances within custom AEC objects. The properties of the block instances are determined in the usual way, depending on how the objects in the blocks were created and the property settings of the layers on which the blocks are inserted.
Prefix
Specifies the prefix to be added to the current drawing file name.
Suffix
Specifies the suffix to be added to the current drawing file name.
?
List Settings
Lists the current settings for the command.