Library Migration issue with door and windows (Monolithic>Libpack)

Kevin Lee — Wed, 20 Aug 2025 22:59:48 GMT

I don’t believe this is a bug—more likely something I’ve missed during the lib-pack migration process.

Background:
We skipped AC28 and am now transitioning directly to AC29. For the new library pack, I’m happy to implement most of the predefined contents, but I’ve needed to tweak a few door objects.

We’ve been using standard Archicad doors and windows successfully in the past. I made some minor edits to add a function, which worked well up to AC27. My process for AC29 was to export the built-in doors and windows, apply the same modifications, then link the updated versions while removing the built-in ones.

Everything seems to be working fine—except for one issue: hotspots are not functioning as expected.

For example:

The door leaf doesn’t respond to hotspot interaction (e.g., opening/closing), though I can still manually enter the opening angle.
Editable sash frames are no longer adjustable via hotspots. it always goes back to the original position

The only modification I made to the GS doors was adding macro calls to show the clear path around the door, which is controlled via MVO settings.

Is there anything Im missing from the migration process ? Has anyone experienced similar issue?

Re: Library Migration issue with door and windows (Monolithic>Libpack)

Lingwisyer — Thu, 21 Aug 2025 08:18:19 GMT

Sounds like you have done better than me... Libpacks broke all of my custom doors and windows that used GS macros. I basically had to extract all of the default macros that were used into a seperate folder to load in order to get them to generate... some still do not work...

https://community.graphisoft.com/t5/GDL/GDL-amp-the-Global-Library/td-p/669680

topic Re: Library Migration issue with door and windows (Monolithic>Libpack) in GDL

Library Migration issue with door and windows (Monolithic>Libpack)

Re: Library Migration issue with door and windows (Monolithic>Libpack)