on
2016-12-26
05:34 PM
- edited on
2021-11-23
07:45 PM
by
Emoke Csikos
Issue
Cause
Solution
Issue
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.”
Cause
The downloaded Library (*.lcf) is corrupted or the User has no permission to the Library.
Solution
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.Issue
Cause
Solution
Issue
There are many symptoms:Cause
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.
Solution
Please do not rename objects unless you are absolutely sure the library part does not use that name in a call to a macro.Issue
Binary objects in embedded library increase file size 10-100 times.Cause
When saving your model as custom library part (see steps: CreateCustomWindow), you have two saving options:Solution
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).