ArchiCAD 29.2.1 — Mac version

Take the stretched dimension text on a migrated project — 29.2.1 catches that before it becomes a construction headache. It’s a small fix in a hotfix list, but it says a lot about the kind of modeling environment GRAPHISOFT maintains.

Building and adjusting the model

The core modeling tools let you shape walls, slabs, roofs and custom elements without leaving the BIM logic behind. When you rotate an object, the updated Rotate command no longer skips a beat on the last input, so fine-tuning angles stays fast.

Working with outside specialists

Not every consultant runs the same software. ArchiCAD exchanges data with structural engineers, MEP designers and other specialists, and you can pull in third-party BIM components right from the integrated web portal without hunting through file folders.

Keeping a team in sync

Teamwork Send and Receive on BIMcloud SaaS now completes in a predictable window — no more staring at a slow progress bar. Whether you’re working solo on a small retail build or sharing a model with three colleagues, the sync feels like a background thought, not a scheduled event.

In daily use on an Apple Silicon Mac, ArchiCAD 29.2.1 feels like a heavy-duty tool that knows how to stay out of your way. Launch time is reasonable for an app of this scale — grab a coffee, not lunch. Once the project is open, orbit, pan and zoom in the 3D window stay fluid on a recent MacBook Pro, even with a full MEP coordination model loaded. Memory pressure sits around 6–8 GB on a mid-size residential project with a dozen layout sheets; the system stays responsive enough to keep Mail and a reference PDF open alongside without swapping. The hotfix specifically smooths out a glitch where scrolling through the Attributes palette could beachball and crash, and after the update that friction is gone. Section and elevation regeneration still takes a few seconds on complex geometry — it’s doing real math, not playing animation — but the progress indicator is honest and the result doesn’t need a redraw refresh afterward.

Setting storey heights before you draw a single wall

New users coming from sketch-based CAD often treat ArchiCAD like a drawing board rather than a database. Here are the mistakes I see over and over:

• Drawing walls without setting storey heights first. Everything snaps to the default 3-meter level, and later adjusting a dozen wall tops one by one is a slow form of regret.
• Ignoring the Navigator palette. Views, layouts and the publisher set live there. Trying to control sheet output without it is like cooking without a recipe — possible, but unnecessarily messy.
• Placing objects without checking their classification. A chair that thinks it’s a plumbing fixture throws off schedules, and tracing that later wastes an afternoon.
• Working solo in a Teamwork file without reserving elements. It works until someone else opens the project, then the ownership conflicts start and the undo history evaporates.
• Using the wrong origin point for external surveys. Shifted dimensions in migrated projects were a known headache that 29.2.1 specifically addresses — but bringing in survey data at the wrong coordinates can still offset an entire building from the site mesh.

Tip: spend an hour setting up favorites, view maps and your default template before modeling anything real. It pays back tenfold by the first design review.

Importing the engineer’s IFC for a three-unit townhouse

Think of a two-person studio — one partner handles client meetings and detailing, the other runs the model and coordinates consultants. They’re working on a three-unit townhouse in Portland. The structural engineer sends back an IFC file with revised beam positions last night. On opening the project, ArchiCAD flags the changed elements in the revision manager. The architect merges the new beams, checks the clashes against the ceiling slab with the built-in collision detection, and adjusts a few partition walls that now intersect a steel member. The zone tool recalculates net areas automatically — the hotfix means the area values in the schedule match the model without a manual override. By lunch, the updated floor plans and a clash report go out through the publisher as PDFs. No exports, no separate clash tool, no re-drafting.

From concept mass to construction sheet

Here’s a start-to-finish workflow for a small café pavilion:

1. Block out the mass. Use the slab and wall tools at generic thicknesses — just enough to set the spatial envelope. Assign a simple composite structure for later replacement.
2. Set views. In the Navigator, create a working 3D view, two plan views at 1:100 and 1:50, and a building section. Name them clearly — “CD-Section AA” is better than “Section 1” six weeks later.
3. Model the structure. Switch walls to their real composite types — timber frame with cladding layers. Add the roof as a single-plane slab with a taper. Place beams and columns from the library; use the object dialog’s built-in search to grab a steel profile from the web portal.
4. Place zones and check areas. Run the zone tool through each room. Open the interactive schedule, verify the gross and net areas against the local code minimums, and lock the numbers before issuing anything to the client.
5. Annotate in place. Dimension the grid lines, structural openings and overall plan. Use the associative dimensions tied to wall faces — if a wall moves, the dimension string updates without a manual edit.
6. Lay out the sheets. Drag views onto a new layout, add a title block from the master template, and align the drawing frames. Check the pen set for consistent line weights at print scale.
7. Publish. Use the publisher set to batch-print the layout to PDF and export a DWG for the structural consultant. The whole export takes under a minute on a modern Mac.

That’s a single session, one piece of software, from massing study to a drawing set ready for a planning submission.

A few practical corrections that keep work moving:

• Patches a lingering input snag in the Rotate command.
• Smooths out Teamwork Send and Receive on BIMcloud SaaS.
• Stops a crash that could happen when scrolling through Attributes.

• macOS 14 or later
• Runs on both Intel and Apple Silicon Macs