Inconsistent display of load-bearing connections between ViewMap and Layout

[DNU]

When creating structural plans in Archicad, we encounter the following issue:

Load-bearing elements that connect to non-load-bearing elements are displayed differently in the ViewMap compared to the same view placed on a Layout. This discrepancy only becomes visible after placing the view on a Layout, making it difficult to detect and control.
Example;
View with structural display; Core only

We use the Structural Display: Core of load-bearing elements only setting.

 
When two elements connect (one load-bearing, one non-load-bearing), the graphic result looks fine in the ViewMap preview, but once placed on the Layout, the appearance changes—often creating visual inconsistencies or unexpected connections.

Is there a known cause for this or a recommended workflow to avoid these inconsistencies?

Any insights or suggestions would be appreciated!

Operating system used: Windows 4001

[Laszlo Nagy]

2 questions that come to mind:

1. When you select the Drawing on the Layout and open its Source View, does it open the correct View?

2. Is the Project by any chance located far from the Project Origin? This can sometimes cause weird issues in Drawing on Layouts.

[DNU]

Hi Laszlo,

Thanks for the quick reply! To answer your questions:

1. Yes, when we select the drawing on the Layout and open its Source View, it opens the correct View from the ViewMap. In that source view, the elements are displayed correctly.

2. No, the elements are located just a few meters from the Project Origin, so distance should not be an issue.

Additionally, I'd like to add some more context:
This issue has been consistently occurring in all our office projects, across all user workstations. Even when we start from the default Archicad template with all standard settings, the same problem appears.

To clarify the issue further, I've recorded a screen capture showing exactly what happens.

[danielk]

Hi,

Based on your video this is very clearly a bug that you should report to your local support team, so that they can register (and fix) it. I also tried it on my end, and it was very easy to reproduce the issue. It kind of seems like it considers the hidden walls to be the same material or something, and it joins them accordingly on the layout (as if you just turned off the layer of those walls).

I think (if that is an option for you), you could temporarily put the non-load-bearing walls on a separate layer, and change their layer intersection group number to 0 (and hidden) for the "core of load-bearing-only" views. But definitely report it to support, or this issue will never get fixed.

Good Luck!

[Barry Kelly]

Yes I could replicate the issue as well.

Be sure to report it to your local support as Daniel suggested.

It looks to me as if the layout is mitering the walls with the old method from version 16 and before.

It does not seem to be using the blocky material strength connections.

Barry.

[DNU]

Thanks Daniel and Barry

We've informed our local Archicad distributor/support team about the issue. They have confirmed the behavior and have escalated it to Graphisoft.

Hopefully a bugfix will follow soon.

We’ve already tried the workaround of setting the Layer Intersection Group Number to 0 for the involved elements. While it helps in some cases, it’s far from ideal.

The downside of this method is that we then need to extend the Reference Line beyond the connection point, but that doesn't always work, especially when non-core skins of composite wall start extending too, which leads to incorrect junctions in the architectural plans where all skins are shown.

So unfortunately, the workaround introduces its own complications depending on the plan type.