Collaboration with other software
About model and data exchange with 3rd party solutions: Revit, Solibri, dRofus, Bluebeam, structural analysis solutions, and IFC, BCF and DXF/DWG-based exchange, etc.
SOLVED!

Using paranthesis in schedules extremely slow in ArchiCAD 22

PVBergkrantz
Expert
Hello. I recently migrated a project to AC22 and am having huge issues with schedules being slow. At first I thought it was just the file and something wrong or overly complex but after some trouble shooting and bug hunting I think I've narrowed down the problem, and it is recreatable in every file I try it with.

When doing a schedule, and setting the rules like below the time to load and display the schedule jumps from a few seconds to 7-8 minutes. This was not the case in AC21.

Type = Zones
( Zone category != Category1 &
Zone category != Category2)

By putting the same rules without the paranthesis it loads in a few seconds (though working without paranthesis is not always an option, especially when using or instead of and).

It also seems to get even worse if there are hotlinks present.
| AC 25 Int | Win10 | i7-7800X | 32 GB | GeForce RTX 2060 6GB |

11 REPLIES 11
PVBergkrantz
Expert
I've gotten a reply from Graphisoft concerning this and they confirm it is a bug and something they are working on to fix in the next update. They gave this recommendation as a workaround:
"There is something we can recommend the client to do for the time being until the issue is resolved.

1. Add a new Property, with Value definition: Expression
2. Add Parameters & Properties: Zone > Zone Category
3. Availability: All

If the client uses this as a criterion, the calculation speed will be significantly faster, since ARCHICAD will then calculate only with Zones rather than Zone Relations.

Unfortunately, we lose the Pop-up value choosing option for the criteria, so it needs to be considered whether it is worth the trouble to implement this workaround to speed up the schedule processing."
And I also made my own workaround by placing the criteria that would be in parenthesis FIRST instead of last, and then not having to use parenthesis at all.
Zone cat IS xxx OR
Zone cat IS XXX OR
...
Element type IS zone AND
Layer IS xxx AND
Hotlink source IS xxx
Though this only works in this specific case with one parenthesis. Otherwise their method might be better.
| AC 25 Int | Win10 | i7-7800X | 32 GB | GeForce RTX 2060 6GB |

Solution
PVBergkrantz
Expert
This seems to have been solved in AC23.
| AC 25 Int | Win10 | i7-7800X | 32 GB | GeForce RTX 2060 6GB |