topic Re: Consolidate .lcf + .libpack systems in migrated projects in Libraries & objects

Consolidate .lcf + .libpack systems in migrated projects

Patrick M — Thu, 19 Mar 2026 19:01:02 GMT

in projects started before 29 (or technically before 28), the 27 library + migration library are essential. For teams who mistakenly add in the .libpacks, it seems to have catastrophic repercussion, at least as far as the library loading report is concerned.
I have whittled it down to where there are either hundreds missing objects, or 1000+ duplicated UI components.
...
anyone have any tips on fixing this, short of putting the project on hold for a week or more so I can trudge through and replace all 27.lcf elements with updated .libpack elements?
It's not as simple as replacing, as I've found the "inject to new library part" trick does not retain the adjusted parameters, size, etc. in the .libpack based elements. Additionally, I need to tear apart the .lcf, since there are STILL elements missing in the .libpacks from the 27 .lcf libraries.
...
I know Jared did a great video that covered most of this... but at this point, I have to just tell the team, they are going to see 1200 duplicates in their library manager. I don't have time for something that should be a simple button "consolidate UI library parts"

Re: Consolidate .lcf + .libpack systems in migrated projects

Barry Kelly — Fri, 20 Mar 2026 02:40:49 GMT

Being an older file, I assume most of the objects will be 27 + migration objects.

If not to many 28/29 global objects have been placed, it may be easier to remove the libpacks and deal wit a few missing object, replacing them with old 27 ones.

But if a lot of 28/29 objects have been placed then it is manually convert one way or the other or live with the mess of having both libraries loaded.

I am not sure if I am imagining things, but I think I saw something from Central Innovation where they converted old objects to the new library packs.

Or maybe it is just to do with the CI libraries?

If I can remember what it was, I will post back.

Barry.

Re: Consolidate .lcf + .libpack systems in migrated projects

Patrick M — Fri, 20 Mar 2026 02:55:41 GMT

yes, c/i is still providing current .lcf. all our projects are using the 27 library + 29 cadimage lcf
but I have 100+ people and 40+ projects... so things naturally go rogue from time to time. Some teams decided more libraries are more better... and added everything.
And since archicad doesn't restrict this, some chair 27 are placed and the equivalent generic chair are placed. If i eleminate the .lcf, I lose chair 27. If I eliminate the libpack, I lose generic chair.
and there's no mechanism to consolidate and say "chair 27 = generic chair"

...

so lots of missing or duplicates... no way around it

Re: Consolidate .lcf + .libpack systems in migrated projects

Lingwisyer — Fri, 20 Mar 2026 05:50:19 GMT

Time to remove the ability to add new libraries from most of your users...

Re: Consolidate .lcf + .libpack systems in migrated projects

Patrick M — Fri, 20 Mar 2026 14:20:42 GMT

yeah, if only I had BIM coordinators to pick up that slack...