<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Abnormaly HUGE objects in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134604#M18596</link>
    <description>Thanks for the answers - your suggestions were my first port of call...&lt;BR /&gt;
&lt;BR /&gt;
I have only the parts that I wish to save selected, there are no other elements present in the 3D window.. I have also opened the 3D/2D script(s) of the saved object and they are very short as expected.&lt;BR /&gt;
&lt;BR /&gt;
While testing where the problem might come from, I came across another problem, maybe there is a link?&lt;BR /&gt;
&lt;BR /&gt;
I copied the door I wished to save into a new project (so as to be sure that there was only the door in the project and no residual 3D in the RAM?), the jpeg texture I had applied came with it, so I changed the materials on the objects to default materials (all faces separately).&lt;BR /&gt;
&lt;BR /&gt;
When I saved the object it was still large (6.54Mo) AND it had saved the object with some materials that were not present in the constituent parts - in fact it kept the material from the original paste and not the material that I had asked it to show.</description>
    <pubDate>Fri, 19 Nov 2010 09:27:53 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2010-11-19T09:27:53Z</dc:date>
    <item>
      <title>Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134601#M18593</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I work with Archicad 13 and have run into a problem where when saving objects form the 3D window creates HUGE objects - the worst I have seen was a cube (6 polygons?) saved as a 45Mo file.&lt;BR /&gt;
&lt;BR /&gt;
Just today I created a custom door, which was rather quite simple, and ended up with a 177Mo object!&lt;BR /&gt;
&lt;BR /&gt;
The final size is seemingly random, an object ranging (for example) from 40Mo to 90Mo depending on when you save it. Also, sometimes (but not always) the same object, saved in a new project, can be much reduced.&lt;BR /&gt;
&lt;BR /&gt;
Saving the same object from the 2D window gives 50Ko files so there seems to be a problem specific to the 3D window. Therefore, when I can I save from 2D, but sometimes need the 3D window (different angle etc...).&lt;BR /&gt;
&lt;BR /&gt;
I have heard that others have had this problem, is there a work around? &lt;BR /&gt;
&lt;BR /&gt;
As we work on a BIM server, the objects are automatically embedded so before we realised where the problem was the file ended up at 664Mo (compressed) and started crashing ArchiCad as the computer did not have enough memory to backup the file. Taking out the offending objects reduced the file size by 600Mo.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 09:52:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134601#M18593</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-24T09:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134602#M18594</link>
      <description>Just wondering - do you have the elements actually sellected in 3D when you save them as an object or are you just saving the whole 3D window?&lt;BR /&gt;
Barry.</description>
      <pubDate>Fri, 19 Nov 2010 02:02:35 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134602#M18594</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2010-11-19T02:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134603#M18595</link>
      <description>Have you opened the object and had a look at the GDL code? The code should be fairly short if it's a simple piece of geometry.&lt;BR /&gt;
&lt;BR /&gt;
Select the object on the floorplan, then go to 'File'&amp;gt;'Libraries &amp;amp; Objects'&amp;gt;'Open Object' (or CTRL+SHIFT+O) to open.</description>
      <pubDate>Fri, 19 Nov 2010 02:58:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134603#M18595</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-11-19T02:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134604#M18596</link>
      <description>Thanks for the answers - your suggestions were my first port of call...&lt;BR /&gt;
&lt;BR /&gt;
I have only the parts that I wish to save selected, there are no other elements present in the 3D window.. I have also opened the 3D/2D script(s) of the saved object and they are very short as expected.&lt;BR /&gt;
&lt;BR /&gt;
While testing where the problem might come from, I came across another problem, maybe there is a link?&lt;BR /&gt;
&lt;BR /&gt;
I copied the door I wished to save into a new project (so as to be sure that there was only the door in the project and no residual 3D in the RAM?), the jpeg texture I had applied came with it, so I changed the materials on the objects to default materials (all faces separately).&lt;BR /&gt;
&lt;BR /&gt;
When I saved the object it was still large (6.54Mo) AND it had saved the object with some materials that were not present in the constituent parts - in fact it kept the material from the original paste and not the material that I had asked it to show.</description>
      <pubDate>Fri, 19 Nov 2010 09:27:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134604#M18596</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-11-19T09:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134605#M18597</link>
      <description>Anyone?</description>
      <pubDate>Tue, 23 Nov 2010 08:50:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134605#M18597</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-11-23T08:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134606#M18598</link>
      <description>I don't know about your problem and my advice maybe not worth much.  This doesn't' sound like a common problem as there is little response, and waiting days for an answer will probably extended into more days.  &lt;BR /&gt;
