Polygons, Again

[James Murray]

Another day, another reminder that there seems to be a deep structural limitation in AC regarding polygon handling. The advice in this advertisement has been standard for as long as I have used the program, despite computers becoming 100s of times more powerful. This puts workaround responsibility on the user, which harms our work efficiency. It shows up as permanent limitations in the tools, such as low-resolution complex profiles and shells. “Polygons are bad” seems like a strange position for a modern 3D modeling software.

Is there any roadmap for improving this situation, or is it as hopeless as it seems?

https://x.com/GRAPHISOFT/status/1915063957246583207

[SeaGeoff]

The X post is downright embarrassing. I remember a time not long ago when GS promoted Archicad's supposed superiority in handling large models as an advantage over the competition.

[James Murray]

OK, we'll go with hopeless for now. Thanks!

[Bernhard Binder]

I don't think that dumb objects with a high amount of polygons are a problem, but all the countless calculations when it comes to SEO and BM intersections. So high polygons are an easy task für GPU but the intersection calculation on the CPU is the real pain.

I am just assuming, unfortunately I am not sure about this.

So reducing unnecessary calculations by reducing details in S/E is always a good advice.