AC28 Teamwork - Cannot load local libraries

[Algimantas Kuprenas]

Hello,

Just started working with AC28 - 28.0.2 version and got missing thing in Library manager. I'am unable to add local libraries into Teamwork files, only Libraries from BIMcloud server can be added. Cannot add these "NEW GLOBAL" libraries from C: drive. For non-Teamwork projects local libraries can be added as it was on all previous AC versions.

[BerndSchwarzenbacher · Accepted solution]

I think it was always like this? At least for AC26 & AC27 I just checked and for TW Projects I can only add TW Libraries. I mean, it kind of makes sense. Otherwise how would another user have access to your local libraries?

If you want to make a local library available, you can upload it via "Manage BIMCloud Libraries" and then include it.

[John Adams]

This solution may be correct but does not work well for point clouds that require and LCF file. I don't want to project specific load point clouds into the BimServer libraries. I want the point cloud library to be "locally" available, like the embedded library. 

So for me this process with the BimCloud libraries is not a good solution.

[Davor P]

Good practice is to have office wide libraries in a central location, then create a project library folder inside project on BIMcloud. Anything project specific - add there.

[John Adams]

As far as I know, Bimcloud Basic does not allow folders for the libraries, and I am not willing to go to BimCloud SAAS. Prefer to host my own BimCloud locally. 

(A point of frustration for me with Graphisoft's subscription service model.)

[Laszlo Nagy]

BIMcloud Help says you can upgrade your BIMcloud Basic to the licensed BIMcloud version and it even provides a link in the relevant page of the BIMcloud Manager. Here is the Help page talking about this:

https://help.graphisoft.com/BC/INT/index.htm#t=Topics%2FBCWelcome_Topics%2Ft_UpgradetoBC.html

I don't know if this "licenced version" is BIMcloud SaaS or on-prem BIMcloud, I suspect that it is on-prem BIMcloud. Hopefully, if you follow the link or ask your local reseller, you can find out.

But this page on the Graphisoft website shows a comparison of the 3 different versions:

https://www.graphisoft.com/en-us/plans-and-products/bimcloud/#compare

[John Adams]

But I don't want to upgrade to be able to load a point cloud file and not clutter my BimCloud libraries with point clouds for various projects. This appears to be an example of Graphisoft downgrading functionality that was previously provided with BimCloud Basic.

Here is a screenshot of how a previous project worked with "Libraries in Project" listed at the top. I don't know if this was only possible with the old library structure, but I can't get it to work this way on a new project.

So in brief what I want to do (and I was able to do before V28):

1. Use BimCloud Basic for AC libraries and Office standards
2. Import project-specific point Clouds which require a LCF file.
3. Load that LCF file locally as "Libraries of Project", similar to how the embedded library works.

Right now, all I can figure out how to do is load all my project-specific LCF files in the BimCloud Library folder, and this is a real mess.

John

ArchiCAD v9 -v29 USA
Mac Computers -current iMacs, Mac Studio and Mac Book Pros

[max_min]

"Libraries in project" always appears even if you are loading libraries from BIMcloud.

All the libraries that appear in the screen shot you shared are BIMCloud libraries, none of them are local linked libraries as indicated by the hexagon icon which means its a BIMcloud library. The reason why they appear separate to the ones on the second section where all the libpacks are is likely because they were being loaded from a different BIMcloud with a different address (http://192.168.0.3:28000)

When I used BIMcloud Basic I always gave the resulting pointcloud lcf file a suffix that way they all tiled at the end of my libraries when I uploaded it as a BIMcloud Library. So for example: "z_PC_ProjectName.lcf" That way you can at least keep them neatly in one area, and you can delete them when the project is done.