&lt;BR /&gt;
I would take a look at reinstalling and it's possible e your problem will be fixed sooner than later.  I had a problem with my REDO command not working and I solved it with a simple uninstall-reinstall of AC 14.  Took me about 15-20mins to do the whole thing (my setup is also simple so mileage may vary).</description>
      <pubDate>Tue, 23 Nov 2010 12:21:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134606#M18598</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-11-23T12:21:32Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134607#M18599</link>
      <description>I've never seen this issue mentioned by anyone else.  Best bet is to contact your technical support...</description>
      <pubDate>Tue, 23 Nov 2010 16:37:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134607#M18599</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2010-11-23T16:37:57Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134608#M18600</link>
      <description>FYI You are not alone, I have seen this before, but was never able to reproduce it. After a while I never had the problem again.</description>
      <pubDate>Tue, 23 Nov 2010 20:20:38 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134608#M18600</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-11-23T20:20:38Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134609#M18601</link>
      <description>Yup we ran into this problem seemed to be a feature in AC13 but mostly on specific machines. We could sometimes get round the problem by saving the object again but using a different PC. We also resorted to redoing the objects in AC12. We haven't come across the same problem with AC14.</description>
      <pubDate>Tue, 23 Nov 2010 22:14:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134609#M18601</guid>
      <dc:creator>fuzzytnth3</dc:creator>
      <dc:date>2010-11-23T22:14:54Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134610#M18602</link>
      <description>Check what materials are used on your object. When you save an object in binary format, that creates a "self-containing" object. That is, all the necessary textures are also saved into the object, so if you take that object into another project, the textures will not go missing. The texture is stored in bitmap format. So, if you are using textures that are in the hundred-kilobytes range in JPG format, then you might end up with objects several megabytes in size. Which is not good.&lt;BR /&gt;
&lt;BR /&gt;
Always use small files as texture. After all, it's just a texture. Using large images will not just create large objects, but will hurt rendering times too.</description>
      <pubDate>Mon, 29 Nov 2010 15:06:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134610#M18602</guid>
      <dc:creator>Greg Kmethy</dc:creator>
      <dc:date>2010-11-29T15:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: Abnormaly HUGE objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134611#M18603</link>
      <description>Thanks for the work-arounds, next time I run into the problem I'll try saving it from another machine to see what it does. We should also have a copy of AC12 kicking about somewhere as a fallback.&lt;BR /&gt;
&lt;BR /&gt;
As for the textures, I had suspected them, and what has been said about them being saved in binary makes sense - although I'm fairly certain that my 40Mo cube saved from the 3D window was with a default material, and 100% certain that the SAME cube, saved from 2D, gave a 8Ko file (among other examples).&lt;BR /&gt;
&lt;BR /&gt;
And if I understand the answers here, the problem doesn't seem to occur in AC14, and certainly didn't in AC11.&lt;BR /&gt;
&lt;BR /&gt;
Which takes me on to a similar problem, although this time I have a work-around ;&lt;BR /&gt;
&lt;BR /&gt;
When saving a module directly from the floor-plan (apologies if the terminology isn't quite correct - I've only ever worked in France) the file size is in the tens of Mo. The same elements (a couple of low-res jpegs a few lines and some text) saved from a "copy" ends up with a file in the low Ko's.&lt;BR /&gt;
&lt;BR /&gt;
We opened both modules and they both have exactly the same contents.&lt;BR /&gt;
&lt;BR /&gt;
As I said, we have an easy work-around by saving from a "copy" so it doesn't block us the way the 3D window, which is sometimes neccesary for certain more complex objects, does. It does seem that in AC13 depending on where you save it from, the same information can vary greatly in size.&lt;BR /&gt;
&lt;BR /&gt;
We have only upgraded to AC13 recently, and while we find many aspects much improved, the problem with huge objects will oblige us to fall back on older versions for more more complex buildings we do, unless that is the work-arounds mentioned help us. I can think of at least a couple of recent projects that just wouldn't have been possible with AC13 because of this problem, which is rather unfortunate.&lt;BR /&gt;
&lt;BR /&gt;
In any case, thanks for your answers and your time.</description>
      <pubDate>Tue, 14 Dec 2010 10:14:59 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Abnormaly-HUGE-objects/m-p/134611#M18603</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-12-14T10:14:59Z</dc:date>
    </item>
  </channel>
</rss>

