When Grasshopper stops and Archicad begins

On April 1st, 2026 at 4:00 PM CEST — no April Fools’ joke — Severi Virolainen answered a question in McNeel’s Rhino User Webinar series that lands on the whiteboard at every competition kickoff at least once: When do I solve a problem with Grasshopper, and when does it belong in Archicad? The recording has been available free since April 2nd. If you haven’t seen it yet, you’re reading the right article right now.

←TODAY: Archicad 27 and Grasshopper run via Graphisoft’s Live Connection in the same European practices — but the handoff logic is mostly undocumented.
→3012: In the Sentinels Atelier, parametric model and BIM database are a single, versioned object — no export, no handbrake.
Fulcrum: Whoever draws the boundary between tools cleanly today builds tomorrow’s pipeline that makes this boundary obsolete.

Virolainen is no ordinary webinar speaker. He’s CEO of Algoritmi Oy in Helsinki, PhD candidate at Aalto University, and — this is the number that matters — he’s been programming GDL since 1987. Nearly 40 years with Archicad’s native scripting language, before Grasshopper even existed. Since 2016 he’s been an active Grasshopper user. This isn’t an academic overview; this is someone who knows both systems from the inside, the way a structural engineer knows his two design codes.

The McNeel blog flanked the webinar with two posts — announcement on March 24th and recording release on April 2nd — and both agree on the core point: it’s about practical workflows, about the boundaries of the platforms, and about small tricks with outsized impact. “Powerful small tricks that make a big difference” is the promise from the announcement. It sounds like marketing, but it’s the precise description of what actually eats time in BIM daily practice: not big architectural decisions, but the 47 mouse clicks for something you could have scripted.

The structural baseline: Graphisoft’s official Grasshopper–Archicad Live Connection plugin enables genuine data exchange between the two environments — not dumb geometry import, but bidirectional connectivity. Where exactly this connection breaks, under which Archicad versions, and which element types it tolerates, is the operational knowledge Virolainen brings. (If you haven’t watched the recording: that’s precisely the part no blog post can replace.)

For DACH practices working with SIA 2051 or the German BIM milestone plans, the question is especially sharp: Archicad is BIM-native, IFC-fluent, and deeply rooted in Central European architecture offices. Grasshopper is the tool when the building has logic that no Archicad tool maps directly — facade grids, structural optimization, generative floor plans. Setting the boundary right isn’t a style choice, it’s a question of model consistency in the submission BEP.

Atelier: In PAZ workflows, this decision appears regularly in the Grasshopper → Archicad pipeline: at PAZ Academy we maintain our own Grasshopper↔Archicad Library that personalises the workflow between the two and fills the missing parts of the current connection — so Grasshopper geometry becomes Archicad elements with true BIM attributes instead of stalling at that gap. Virolainen’s webinar approaches the same pain from workflow strategy; our library, from the data pipeline.

The recording is free, linked on the McNeel blog, and runs under the Rhino User Webinar program — a series that had over twenty publications in March 2026 alone, from Pragmatic Parametrics to Enscape for Rhino users. No paywall, no sign-up after the live event. That’s structurally cheaper than any course voucher.

Name the risk: The webinar sources cite neither the specific Live Connection plugin version nor Archicad version requirements. Anyone wanting to rebuild the setup directly needs to watch the recording — and should have the Graphisoft documentation open in parallel. “Practical tricks” without version control are sometimes just tricks for a version you no longer have.

Concrete next step: Watch the recording with your BIM coordinator together — not alone. The strategic question of where your practice draws the Grasshopper/Archicad boundary is a team decision, not a personal preference. After that, review the PAZ Grasshopper↔Archicad Library workflow and verify whether your JSON-API calls are already documented.

Source: McNeel Blog (Rhino)