topic Re: Trace slows down drawing so much, almost unusable in Modeling

!Restored: Trace slows down drawing so much, almost unusable

kevin b — Wed, 13 Feb 2008 18:13:09 GMT

So are others having this problem? If I use a plan as a trace reference, everything slows down to a crawl, any move I make takes several seconds to recover and trying to select something, takes two or three attempts, each one taking several seconds, before the item actually gets selected.

Re: Trace slows down drawing so much, almost unusable

Anonymous — Thu, 14 Feb 2008 01:56:05 GMT

Are you referencing from the view map? If the reference has different layer settings, view options, etc. it can slow things down. A live building elevation view can really hang you up. (It's best to reference from the Navigator.)

Re: Trace slows down drawing so much, almost unusable

Stress Co_ — Thu, 14 Feb 2008 03:47:34 GMT

I added a keyboard toggle (shortcut) to switch trace on and off while I zoom and pan around the drawing. Saves the redraw time until I'm at the view/zoom I want.

Re: Trace slows down drawing so much, almost unusable

Karl Ottenstein — Thu, 14 Feb 2008 04:34:42 GMT

See this article:
http://www.archicadwiki.com/Virtual_Trace?highlight=%28trace%29

particularly the part at the bottom about 2D speed.

Personally, I've never had a speed issue, but my models are relatively small.

Cheers,
Karl

Re: Trace slows down drawing so much, almost unusable

Anonymous — Thu, 14 Feb 2008 10:30:04 GMT

The problem seemed to have been fixed in the last hotfix but one but returned with the latest - my experience anyway1

Re: Trace slows down drawing so much, almost unusable

Thomas Holm — Thu, 14 Feb 2008 15:10:32 GMT

Matthew wrote:
... (It's best to reference from the Navigator.)

Yes, "Project map" gives you references with the same layer combination as the current. No speed penalty.

Edited: OK, no BIG speed penalty...

Re: Trace slows down drawing so much, almost unusable

kevin b — Thu, 14 Feb 2008 23:30:33 GMT

I have the trace on/off toggle shortcut but its still a pain in the ass. For all the significant improvements trace has over ghost story, this slow down is stopping a lot of user here staying away from it.

Have been using the Navigator View Map mostly as opposed to the Project Map. I did see previously comments about the layers being different causing the slowdown but I made some test views in the navigator making the layers the same and still had same speed issues. And the fact is we really need the layers to be different, the thing I want to trace are on layers turned off in the view I am tracing in.

Edited: OK I chaneged the layers of the view I'm in to include those I want to trace and then used the Map reference and it is somewhat better but still this is a fantastic idea but is still very buggy to have such a speed issue trying to do exactly what it is made for.