cancel
Showing results for 
Search instead for 
Did you mean: 
EN
cancel
Showing results for 
Search instead for 
Did you mean: 

Building Component Thickness & Unit Handling Improvements

BDarch
Booster

I recently noticed an inconsistency in Archicad schedules and calculations regarding Building Component Thickness values.

Currently, even when multiple building components have exactly the same thickness value, Archicad does not allow them to be merged/grouped properly in schedules or calculations. This feels unintuitive, since identical values should logically be combinable the same way as other numeric properties.

It would be very helpful if:

  • Building Component Thickness values with identical numeric values could be merged/grouped automatically.
  • Thickness parameters could behave more consistently with other measurable properties in schedules.

Additionally, there is a small but frustrating unit-handling issue:
when perimeter values are displayed in meters, thickness values are still forced into the same unit context. As a result, users sometimes need to display perimeter values in millimeters just to keep thickness values readable and technically correct.

It would greatly improve usability if Archicad allowed:

  • independent unit formatting for different parameter types within schedules/calculations;
  • for example:
    • perimeter → meters (m)
    • thickness → millimeters (mm)

This would make schedules significantly cleaner and more natural to read, especially in professional documentation workflows.

 

Thank you!

3 Comments
Laszlo Nagy
Community Admin
Community Admin

Can you post screenshots that illustrate this?

BDarch
Booster

It could look like this. Alternatively, you could make it work like the Classifications menu, where users can select which dimensions they want to display, as well as the tolerance settings.

For example, in this case I don't want to show the Total Length in millimetres.


BDarch_0-1785246433787.png

 

runxel
Moderator

Allowing different units, or overriding them an a per-column basis has been discussed before. I think there are still some roadblocks, but @James B is aware of this need and I think it's strongly considered.

Having a total row being also different to the rest of the column is a new one, tho. That's kind of "per-row / per-cell" territory.

Status
Open

with 2/200 Votes 100%

Wish details