Use Layers to Prevent Intersections - a defect Exception for Level 0

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-10 05:28 PM
Hello Graphisoft,
after I switched to ArchiCAD 27 - CZE I found that exception for Level 0 does not work in Sections. I solved the same problem in ArchiCAD 23 - an update helped. In ArchiCADs 24-26 there was not such a problem with it.
When is the new update of ArchiCAD 27 - CZE planned? Will the defect be fixed?
Thank you for your answer in advance and have a nice day.
Best regards
Radim
Operating system used: Windows 21H2
Solved! Go to Solution.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-10-09 09:37 AM
Can you modify the GDL Script?
You could modify it so those geometries do not touch, but there is a very small gap between them, like 0.1 mm. Then those lines will be generated because Archicad will sense they are not touching. However, the gap will be small enough not to cause any issues in visualization or dimensioning.
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-13 05:06 PM
So, if I understand correctly, you say that an element is on a Layer with a Layer Intersection Group Number of 0, yet, the element still intersects with other elements in Section?
Can you be a bit more specific? What element types are involved? Can you show screenshots of the situation, maybe another screenshot of the Layer Settings Dialog?
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14
12:03 AM
- last edited on
‎2024-02-14
12:15 AM
by
Laszlo Nagy
Hi Laszlo,
Thank you for your response.
The problem is with the GDL library objects . Two separate objects are OK. The problem is inside the library object. The objects are composed of cprism_ and prism_.
I am attaching PrtScr. I had a similar problem with version 23 (Level 0.jpg).
 
 
 

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14 12:24 AM
The Layer Intersection Group Number has no effect on what is happening inside a GDL Library Part.
What I see on these screenshots is that certain geometries within the Library Part are merged in Section in Ac27, while they are not merged in Ac26. This is usually due to modeling/scripting accuracy. Generally, in Sections, if two geometries touch and their Building Material/Cut Fill is the same, their Fills will be merged.
So, my guess is that the script of the Library Part was changed between Ac26 and Ac27. In Ac27 the script is so that the geometries touch and so the fills are merged, and you do not see the division line.
I think the GDL Script could be changed so that the geometries not touch, in which case it would generate a division line in Section. However, changing the script requires GDL knowledge.
My guess is that the developers changed it for a reason, maybe some users requested it. And now those users are happy, while you are not happy with the new way.
Is there any way you can use the Ac26 versions in Ac27?
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14 01:34 AM
The library elements are identical. The settings of elements, cuts, layers, ... are the same. It is the same project. Only real difference is in the opening of Ac 26 and Ac 27. The script of the library elements was not changed.
The layer intersection group number=0 in the Ac26 has effect on what is shown a GDL library element - in the Ac27 has no effect on what is shown a GDL library element.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14 04:48 AM
What object is this?
AC22-28 AUS 3110 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14 08:28 AM
Are you saying that you are using, let us say, "Cabinet 26" in both Ac26 and Ac27 and they are giving different results?
Or are you using, let us say, "Cabinet 26" in Ac26 and "Cabinet 27" in Ac27?
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14 10:43 AM
I'm using custom library programming elements in gdl code. This problem is also with the original elements (Cabinets).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-02-14 10:48 AM
I'm using "Cabinet 26" in both Ac26 and Ac27 and they are giving different results.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2024-04-21 09:58 AM
Current update installed.
The problem remains.
I feel it's a shame that I still have to work with version 26!
What's the point of paying for updates?
Best regards
Radim