Very Slow when open any teamwork project

[Karim L Sayed]

 

The user experiences significant delays during the startup phase of a Teamwork project in Archicad. The issue is characterized by two main symptoms:

1. Slow Project Opening: The project takes an unusually long time to become accessible.

2. Repeated Library Loading: The Archicad libraries are loaded from scratch every time the project file is opened, rather than being cached for faster access.

[Lee Hankins]

Teamwork files can take a long time to open if you have imported content from other locations such as jpegs, PDFs and hot link modules stored locally in to the project file. 

The best way to address this is to break the links to the files stored locally (they can always be relinked later) and upload the hotlink modules to the same BIMcloud. 

Lots of people Embedded Library parts can also cause a slow down. 

I share your frustration with the teamwork files seeming to re-load the libraries every time the project is opened. I have been assured this isn’t actually the case and it’s just Archicad checking for updates to the loaded Libraries. You should notice the loading of libraries is quicker once the project has been opened for the first time. 

Opening of Teamwork files can also be significantly affected by your broadband speed if you are using BIMcloud SAAS. 

[DOWA]

Hi,

we are having a similar problem in our office.
How do you upload your Hotlinks to BIMcloud?

They all have to be Teamwork files? BIMcloud doesn`t let you upload a pln.
We have a very complex project with one teamwork master file with site plan and anew building and many existing buildings which are .plns and are loaded as Hotlinks.
Do we have to make each one of them a Teamwork file?

Thanks