Project data & BIM
About BIM-based management of attributes, schedules, templates, favorites, hotlinks, projects in general, quality assurance, etc.

Conflict between Demo & New Layers.

Anonymous
Not applicable
I am relatively new to archicad and fumbling my way through a bit.

I have set up existing, demo, and new layers for text, dimensions and walls.

I am running into a problem.

If I have a wall on the new layer that overlaps a wall on the demo layer ,which is turned off, I end up with a hole in my new wall. It is trying to reconcile I suppose or automatically clean up the intersection.

I need to stop this from happening. Any ideas?
13 REPLIES 13
Eduardo Rolon
Moderator
In the Layer Palette change the Intersection Number for that layer.

Same numbers they intersect, different numbers they don't.

Read Page 22
ArchiCAD 11 Reference Guide
Eduardo Rolón AIA NCARB
AC27 US/INT -> AC08

Macbook Pro M1 Max 64GB ram, OS X 10.XX latest
another Moderator

David Larrew
Booster
Be sure to update any/all your Layer Combinations since the Intersection Number is stored in each LC.
David Larrew, AIA, GDLA, GSRC

Architectural Technology Specialist

a r c h i S O L U T I O N S



WIN7-10/ OSX 10.15.7

AC 5.1-25 USA
David wrote:
Be sure to update any/all your Layer Combinations since the Intersection Number is stored in each LC.
There is an add-on, 'Intersections in Combos' or something like that. You run it and it gives some number (say 1) to the visible layers and some other number (say 0) to the hidden layers, going over every single layer combination. Especially if you are developing your layers setup, running that every now and then is much better than manual maintenance. Very rarely you may still need to go manual for some subtle tweak, but the bulk of the work is done by the computer.
Thomas Holm
Booster
Ignacio wrote:
David wrote:
Be sure to update any/all your Layer Combinations since the Intersection Number is stored in each LC.
There is an add-on, 'Intersections in Combos' or something like that. You run it and it gives some number (say 1) to the visible layers and some other number (say 0) to the hidden layers, going over every single layer combination.
The Intersections in Combos add-on will return Archicad to older version's behavior that hidden layers did not interfere with the visible. This is straightforward but doesn't allow for the more sophisticated options for layer combinations that individually set intersection numbers allows. Since it changes your settings overall, be careful!
AC4.1-AC26SWE; MacOS13.5.1; MP5,1+MBP16,1
Thomas wrote:
The Intersections in Combos add-on will return Archicad to older version's behavior that hidden layers did not interfere with the visible. This is straightforward but doesn't allow for the more sophisticated options for layer combinations that individually set intersection numbers allows. Since it changes your settings overall, be careful!
There is a time for aikido and a time for a shower of katyusha area saturation rockets.
Thomas Holm
Booster
Ignacio wrote:
There is a time for aikido and a time for a shower of katyusha area saturation rockets.
Absolutely! but because this add-on might screw it all up if you're using a carefully set-up template, I thought a warning is required.
AC4.1-AC26SWE; MacOS13.5.1; MP5,1+MBP16,1
Djordje
Ace
Ignacio wrote:
There is a time for aikido and a time for a shower of katyusha area saturation rockets.
Aikido exists in the smoking silence of the empty katyushas too.
Djordje



ArchiCAD since 4.55 ... 1995
HP Omen
Thomas wrote:
Absolutely! but because this add-on might screw it all up if you're using a carefully set-up template, I thought a warning is required.
Oh that's right. Based on the nature of the problem I assumed he was stuck while setting everything up from scratch and thought brute force would provide a good starting point, but it can happen with a 'Demo'-'Exst' addition to a solid refined 'New' template.
Thomas Holm
Booster
Ignacio, you may well be absolutely right, and your solution the best in this case. I'm sorry if I offended you, that was not my intention. I just thought these posts will remain and will be read by others for some time to come. Thus, I wanted to complete the picture.
Best regards,
Thomas
AC4.1-AC26SWE; MacOS13.5.1; MP5,1+MBP16,1