Trace reference is really slow!!!

[Anonymous]

Every time I turn on trace, I have problems.

Whenever I do anything, even if I click on a line or element, it starts to think for at least 30 seconds.

Does this happen to everyone? Trace is a awesome and very powerful option but not like this, it is completely USELESS!

Please anyone offer me some advice.

(I am using a PowerPC G5 with 1 gig/ram, dual 1.8 Ghz)

[Karl Ottenstein]

Steven wrote:
DENNIS!!!!

Thank you, that works!

I was using the view sets as trace and when I went to the project map it now runs flawlessly.

Ummm.... posted earlier in this thread is the document explaining this:

See also the Virtual Trace section of this article:

http://www.archicadwiki.com/2D_speed


Karl

[Anonymous]

Sorry Karl I must have skipped over that part....

[Anonymous]

Karl wrote:
See also the Virtual Trace section of this article:

http://www.archicadwiki.com/2D_speed
Karl

I did not know that this was the case. I had to read it for myself. Here it is:

The use of View map items as Trace Reference
If you wish to use e.g. an elevation as Trace Reference under your floor plan, you can do it in two ways:

Select the elevation in the navigator’s Project Map, and select “show as Trace Reference”

Select the elevation in the navigator’s View Map, and select “show as Trace Reference”

In the first case, the Trace Reference will use the same layer settings and model view options as the active view. In the second case, the Trace Reference and the floor plan will use different layer settings and model view options. This latter scenario will result in a slower 2D rebuild, because the refreshing of the Trace Reference involves changing layer and model view states. So, if possible, use Project Map items instead of View Map items as Trace Reference

I know there are many other reasons to upgrade to AC11, but I thought the Plan + Elevation (as View map trace) was a nice feature. I did not know of the Speed hit.

[Dennis Lee]

Thanks Steven - no, really, I'm really just stumbling along here w/ everyone else - I hope "they" make me a beta tester first though...

[Anonymous]

Thanks to you all.

I finally get it. I didn't understand the difference in speed between view and project map reference.

Selecting from project map is just like using good ole' ghost story...
nice and speedy.

[Anonymous]

I've followed all of the suggestions on this issue and it is still slow... (think my mac is dying a slow death)

Another tip not mentioned here(unless I'm blind?) - not sure how much it will affect performance though - try adjusting the information shown on the Trace reference - go to the Trace reference pet palette, click the black arrow and check/uncheck the elements required.

[Anonymous]

using the trace tool just slows everything down, sounds good but not yet working. i see the sugestions for using project map references and not view sets, but this should not be the case, if the option is there, it should work. whenever you move around the screen with a trace reference on i can see the quick options pallette scale settings flipping between 100 and 50, it seems to be reading or checking the scale.
Also, with trace on, when you zoom in to place a mesh, both cursor and stretch line disappear completely, so you have to place node points blind.

[Da3dalus]

I've noticed all of these symptoms, as well as a problem with being able to select items in the active view. The visual problems are workable, but the functional ones are not! I have a pretty fast Xeon workstation, so it should be as good as it gets!