I am also having this problem not only whiile dimensioning but in other commands too. It makes osnap settings useless and very annoying. After rare cases where I use the 'nearest' snap, the nearest will take over for the node awhile, then node eventually comes back to haunt me. Has there been any 'fix' for this? (Using Mechanical 2010 in Windows 7)
Definitely appreciate any help on this! Thanks much.
Shelby
Well in ACM 2012 on Windows 7 I haven't had any such trouble... it could be that it's version-bound?
Hah! It is ever so funny when a thread comes back to haunt you...
I now have a user with exactly this issue... In AutoCAD Mechanical 2012 SP1 on Windows XP - so it is definitely not version bound.
What we have tried to do so far to fix/pinpoint it:
- Set up a Power Snap Configuration Setting (3), with just endpoint on.
- Select this Power Snap Configuration
- OSMODE check (comes back with <1>, which is what it should be)
- Check by right-click objectsnap icon (bottom right of the screen) > settings. Only Endpoint is checked.
- Powersnap filters have not been changed from default.
- 3D snap is off
Does anyone know any other sysvars, settings, etc that could be connected?
Note: the snap icon that appears during powerdimensioning looks like the node snap (circle with an x through it), but perhaps it is something else?
Using the configuration settings worked! Thanks for the reply, been using configs for a couple weeks and haven't had the "node" return!
Sorry took so long to reply, was working in Inventor for awhile and needed to switch back to Autocad for some test driving. Thanks again for helping to dump this time wasting annoyance!!
Cadallday