topic Re: Surface / Component Schedule Bug: Automatic Column Wrapping Ignores Folded Geometry and Returns in Project data & BIM

Surface / Component Schedule Bug: Automatic Column Wrapping Ignores Folded Geometry and Returns Flat

Narendra — Thu, 24 Sep 2026 16:14:05 GMT

Subject: Surface / Component Schedule Bug: Automatic Column Wrapping Ignores Folded Geometry and Returns Flat Bounding Area

Hi everyone,

I am trying to extract accurate paint/finish quantities for a real-world structural condition where a structural Column intersects wall and is wrapped automatically by a composite Wall skin. (Refer plan & 3D)

The Model Configuration:

wall is 1m long X 3m tall (Concrete block (intersection priority 750) +gyp plaster (IP-220) - finish (Titanium-white) +Cement sand plaster (IP-640)- finish (stucco yellow)

Column is 0.3x0.3x3m tall (wrapped)(Reinf conc core (IP-800)(no veneer)

Surface Schedule (Exposed Area parameter):

No matter which scheduling method I use, Archicad refuses to calculate the true unfolded surface area of the wrapped protrusion(Stucco-yellow) (which geometrically should be 4.20 m²). Instead, it falls back to a flat bounding calculation(1.98sqm(?))

The Problem with Scheduling:

Component Schedule (Projected Component Area (Net) parameter): When scheduling the literal material skin (Plaster - Cement Sand), Archicad completely ignores the 3D jogged geometry of the column wrap. It evaluates the 1.00m wall length deducted by column 0.3, strictly by its flat centerline projection (1.00m length × 0.7m height), yielding exactly 2.10 m² (flat face area) and omitting the depth of the column flanks entirely. (It should be 4.20 sqm)

What I Have Already Tried (None of this works or are viable):

Solid Element Operations (SEO): Subtracting the column from the wall does not change or reduce the coplanar surface total in the schedule.
Changing Column to Independent: Causes overlapping 3D volumes and incorrect/inflated totals across the overlapping elements.
Splitting/Breaking the Wall in 2D: Not a viable option as this is a real-world building model and cutting structural walls into small pieces breaks standard architectural drafting workflows and cleanup lines.

My Question:

Why does Archicad's calculation engine completely fail to unfold the perimeter length of an automatically wrapped composite skin? Is there a known workaround to force either a Surface or Component schedule to measure the true unfolded perimeter of a wrapped element face without resorting to manual calculation multipliers?

Appreciate any insight or workarounds from the BIM managers here!

Narendra (India)

Operating system used: Windows 10

Re: Surface / Component Schedule Bug: Automatic Column Wrapping Ignores Folded Geometry and Returns

Narendra — Fri, 25 Sep 2026 12:13:42 GMT

Hi everyone,

I was expecting an immediate reply because this is a hot issue-"Wrong quantities". I cannot pass the wrong information.

We all are beyond creation of beautiful 3d models and are deep into information exchange from those models.

Besides somehow there is no direct communication with Graphisoft's think tank (at least from India).

Hence an earnest request to suggest for any insight or workarounds from the BIM managers here!

Narendra (India)

Re: Surface / Component Schedule Bug: Automatic Column Wrapping Ignores Folded Geometry and Returns

Ricardo Heim — Fri, 25 Sep 2026 12:33:32 GMT

Hi @Narendra !

I always have problems with archicad's materials calculations and every time that happens I fall to doing what's wrong in a finish solid wall with the construction material and finish you want, in your case, just wrap a wall around the column and classify as wall finish.

As you noted, the wrap around function seems more visual than anything else, it even doesn't have plan view hotspots to accurately move things away from the finish. I think you should make this topic a wish in the wishlist.

I have the same troubles to quantify with the stairs tool, it's like the tools are made differently and doesn't talk with each other, its a major issue for us that manage the model and need to do automatic quantifications.