Trace reference so slow it is not usable.

[Anonymous]

This trace bug is infuriating! Archicad grinds to a halt when it's on. No amount of simplification changes the clunkiness. Productivity in our office is suffering from this unstable mess of an update.

[Anonymous]

I have finally after a lot of years and much hardware resolved the typical slugishness of things like trace. I upgraded my late 2011 17" MacBookPro with a decent SSD and now 8GB of memory. I don't do large projects, but have a 13 unit townhouse apartment project working with Eric's Master Template and the system is quite quick.

Try it you might like it!

[Anonymous]

Any word on a fix for this issue?

[Ed_Brown]

When the trace reference is from the view map and not the project map then then essentially two layer combinations are used to display the elements on your screen. In this case differing intersection groups in the two layer combinations can incur heavy performance penalties.

A workaround to improve responsiveness is to duplicate the two layer combinations used and in these two temporary layer combination sets make sure all of the intersection groups are set to 1. Understandably while you work in this “optimized” trace environment intersections will not appear as you desire, but your ArchiCAD will be considerably more responsive.

Hope this helps,