"New" Global Libraries - Parametric Object Creation?

[Kalib Stewart]

There's been a lot made about moving to global libraries, which hasn't actually done much, seeing as the Archicad libraries have barely evolved over the past decade... Still no claddings, still no parametric windows and doors, still only like 2-3 skylights, still very very limited fixtures, casework, and appliances. Half of my Toolkit is just CI tools and their Select Library.

With all this fuss about transitioning from one form of library pack to another form of library pack, are there any plans to finally allow us to create our own "parametric families (objects)" in both 2D and 3D? 

GDL is archaic and redundant for anyone trying to be productive design and documentation-wise; we don't have the time nor the desire to code so that I can make a 3D tap or a stretchable 2D symbol...And then test it for hours on end until I figure out where the single wrong line of code is.

Param-o is clunky and requires creating 10 blocks with 20 lines to create a four-leg table... Nice if you're experienced in Grasshopper, worthless if you're not.

And, the library part maker, at least in my experience, seems awfully slow and limited. There's also little to no available documentation available on how to even use it in an optimal fashion, and it seems I have to be doing it in separate files all the time.

So, for this 28 release/preview, are actually going to see any substantial improvements in our libraries or our library creation ability upon the release or before the end of this decade? This global library "feature" has so far been nothing but moving existing objects into new folders, and I could have done that in Windows Explorer and some website downloads.

This "Global International Library" has given me access to maybe 4 new useful objects...

It's been what, 10 years and for example there's still only one very limited vanity option.... 10 years with essentially the same limited library and no efficient ways to add to it. Is there actually any work at all going on in this area at GS?

Revit's had this mastered for years and it seems GS hasn't even started.

[Jim Allen]

Agreed, the GDL created from geometry capture is way too complex.

[mthd]

Architecture really doesn’t have much in common with Computer Programming or GDL script writing. Only that Archicad understands that language when library parts are made using it.

Architects are not script writers by any means but if you can use it to manipulate an existing library part then that all helps.

If you are paid to create custom objects via GDL for the AC library then it’s probably worth learning it ?

If you can learn to use LPM then that is probably a more logical way of creating 3D library parts for Architects. Most of us Designers and Architects understand 3D object creation with sketch up and Morphs.

I think we need to find a better way to edit 3D existing library parts like doors and window parameters without the need to use GDL to add new parameters.

Exploding a 3D library part and adding new parts could be done via the morph tool and then recombining the object back into an editable library part like a door or window ?

I don’t know much about library part creation but we all know lots about putting buildings together.

GS are at least trying hard by giving us these new options for library part creation.

[SeaGeoff]

Para-O is a dead end. Not powerful enough to replace GDL scripting, but not easy enough for wide adoption by users. To my mind LPM is the best option when something better than a basic save-as object is required. But clearly there is room for improvement, namely the addition of basic resizing parameters. Complex Profile Modifiers show how that could be done. This one (albeit massive) improvement would give us the graphic object creation power that we all want for our day-to-day needs while GDL remains available for more complex objects.

[Lukas Zeleny]

I fully agree that Archicad needs a simple way to create both static and parametric objects.

There are too many ways to create an object and each one has its own disadvantages. I have been working in Archada for many years but I never had enough time to learn GDL coding, I had  moments when I started but always hit the wall of complexity. The problem is that creating objects is a tiny percentage of the time in a normal project, so these skills are easily forgotten. I know only a few commands and tricks how to complete my objects in GDL code. I always make the base using a different method and then modifi it a little in GDL

In the office, we use three methods of making objects:
1. Save as - simple 2D symbols

2. Library part maker - has several unbearable bugs, such as the fact that if you use it to make more objects in the project, they start to disappear from the list, if you rename them, it still wants to save them under the original name, sometimes it "forgets" how you set the Details in object. But otherwise I consider it a quick solution for making a static object with 3D and representation according users wishes. But that's all, no parametrics, not even stretching

3. PARAM-O - my favorite and I'm sad it's ending. You cannot influence how the object will be displayed in 2D, that is its biggest weakness. Creating a series of objects as long as you have 2 or more is fine, until you suddenly want one. That's when it gets complicated. No hot editing points in object, everything must be done by editing numbers in object setting. The interface could also be more intuitive. But I have to say that after a few hours of stretching threads between the parameters, I got the hang of it and I can create even more complicated objects. In combination with the GDL code for geometries that are more difficult to make in it, it can be effective.

Yes, I need a user-friendly tool for creating objects so that we don't have to have specialists for such a basic thing
Yes, GDL is a powerful tool, but at the same time difficult to master, therefore it is not suitable for ordinary architectural practice.

PS: Imagine PARAM-O on steroids that could control other parts of the project in addition to libraries. For example, coding layouts, saving drawings to layouts, assigning parameters to objects according to their properties, creating expressions

Few PARAM-O examples in pictures. They are fully parametric, you can change size of tables, chairs, their material, how deep is the chair tucked under the table, Number of tables in circular one, angle of its rotation and so on.