topic Re: Trace reference so slow it is not usable. in Modeling

Trace reference so slow it is not usable.

Anonymous — Wed, 05 Sep 2012 00:00:05 GMT

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.

Re: Trace reference so slow it is not usable.

Anonymous — Wed, 12 Sep 2012 14:37:18 GMT

I had the same problem with trace when I opened up projects from AC15 with AC16. However, if I copied the project and pasted it in a new AC16 the trace reference worked fine? So far that is true with all my AC15 files. I have to copy/paste the project into AC16 for it to work normally with trace reference. Otherwise I just use AC15 for older AC15 projects. I don't know why there is a hangup within AC16......

Re: Trace reference so slow it is not usable.

Anonymous — Wed, 12 Sep 2012 17:06:42 GMT

Trace reference has ALWAYS been slow for me. Sometimes when panning around with trace on, it zooms me way out unexpectedly. Or I get a flashing hourglass symbol. Turning trace off fixes it all.

Trace is a very helpful tool but I do wish it would work more fluently.

Re: Trace reference so slow it is not usable.

Karl Ottenstein — Wed, 12 Sep 2012 21:05:37 GMT

Just a reminder: when you enable a reference, if it is to a VIEW (View Map), the process will be slower because potentially different layer combo, model view options, etc etc are rendered for both the active and the trace. For complex models or for slower computers, this can be noticeable.

If the reference is to a viewpoint (Project Map), then the exact same layers, model view options, dimension settings, etc etc are used for BOTH the trace AND the reference and things are much faster.

(For old-timers who remember Ghost Stories as the only 'trace' option ... with the old Casper-the-Ghost button ... this latter type of tracing to viewpoints corresponds exactly to the old ghost story.)

See if tracing a View vs Viewpoint might explain the slow behavior you are seeing?

See further info here:

http://www.archicadwiki.com/2dSpeed?highlight=%28CategoryTrace%29#Trace_and_Reference

Re: Trace reference so slow it is not usable.

Anonymous — Thu, 13 Sep 2012 00:28:44 GMT

I ran a peformance monitor of my ram in 15 using trace and compared it with 16. Massive jump up in ram usage.

We never had an issue before with 15 using a view map trace. Which we need to for ceiling and slab layouts.

This......

"I had the same problem with trace when I opened up projects from AC15 with AC16. However, if I copied the project and pasted it in a new AC16 the trace reference worked fine? So far that is true with all my AC15 files. I have to copy/paste the project into AC16 for it to work normally with trace reference. Otherwise I just use AC15 for older AC15 projects. I don't know why there is a hangup within AC16......"

Re: Trace reference so slow it is not usable.

Anonymous — Thu, 13 Sep 2012 20:45:19 GMT

As I am on my phone I have not scrolled through earlier posts on this topic - so forgive any repetition

We experience slowdown and even apparent hangs- so bad we were wondering if we could continue with 16.

Tech support advised and we can confirm it is a bug with views defined in a 15 file that has been migrated to 16! The workaround for us is to delete the view and redefine. Then all goes well. I gather it may be addressed in next hot fix.

HoPe that helps

Re: Trace reference so slow it is not usable.

Anonymous — Mon, 12 Nov 2012 02:04:45 GMT

Has there been in progress on resolving this issue?
We are having major problem with trace reference since upgrading to AC16. Same symptoms as others are experiencing and it doesn't seem to matter if the trace is taken from the project or view map.

Re: Trace reference so slow it is not usable.

Katalin Takacs — Thu, 15 Nov 2012 15:29:29 GMT

On ArchiCAD Wiki we published a description about this issue and tips to avoid the problem: http://archicadwiki.com/Troubleshooting/SlowTraceReference

Sorry for the inconvenience.

Re: Trace reference so slow it is not usable.

Anonymous — Mon, 26 Nov 2012 23:28:24 GMT

Thanks for the reply Katalin. Unfortunately none of these have made significant change.
I have been using AC15 for the current job I'm working on which is quite ridiculous and I think unacceptable.
Is this issue something that is being looked at or able to be rectified through a Hotfix?

Re: Trace reference so slow it is not usable.

Katalin Takacs — Wed, 28 Nov 2012 14:25:12 GMT

Currently we are only aware of the workarounds suggested in the wiki article.
Probably the next Hotfix of ArchiCAD 16 will have the fix of this issue, too.

Re: Trace reference so slow it is not usable.

Anonymous — Sat, 01 Dec 2012 03:42:31 GMT

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!

Re: Trace reference so slow it is not usable.

Anonymous — Wed, 27 Feb 2013 05:23:50 GMT

Any word on a fix for this issue?

Re: Trace reference so slow it is not usable.

Ed_Brown — Tue, 30 Apr 2013 07:15:49 GMT

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,