2023-06-02 10:08 PM
Dear Communitiy, I have been working with ArchiCAD since version 6.0, and since we can move objects and overlapping surfaces in sections, I've only now encountered a problem in v26.
In sections, the overlapping surfaces of walls, girders or slabs do not respond to either bring to front /bring to back commands if they overlap with mesh structures. Eg. if you have a mesh as terrain and you have walls or slab for foundations, the mesh always comes to the top in the display order in sections, hiding the walls and the slabs, no matter how weak its building material is set to, or if I use the bring to front/back commands. This problem was not present in v.25, only in v26. Is there a new tool that I am not aware of or is this some sort of a bug?
The only way to show such foundations in the terrain is with boolean functions, but that unnecessarily comlpicates the model.
Please adise, thanks,
Kornél Sziklai, architect, Hungary/Germany
2023-06-04 10:03 PM
Yep, that's a bug, and a quiet annoying one.
2023-06-22 05:57 PM
Dear @KornelSziklai,
Thank you for raising this topic!
Oleksandra Vakariuk
Technical Support Engineer2024-01-11 11:10 PM
Oleksandra Vakariuk
From Archicad 26, the display order does not work on the overlapping 3D elements in sections and needs to be adjusted with a proper junction. For example, using a Solid Element Operation.
I am running into this issue and it seems to be randomly happening, if i move the position of the section in plan then sometimes it works correctly other times not. has anyone figured out how to fix this issue, SEO is not an option
2024-01-12 08:51 AM
Hi @Nuge,
I would use a complex profile wall in this case.
Kind regards,
Oleksandra Vakariuk
Technical Support EngineerThursday
I ran into this old topic because some colleagues are experiencing unexpected and difficult-to-control section display issues, especially between foundations and meshes. Maybe before Graphisoft assigns all their developers to chase the next AI fad they can tackle the hard but necessary work of making model elements actually interact like their real-world counterparts. Every project has terrain, and foundation elements that need to be subtracted from it. And yet Priority Based Connections do not operate here. Why? When can we expect Graphisoft to address this?
Thursday
This graph (found here), which has not been updated since the introduction of building materials in Archicad 17, should be an embarrassment to Graphisoft. I know I am embarrassed when training new users. Mesh is not even listed. And some things don't work as advertised, like stacked walls. The sheer number of workarounds required to get acceptable connections across the average model is staggering. Graphisoft created a brilliant system based on sound logic, but never bothered to extend it to all elements, or add the needed manual overrides. This despite the fact our computers are many times more powerful now and could handle the required computations.
Fixing this should be development priority #1.
Technically you could change the display order of elements on sections to correct these in 25, but this had to be done per viewpoint and didn't work in Teamwork (since this action is not shared in a Teamwork Project). The display order in Archicad 25 and before also caused a lot of instabilities in different tests which is why the logic behind it has been changed.
From Archicad 26, the display order does not work on the overlapping 3D elements in sections and needs to be adjusted with a proper junction. For example, using a Solid Element Operation.