Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Why do exploded views cause extreme increase in dwg file size?
Why do exploded views cause extreme increase in dwg file size?
I was working with a drawing which has 1256 parts... When this drawing was done with a single sheet, single exploded view, the drawing file size was 5.0MB, when the drawing was done with 11 views (orthographic, detail, and section) over 3 sheets the drawing file size was 2.2MB (56% smaller).
Any ideas from anyone... for what is going on behind the scenes to cause this?
Perhaps there are more entities in the single
iso exploded than the others combined? Also consider that perhaps
there are alot of plines used in representing the geo. in the iso exploded
view (a single pline which takes more bytes to describe than a single
line).
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">I
was working with a drawing which has 1256 parts... When this drawing was done
with a single sheet, single exploded view, the drawing file size was 5.0MB,
when the drawing was done with 11 views (orthographic, detail, and section)
over 3 sheets the drawing file size was 2.2MB (56% smaller).
Any ideas from anyone... for what is going on behind the scenes to cause
this?
Thanks Dave... guess we need to remember that IDW views are based on CAD principles (i.e. plines, lines, etc)... and not from some form of magical "vector" display system that does not increase in file size!
I was just reading the thread from Oct/09/03 "does size matter?"... we are going to do some experimentation with using "design-views" in the assembly models... and thus, apply them in the design views of the drawings.
My guess is that this should help performance when the views go precise... and also help speed up the "BackAHL.exe” process… not sure however high file size will be affected?
I should also bring up an important point… I posted this thread to satisfy my curiosity and understand the process… I am not “whining” about the file size increase… one needs to keep things in perspective. The minimal cost of extra storage space is meaningless compared to the value of a clearly communicated design concept!
When I read your post I had interpreted (in err and
I don't know why I did cuz you surely didn't imply) it in the context of a DWG
file and not and IDW file. I have no idea how entities are stored in an
idw (if at all) and whether my logic applies to IDW. Though I do expect it
would apply to a file exported to DWG from IDW.
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">Thanks
Dave... guess we need to remember that IDW views are based on CAD principles
(i.e. plines, lines, etc)... and not from some form of magical "vector"
display system that does not increase in file size!
I was just reading the thread from Oct/09/03 "does size matter?"... we are
going to do some experimentation with using "design-views" in the assembly
models... and thus, apply them in the design views of the drawings.
My guess is that this should help performance when the views go precise...
and also help speed up the "BackAHL.exe” process… not sure however high file
size will be affected?
I should also bring up an important point… I posted this thread to satisfy
my curiosity and understand the process… I am not “whining” about the file
size increase… one needs to keep things in perspective. The minimal cost of
extra storage space is meaningless compared to the value of a clearly
communicated design concept!
Well... I guess if IDW views have the ability to "scale", and individual line "elements" within the view can be deleted... then it is "vector" based system. So I feel your logic does apply... it seems natural that more entities in a view (and the complexity of them)... will require more data (thus larger files) to represent the view. Which, from my assumption... is a "2D profile" of the model projected onto a sketch plane. Maybe somebody from Adsk can give us a brief explanation?... or maybe somebody else can point us to publish docs on the topic?
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")