Archicad 28 slow to start

[MarkT]

Just installed the latest hotfix (4001). Opened our template file and my timer got to 18:10 before I killed the process. Stuck on updating Lib data. It was slow before but now it's just ridiculous.

 

[Jaime-airc_digital]

Please provide feedback on this bug, as it is affecting the loading times of projects for most companies.

[SeaGeoff]

My team and I are also affected by this. When we switched to AC28 we did not convert to the Global Libraries because of reports of long load times such as this, and because we were hoping that additional features would be added to deal with the complexity of managing so many libraries. With AC29 we took the plunge and switched to the new libraries but none of those improvements have been made by Graphisoft.

In addition to very slow load times we are missing the ability to update all of the libpacks on our BIMcloud in one shot, and the promised ability to change library defaults without having to manually edit a JSON file with over 1,500,000 lines of code.

All of these issues have been reported multiple times here on the forums. Graphisoft might be enjoying the supposed benefits of the global libraries, but so far they have just made using Archicad  slower and more frustrating for the rest of us.

[Jaime-airc_digital]

[Sarcastic mode ON]

While we wait for the development team to address why a process that used to take 30 seconds now takes several minutes, here is a "manual patch" for your sanity:

The Workaround: Spam-click the Stop button (approx. 40 times) during the "Updating local library data" phase.

This bypasses the loop and returns the loading time to pre-AC28 speeds. It works for opening projects, updating libraries, and even IFC links. If Graphisoft won’t give us back those lost minutes of our lives, I guess we’ll just have to click our way out of it.

Thanks for the finger workout, Graphisoft!

[marcoariveross]

Hi Jaime, I thought it was a recent problem... We're having this problem with Archicad 29... there's no sign of a solution, and it's pointless to pay for Bimcloud as a service. I'd rather stick with my basic Bimcloud...

[ricki-fritz]

Hi all, thought I'd try a test and share my results (& pain) with anyone still struggling with this.

Here's what I tried: extracted ALL the Graphisoft *.libpacks and compiled them into:

1. Merged ArchiCAD29 library  *.libpack, and
2. Merged ArchiCAD Libraries 29 *.LCF file.
3. First Colum (Status Quo) is the current setup with all the Graphisoft *.libpacks separate

Also tested whether the file being Solo or on Teamwork made a different

And where the Library was hosted: locally (our P: drive) or on BIIMCloud Basic - if I have time will do this on SaaS as well, but I suspect this will have longer load times)

This defeats some of the goals of the global libraries as the Merged LCF and libpack will no longer be able to do the live check (which I suspect may be part of the problem anyway). I also stripped out any mapping and translation files for simplicity

[Laszlo Nagy]

So, if I understand right:

• If you work on a Solo file, the OOTB individual Lib Packs loaded from your computer's storage device are about as fast as a merged Lib Pack file loaded from your computer or from the BIMcloud Basic server. No reason to create merged Lib Packs for load time reasons.
• If you work on a Teamwork file and use BIMcloud Basic (on-premise BIMcloud), the merged Lib Pack is the clear winner.
• The merged LCF is never a good choice.

[ricki-fritz]

That's correct @Laszlo Nagy   - so this would make loading BIMCloud libraries for Teamwork Projects simpler

But you'd need to recombine when there's a Global Library update that your firm required.