Despite repeated attempts to adapt and train individuals to this, it continues to be a huge productivity killer for us and probably the biggest source of frustration for those who are modeling. I am interested in seeing a Bentley response on this as well.
Thomas' specific issue is with using tentative snap (not AccuSnap) in a view with an ACS that is edge-on (ex. top in a front view)...is this your issue as well? A solution to this specific problem is to define a different ACS for the view, either front or view-independent.
Hi, the NNTP feed is not working so I shopped around in the web interface without understandong much but saw I could EDIT this post. Is that really inteded? /Thomas Voghera
Actually snaps and accudraw in general. Most work in multiple views, namely isometric, top and front or side. When starting operations in one view then using another to complete, the acs is inaccurate as to it's relationship. This becomes particularly frustrating when using Bentley Architecture or any of the other verticals as it becomes impossible to have to define custom height ACS settings and then have to do so per view. Most have just gotten into the habit of continually cycling the ACS rotaton with "V" or specifically calling out the rotation that they need: "T", "S", "F"...and so on.
I think it would be best if you could post a simple example; you've used the terms AccuDraw and ACS in such a way that it's not at all clear to me whether you actually have an issue with the per-view ACS or are referring to the AccuDraw compass as the ACS (because they aren't the same thing).