Yes! I just mentioned that to tech support in North America. While we have NOT seen this using an Iceberg model, we have other exports. In one case of a partial site plan file (very large site), previous exports were 15 MB, now 300 MB saved from my Mac or 95 MB saved from a Windows PC. As far as I can tell, we used the same procedure and very little changed information. Seems to have occurred since last Hotfix update, 6004.
I have had a response from Graphisoft which I thought warranted sharing here
Apparently the problem arises because of a "bug" fix. In my opinion its not a "bug" and didnt need fixing.
Their response was as follows:
The reason for having more classification items compared to AC24's module is due to the fix for defect DEF-406 (Properties of hotlink lost their unused classification).
Previously we did not save every classification of those which were necessary to preserve the availability of the properties' and this caused problems. Now if we save a property then we save those classification items which are in a property's availability and this results in an increased size.
As a result we would suggest reconsidering the availabilities of the used properties in the project file, especially if it is really necessary for some of the properties to be available for every classification under UniClass 2015.
Otherwise, we can put a registry key to alter this behavior, at the cost of reversing the fix for DEF-406: - On macOS: under /Users/<user>/Library/Preferences/com.graphisoft.AC-version.plist - On Windows: HKEY_CURRENT_USER/Software/Graphisoft/Archicad/Archicad-version Create the key Module File and within it a value named SaveMinimalClassificationSet (REG_DWORD) set to 1.
This sets AC back to the previous functionality in AC24
My thoughts are:
So my understanding is that this "bug" occured when people placed mod files with conflicting classification systems - which is an easy fix for the user
the "fix" requires the user to update their template and restrict the availability of classifications. This is not an easy fix for the user.
this is compounded by the fact that classifications and properties cant be applied to mod files once placed.
I wouldnt have considered it a bug that nees to be fixed.
From a user point of view the flexibillity of being able to model a component using whatever tool I like and calssify it following that is one of the best things about Archicad.
This will become a problem for tech support once larger firms start migrating to Archicad 25
Here are my proposed solutions.
1. Allow MOD files to have properties and classifications applied in place. :0)
2. Allow the control of this behaviour on export within mod file options dialogue within in publisher/save selection as process.
3. Allow control of this behaviour on import within hotlink module settings dialogue.