The Global Archicad Community

Stay informed. Get help. Share your knowledge.

Topics specific to the scripting and development of Library Parts and Libraries using Param-O or the Geometric Description Language – GDL. (Example: How do you use “REQUEST” GDL commands?)

Moderators: Karl Ottenstein, LaszloNagy, ejrolon, Barry Kelly, Gordana Radonic, nbalogh, mnguyen, gkmethy, rmasaki, Akos Somorjai, Csilla Mai, Peter Baksa

#320104
I would hope that GS is not trying to catch up with Rhino/GH for "formal, architectural design" functionality. I would rather improve a lot more the AC-Grasshopper Connection for that use cases - like that second topic her: https://www.rhino3d.com/7/new/

I see PARAM-O more as a tool to structure objects in hierarchies with capabilities for scheduling and geometrical flexibility - like an enhanced version the family editor of Revit.
#320110
GH is a interface for Rhino API.

We should expect the same from param-O. IMO trying to mimic GH functionality because they "look the same thing" it's a mistake.

By the other hand, Archicad exposes multiple API, and reading what people is expecting from param-O, it seems that people expects an UI only for GDL API: i.e. a tool for developing geometry. Nothing wrong with this. Just don't expect the power of Rhino's geometry engine. McNeel spent decades working on this.

Now, what about the rest of the API's? what about managing documentation, attributes, issues, connecting Archicad with external app (Excel, PowerBI) or the WWW...

Programming geometry is very cool, but in the end of the day, it doesn't fit well in production. Projects changes a lot and maintaining an algorithm according to these changes is extremely tricky. Spaguetti mosters et al.

Managing information, that's the real deal IMO.
#320114
How long has Graphisoft spent to develop ArchiCAD? It has started working on that “parametric software” since 1980s.
#320127
Archicad also has been developed "for decades", sure.

The difference is that McNeel has been developing mainly the "geometry engine" while Archicad's is a BIM tool (documentation, collaboration, issue management, IFC support... In comparison, Rhino's support for all these functionalities is (almost) inexistent.

But geometry in Archicad is mainly based on primitive solids and discretized curves. And this is ok IMO. Good enough for 99% of the architectural projects. Digital Project from Ghery technologies was developed to support the geometry limitations of BIM tools like ArchiCAD.

Rhno and Archicad. Two apps, two purposes.

By the way, Archicad is already 'very' parametric software, isn't it? Certainly, not the same explicit parametric modelling paradigm as in Digital Projects, for example, but still parametric. Maybe you are looking for a different app?
#320133
Certainly, Param-o need not follow the same path as the Rhino with the Grasshopper with decades of development, and spend all the energy on manipulating geometry.
But the BIM "I" information is missing (and it is extremely necessary). For now it is possible to build simple "M" models in Param-o, I believe that small and simple implementations to extract information can add a lot to the application.

---> 1 - Extract lists of these geometries;
1.1 - number of pieces;
1.1.1 - dimensions of the parts;
1.1.2 - orientation of the parts;
1.1.3 - surface of the pieces;
"" 1.1.4 "-" material "of the pieces;"

(We already have a way to make lists like that with doors and windows. But now would be a good time to expand the details with a magnifying glass and refine the precision, to be able to participate in the construction of building elements)
(and probably the archicad already has this "list", because in order to be able to draw the elements on the screen, it probably needs this "list")

---> 2 - To be able to add "materials" to these geometries and validate point 1.1.4. (ok this is a little irrelevant, but it would be good to generate plans, and budgets)

These solutions are simple and of great advancement in the application.
The "I" information of the "M" model enables the "B" construction. In short, we will have BIM within Param-o. :D


ImageImage
#321346
leceta wrote: Sat Dec 12, 2020 1:07 pm Archicad also has been developed "for decades", sure.

The difference is that McNeel has been developing mainly the "geometry engine" while Archicad's is a BIM tool (documentation, collaboration, issue management, IFC support... In comparison, Rhino's support for all these functionalities is (almost) inexistent.

But geometry in Archicad is mainly based on primitive solids and discretized curves. And this is ok IMO. Good enough for 99% of the architectural projects. Digital Project from Ghery technologies was developed to support the geometry limitations of BIM tools like ArchiCAD.

Rhno and Archicad. Two apps, two purposes.

By the way, Archicad is already 'very' parametric software, isn't it? Certainly, not the same explicit parametric modelling paradigm as in Digital Projects, for example, but still parametric. Maybe you are looking for a different app?


Just a point of note...

Digital Project is actually a repurposed version of CATIA - which was actually developed and initially released earlier than ArchiCAD.
(it was developed in '77 and initially released in 1982)
Frank Gehry's company was the one that first used CATIA in the late '80's/early '90's to help him design and realize the famous Guggenheim Bilbao Museum, and in the late 1990's they repurposed the software in-house to help them design buildings and designs with that curvilinear style and irregular form and to end up with what's now known as Digital Project.
#321356
PARAM-O looks like a proof of concept plugin at the moment with quite limited functionality. When can we expect the macOS release? Are further nodes planned?
https://helpcenter.graphisoft.com/user- ... ter/85692/

Right now both the GH-connection and PARAM-O is half-baked in my experience. Rhino.Inside.Revit looks extremely powerful in comparison, having a robust connection to the Rhino-GH ecosystem is a getting invaluable, prototyping custom tools or workflows for ARCHICAD has a very high threshold compared to it.

Accessing and mixing building material-, object- and project level properties and attributes, passing parameters based on context is not really doable in either solution right now.