topic Re: Archicad 15 trace reference problem in Modeling

Archicad 15 trace reference problem

Anonymous — Tue, 23 May 2023 12:44:19 GMT

When trace reference is activated, as I move the mouse over the edge of some objects (e.g.. walls), but also 2D objects (hatches, line or poly line), windows sand-glass mark starts to flash intermittently unless the mouse moves out.
In this case, I can not even find the centre of the object (V character) and the zooming by mouse wheel or selecting objects is hard thing to do.
I have noticed that this is happening when traced drawing has different layer combination than actual drawing.
For example when I work on first floor and have traced foundations or roof with different layer combination.
Tested on two different computers (windows xp and 7, ArchiCAD15), the same. AC14 works fine.
Any experience of this behavior or any suggestions what is wrong.

Re: Archicad 15 trace reference problem

Anonymous — Thu, 26 Jan 2012 14:51:40 GMT

Is there anyone facing this problem ?

Re: Archicad 15 trace reference problem

Stress Co_ — Sun, 29 Jan 2012 19:01:21 GMT

I haven't noticed it in 15.... but YES in earlier versions.

Re: Archicad 15 trace reference problem

Arcadia — Mon, 06 Feb 2012 09:25:31 GMT

Yes this has been an issue for me right back to V12. It is a headache. In fact I find trace reference to be quite clunky for such an important facet of Archicad. I have not found a solution to it although it doesn't seem as bad in V15. I believe it may be something to do with Nvidia video card drivers which is surprising given I use Quadro cards. I have a new system on order that is very high specced and I have decided to go to ATI Pro cards this time to see if this helps.

Re: Archicad 15 trace reference problem

Anonymous — Mon, 06 Feb 2012 10:33:47 GMT

Sounds like an issue we sometime get when the special snap points is set to thirds. too many polyline snap calculations for the computer to handle.

It is better with AC15.

Re: Archicad 15 trace reference problem

Anonymous — Wed, 08 Feb 2012 21:33:30 GMT

It indeed has to do with special snap points. The problem occurs when option "Between Intersection Points" is set. Setting "Along Entire Element" will solve it.
Thanks Paul for reference to these options.