topic Re: libpack and object organization in Libraries & objects

libpack and object organization

Patrick M — Wed, 12 Nov 2025 22:40:47 GMT

if I start a project from any of the USA templates available, my objects show with the CSI structure we are used to seeing.
if I migrate a project, and match the .libpacks loaded into the the template, the migrated project shows with the international structure... even though I have no INT or alternative language .libpacks loaded.
I understand this is a "feature"; when loading multiple language .libpacks, it defaults to the international structure. But I don't have anything loaded in the migrated project that isn't part of the USA default library structure.
Am I missing a setting somewhere to organize my objects, windows, doors, etc.? or is this just a big **** *** to GSNA people?
It seems like a petty thing. I don't mind learning a new structure and UI; but it should be consistent for new files vs migrated files. Its the inconsistency and no way to resolve it that is killing me.

screen shot 1: OOTB USA template file's library manager on the left, migrated file's library manager on the right

screen shot 2: OOTB template object tool organization on the left, migrated files object tool organization on the right

Operating system used: Mac Apple Silicon

Re: libpack and object organization

Barry Kelly — Thu, 13 Nov 2025 00:26:25 GMT

There is a command called 'Library Localisation Preferences"/

Your USA 29 template is already set to use the USA preferences (even though it won't show this - see later).

Your old files will not have this set, so you need to do it.

How?...

Open the 'Edit GDL Library parts' palette.

Then click on the 'Library Developer' command and choose 'Library Localisation Preferences'/

This will bring up this dialogue where you can choose the USA localisation.

This should now show the library in the format you want.

Although it says that if the list is empty, then it will use the localisation of your Archicad program.

So it should be using USA localisation, unless there is something in your list already?

But there is no harm in setting this.

Barry.

Re: libpack and object organization

Patrick M — Thu, 13 Nov 2025 17:48:46 GMT

Barry! you are freaking amazing!
I knew there had to be a way to do it!

If you have any other magic in your bag of tricks... any chance you know a way to open a 27 file, load the libraries, and NOT have 250 missing parts? seems absurd to migrate a project then need to redo every window, door, and object in the file... but I guess thats the pains of moving to AC29?
Maybe a topic for another thread

Re: libpack and object organization

Barry Kelly — Thu, 13 Nov 2025 01:13:21 GMT

Glad it worked.

As for migrating old files, there is no easy way other than manually swapping each object.

Or just keep using the old libraries.

https://community.graphisoft.com/t5/Libraries-objects/Archicad-28-Migration-Converting-from-Monolithic-Libraries-to/ta-p/631549

There are some other post around about it as well.

Personally I think migrating every old job will be too tedious.

Do it for your company template and get that correct.

But old jobs open in 28 or 29, but just keep using the old libraries.

Barry.

Re: libpack and object organization

Kpetrocheilou — Fri, 19 Dec 2025 10:09:33 GMT

This makes no sense, to be honest. So if we have a project full of Doors 27, there is no automatic way to make them all just Doors (based on AC29 libpack system), right? It's hard to believe!

So the new Library system of AC29 is to be used only in new projects, or if you manually update one by one the objects/elements of an existing project.

So we need to keep using the Library 27, and avoid migration every time we open the project. When we choose to migrate, the library parts are missing, as there is no Door 29..

Am I understanding something wrong?

Re: libpack and object organization

Barry Kelly — Fri, 19 Dec 2025 11:56:14 GMT

I can't say I have tried this but I am sure I read it in a post somewhere here.

You could select the missing objects by name (i.e. all of the same name objects) at once and then swap them for the 29 equivalent using the CTRL+ALT inject option (CMD+ALT on a Mac?) as you choose the new library object.

I am not sure if the object are the same but different sizes, if those sizes transfer or if they all become the same size.

But this is not something you would probably want to do for every file.

Just your template for future jobs.

Keep existing ones using the old libraries.

There is also something else I am yet to try.

Central Innovation have a tool for migrating 27 library objects to the global library objects.

https://centralinnovation.com/resources/ci-launchpad-migrating-project-libraries

As I said, I have not used it so can't tell you anything about it.

Barry.