While you are opening a solo project or joining/opening a TeamWork project, the following warning message appears and the Library won’t be loaded: "The Library contains one or more library parts whose path is too long; the library cannot be added to the Active Libraries.”
The downloaded Library (*.lcf) is corrupted or the User has no permission to the Library.
If you work on a solo project, check the Library (if it is needed the *.lcf file can be extracted with File > Libraries and Objects > Extract a Container... command) and remove the corrupt Library in the opened project (File > Libraries and Objects > Library Manager). If you work on a TeamWork project, reload the *.lcf Library loaded to server and remove the Library in the local data manager on the client computer. The client should reload the project. Check the User's permission right to the Library.
Nominal Size Setting Changes Window Width
If there are several windows placed on the floorplan with different width, with Reveal chosen. Under Basic Window Settings tab Window Size Setting has Wallhole Dimensions as Set as Nominal. And we select the windows and change Set as Nominal to Reveal Dimensions then the width of the selected windows will change to the same. (To the first selected one.)
This happens because under multiple selection the parameters changed in the settings dialogue are applied to all selected elements.( Parameters changed by the user and parameters received from the script.)
If we check in the "Retain Nominal Size on Change" option, then the new nominal size will usethe old nominal size. This way the width parameters won't be unified for all windows.
Library Part Makes Project Unusable
There are many symptoms:
Computer restarts after 3d window is opened
Disk Full message
Out of memory message
Teamwork project is non-responsive or crashes in anything other than plan or detail views
A library part used in the project was renamed using the Finder or File Explorer to the same name of a macro call used by it. This made the library part call itself ad infinitum (recursive). In the below example a table was renamed from the name ARCHICAD gave it "edv-tisch gelb1.gsm" to the name "edv-tisch gelb.gsm". The renaming lost its user several hours of work.
Please do not rename objects unless you are absolutely sure the library part does not use that name in a call to a macro.
File size grows because object are saved as binary data in the embedded library
Binary objects in embedded library increase file size 10-100 times.
When saving your model as custom library part (see steps: CreateCustomWindow), you have two saving options:
save as Editable GDL Script
save as Non-editable binary 3D data
If the binary option is used, then a "self-containing" object will be saved, that is, all attributes (line types, fill types, material texture) will be saved within the object. The material texture is saved in bitmap format. This is usually not a problem, since most ARCHICAD textures are small, but if the object uses a large image as texture, then the resulting file can be huge. (The size of a 1024 by 1024 bitmap is 3MB!) This is even more important if you are saving a series of similar objects using the same material. In this case the binary option means that the same bitmap is embedded in all of these .gsm files. This will bloat the library size, and slow down the library loading process.
When saving Library Parts from 3D use the ‘Editable GDL Script’ Format. This will reference texture maps, but will not embed it in the file. In this case you have to ensure that the referenced image is loaded with the libraries, but the referenced image can be a compressed file format (like jpeg).