cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
2024 Technology Preview Program

2024 Technology Preview Program:
Master powerful new features and shape the latest BIM-enabled innovations

Modeling
About Archicad's design tools, element connections, modeling concepts, etc.

Clean Wall & Beam Intersections stopped working

On a pln on 27 AUS 5003, MacOS 13.6.6. on M1 Max, at some point Clean Wall & Beam Intersections stopped working. On a backup file from a few hours earlier things work fine, when opening both files at the same time on different sessions on the same computer.

 

Restart changed nothing, neither did Open & Repair.

 

Relative to the slightly older file, the actions I remember were bringing in some PDF into worksheets, modifying the elevation to sea level, elevating a slab, running Intersections in Layer Combinations (not sure if I did this before or after, as a reflex action when coming across some intersection issue). Owerwriting (restoring) layer combinations with those of the previous file through Attribute Manager changed nothing.

 

First time I remember seeing this.

 

Video at https://www.dropbox.com/scl/fi/blzr8m6v472ar6fgi27wh/no-cleaning-high.mp4?rlkey=ptdlfdv1ja312sx8z6rd... 

 

Operating system used: Mac Apple Silicon 13.6.6

14 REPLIES 14
Barry Kelly
Moderator

Assuming all of those walls are in the same layer, what is the Intersection Group number for that layer?

 

Barry.

One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

It happens in all layer combinations. When visible, 1, in all combinations in both files (I always stick to the results of Intersections in Layer Combinations, don't mess with that). The problem appeared simultaneously in all walls on any layer, and beams on their layer, in all cases 1 when visible. My first thought was that I had inadvertently hit a new shortcut in 27, but “On Screen… > Clean…” has no shortcut. 

I just copied a couple of walls from the new problem file to the old file, and they clean up all right there; from the good old file to the new problem file, and they don't. 

This is a very simple model on an initial phase. Just straightforward walls, there are no duplicates nor overlapping walls, and in any case they are the same walls in both files.

This is strange.

It is possible for the layer combinations to have the correct Intersection Group numbers, but still have it set to zero in the actual layer.

 

BarryKelly_0-1714357763465.png

 

But this will fix as soon as you choose a layer combination.

Other than 'Clean wall & beam intersection', or the layer intersection group number, I can't think what else would stop the clean up.

 

Barry.

One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

Layers are 1 when visible, in all layer combinations. (That is what Intersections in Layer Combination does; visible 1, invisible 2.)

Dmitriy L
Participant

Hi, I've run into the exact same issue. Toggling "Clean Wall & Beam Intersections" doesn't appear to do anything. My last actions were creating complex profiles. I don't have a backup to return to unfortunately. It's a relatively new file so I might be able to copy across to a new file. 

 

Would appreciate any ideas or fixes.

 

Thank you,

Dmitriy

 

Edit:

A quick update - I've restarted my machine, started a new file, and turned on all layers in my broken file to start copying things across to a new file. I'd copied across one storey when I noticed the original file had fixed itself. I don't know what I triggered, or where.

 

Perhaps it was something to do with intersection group numbers - but the issue was affecting walls on the same layer. Maybe having a second copy of AC running had something to do with it. I did toggle "Clean Wall & Beam Intersections" in the new file to check it was working ok there (it was). Maybe that helped? I'm afraid I can only speculate.

 

AC27 5003 AUS FULL

Hardware:

HP ZBook Studio G7

Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz 2.40 GHz

On my video some confusion is evident also on the part of Archicad between “Clean Wall & Beam Intersections…” and “Wall & Beam Reference Lines”. I would guess related symptom, because I don’t think I had seen this in 20+ years either. 

[Actually, that may be how the problem started: I opened the file to find it with reference lines off (I absolutely never have them off), turned them on, and misery ensued.]


@Ignacio Azpiazu wrote:

Layers are 1 when visible, in all layer combinations. (That is what Intersections in Layer Combination does; visible 1, invisible 2.)


The layer combination may be showing 1, but the actual layer may be set to zero (custom layer combination).

If zero, then there will be no trimming in that layer, regardless of what the layer combination shows.

But as soon as you activate a new layer combination, it should reset.

I don't think this is your issue, but just wanted to point out a layer can be set to 0 when it is not set that way in the combination.

 

1 & 2 does not mean visible or invisible.

All layers set to 1 will trim with each other.

All layers set to 2 will trim with each other.

Even if the layers are turned off, they will still trim with other layers with the same intersection group number.

 

Elements in layers set as 1 will not trim with elements in layers set as 2.

 

Barry.

 

One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

In the back of my head I can recall that this problem has occurred before, but not the solution.

Maybe the complete machine restart is it?

No harm in trying.

 

Barry.

One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

Complete restart is the first thing I did.

Setup info provided by author