https://community.graphisoft.com/t5/Libraries-objects/Migration-libraries-reduction-workaround/m-p/137917#M17852 <DIV class="actalk-migrated-content"><T>This might have been covered before.<BR /> Some of our current projects are quite old, requiring down to AC7 libraries.<BR /> Even though migration libraries seem to reduce the amount of libraries that need to be loaded, they still add up to quite a number of library parts. The AC14 library alone is almost 200mb. The standard migration libraries can be more than 100mb, even though I use very few of the parts. <BR /> <BR /> To cut down loading time and prevent this, I've recently done the following:<BR /> - On an old project, make sure all the relevant libraries (including migration) folders are loaded. <BR /> - Exported the project to the .pla format.<BR /> - Open the .pla<BR /> - Extract the libraries to a separate folder. This only saves library parts that are in use.<BR /> - Delete the AC14 library from this folder.<BR /> - Load this folder, together with the latest library folder as library parts. <BR /> <BR /> On one project, the additional migration library I needed to load was less than 9mb. It sure beats having to load all the migration libraries and there's less chance of us using older libraries when working.</T></DIV> Fri, 26 Nov 2010 16:51:15 GMT Haneef Tayob 2010-11-26T16:51:15Z https://community.graphisoft.com/t5/Libraries-objects/Migration-libraries-reduction-workaround/m-p/137917#M17852 <DIV class="actalk-migrated-content"><T>This might have been covered before.<BR /> Some of our current projects are quite old, requiring down to AC7 libraries.<BR /> Even though migration libraries seem to reduce the amount of libraries that need to be loaded, they still add up to quite a number of library parts. The AC14 library alone is almost 200mb. The standard migration libraries can be more than 100mb, even though I use very few of the parts. <BR /> <BR /> To cut down loading time and prevent this, I've recently done the following:<BR /> - On an old project, make sure all the relevant libraries (including migration) folders are loaded. <BR /> - Exported the project to the .pla format.<BR /> - Open the .pla<BR /> - Extract the libraries to a separate folder. This only saves library parts that are in use.<BR /> - Delete the AC14 library from this folder.<BR /> - Load this folder, together with the latest library folder as library parts. <BR /> <BR /> On one project, the additional migration library I needed to load was less than 9mb. It sure beats having to load all the migration libraries and there's less chance of us using older libraries when working.</T></DIV> Fri, 26 Nov 2010 16:51:15 GMT https://community.graphisoft.com/t5/Libraries-objects/Migration-libraries-reduction-workaround/m-p/137917#M17852 Haneef Tayob 2010-11-26T16:51:15Z https://community.graphisoft.com/t5/Libraries-objects/Migration-libraries-reduction-workaround/m-p/137918#M17853 AC 14 has a nice feature for this: 'Embed placed objects of loaded libraries'<BR /> Use this feature to embed all the objects placed from a linked library or BIM Server Library into the project. <BR /> <BR /> <IMG src="http://www.graphisoft.com/ftp/publishing/ac14_help_INT/Files/images/EmbedObjects.png" /> Sun, 28 Nov 2010 15:58:49 GMT https://community.graphisoft.com/t5/Libraries-objects/Migration-libraries-reduction-workaround/m-p/137918#M17853 Anonymous 2010-11-28T15:58:49Z