Abnormaly HUGE objects

[Anonymous]

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.

Just today I created a custom door, which was rather quite simple, and ended up with a 177Mo object!

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.

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...).

I have heard that others have had this problem, is there a work around?

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.

[Barry Kelly]

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?
Barry.

[Anonymous]

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.

Select the object on the floorplan, then go to 'File'>'Libraries & Objects'>'Open Object' (or CTRL+SHIFT+O) to open.

[Anonymous]

Thanks for the answers - your suggestions were my first port of call...

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.

While testing where the problem might come from, I came across another problem, maybe there is a link?

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).

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.

[Anonymous]

Anyone?

[Anonymous]

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.

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).

[Karl Ottenstein]

I've never seen this issue mentioned by anyone else. Best bet is to contact your technical support...

[Anonymous]

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.

[fuzzytnth3]

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.

[Greg Kmethy]

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.

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.