Library pack has wrong subversion?

[Patrick M]

what does this even mean? these .libpacks seem to have only simplified archicad for one group of people... and its not us at the end user side.

Operating system used: Mac Apple Silicon

 

[runxel]

Well, only the "normal" object library is backwards and forwards compatible – the MEP library on the other side is always tied to the version, and will probably stay like that for a while.

So my guess is there is a version mismatch here between AC and the library.

[Patrick M]

very strange... these are all libraries uploaded from the AC29 applications folder; nothing from 28 is on that server

[furtonb]

Same error, I've never seen this before.

This file was just uploaded from a .pln to a BIMcloud:

The problematic .libpack files are on the BIMcloud, the file was started in AC29.

How to resolve this?

[furtonb]

I think I found it: make sure to update your libraries too...

[Lingwisyer]

Yeah, the libpack updates are not backwards compatible. So if one person updates theirs, everyone needs to update.

[runxel]

---

@Lingwisyer  schrieb:

Yeah, the libpack updates are not backwards compatible. So if one person updates theirs, everyone needs to update.

---

Wait,.... what??? Are you sure?

Wasn't that the whole and sole reason to switch to the global library?

Man this gets dumber by the day.

[Patrick M]

I'm like 90% certain the whole reason to switch from .lcf to .libpack was less work on the software developers side... on the user side, it takes a software developers understanding of the tool to get a file's libraries sorted out any more.
I mean, take 1 library + a migration library and turn it into 40 separate libraries that all still need to speak to each other in some capacity (macros, etc.), and need to be coordinated for updates individually... yeah, this wasn't for the benefit of anyone on the user end of things.

[Lingwisyer]

Clarification: they are AC version "backwards compatible", but not Library version backwards compatible.

*Apparently some of the objects added with the library update post AC29 are not compatible in AC28... It was mentioned in the library update release post. I have not used or checked any of them.

[Lingwisyer]

Yeah, I do not get why AC cannot just read a folder of Libpacks. Sure, libpacks give the user more flexibility, but most do not need it... Just give the user a folder of their localised libraries that they can add to if they need to.

eg. I just load "Library (AUS)" folder and I get all of the generic and AUS library parts. If I want the "Japanese Arhcitecture" library, I just copy it from "Other Libraries"  folder into "Library (AUS) folder.

Ling.