OSNAP sensitivity and AREA command

[Anonymous]

Is there a reason why OSNAP aperature would change with different commands?  I have osnap aperature set to 40, and it works fine most of the time. 

But when I use the AREA command, I have difficulty selecting points.  I have to zoom in pretty tight to select points, and even then it is difficult.  It feels like the aperature drops to maybe 1 or 2.  I mean, if I'm trying to grab an end point, I have to be perfectly on the end.  And sometimes it looks like I'm on the end, but it doesn't grab the point.

It's confusing, because I don't have any problems with any other command.  I assumed that osnap aperature was a universal setting, but is there another setting I need to adjust?

Also, why does autosave always execute at the same time as the AREA command?  When I hit enter after making my selection, fairly often I will see a dialogue box showing the autosave info in the place of the display of the area calculation.  I know I can expand the command bar to find the area result, which is always immediately before the autosave line.  I wouldn't mention it if it happened once or twice, but sometimes it seems like it happens 50% of the time.  I have autosave set to every 15 min.

(Ooops,  already posted in regular "AutoCad" forum, not knowing there was specific LT forums and even the LT for Mac forums...so many forums, so little time...)

[maxim_k]

Welcome to Autodesk Forums!

Hi Darren,

>>>> I assumed that osnap aperature was a universal setting, but is there another setting I need to adjust?

Yes, it is universal and it doesn't change during AREA command. Do you have ENDpoint snap enabled as running object snap? Is it only one OSNAP that is active?

>>>>Also, why does autosave always execute at the same time as the AREA command? 

No, it is not correct. I think it is rather coincidence.

Have you tried to use MEASUREGEOM command with Area option? When this command gives the result of area calculation you are still inside command and autosave will not interrupt it, allowing you to see the results:

[ChrisPreece]

Hi @Anonymous,

Welcome to the Autodesk Community, and thank you for posting your question here in the AutoCAD for Mac forum.

I'm just checking in to see if you need more help with this. Did the suggestion that @maxim_k provided work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

[Anonymous]

With further testing, I'm noticing that indeed, it is not specific to the Area command.  But it happens in commands like area, when I'm zoomed out. 

I do have the standard osnaps enabled--end, middle, center, int.  I manually type in others as needed. 

I think I solved it.  It appears that the grid snap was turned on (grid is off), by default it seems.  (It would have to be default, because I've never intentionally used it.  But I'm on a brand new install of AutoCad...)  Grid spacing was set to 1/2", small enough that I didn't notice it.  Apparently the tight grid was in conflict with the aperture setting?

I turned the grid snap off, and now my osnaps work perfectly.

I turned the grid snap back on, and everything still works fine.  I can't reproduce the problem, but atleast the problem is gone!

It really seems like the grid snap was overriding the osnap aperture.  After I selected the first point, I had to get within that 1/2" grid to select subsequent points, or atleast that's my theory.  I had to be right on top of the point, and sometimes I still couldn't grab it!

Another weird observation--I was having trouble with the "none" osnap.  I always used it in the past, but I was getting "invalid point" dialogue when I tried to use it.  But now, after turning that infernal grid snap off, it's working perfectly.  And again, I can't reproduce the problem by turning the grid snap back on.

[maxim_k]

Glad to hear that the problem has been solved.
Do you restart AutoCAD at least once a day? Or you don't turn off your Mac and AutoCAD is running on the background all the time week after week?

[Anonymous]

I close the application periodically, but I don't have a specific
routine.  I just recently renewed my subscription as I am getting
serious about a new project, so it is a new install.

This problem was persistent over the few weeks since I renewed my
subscription, which included multiple re-boots and re-starts, within the
same file and with other files.

But again, this issue seems to have resolved itself immediately after I
de-selected the "Snap On" option under the Grid & Snap menu (Drafting
Settings).  I made this change while the particular file was open, and
the osnap problem was gone immediately after I closed the drafting
settings window.

Turning the Snap back on doesn't bring the problem back.

I don't know what happened, but I'm happy everything is working as
expected now.

(But why does autosave so frequently prevent AREA command from showing
it's result?  I'm in the command, I make my selection, I hit enter...and
all I see is a dialogue saying autosave just happened! I can retrieve
the info by expanding the command line, but still, it's annoying.)

[maxim_k]

>>>>>But why does autosave so frequently prevent AREA command from showing
it's result?

Have you tried to use MEASUREGEOM command with Area option instead of AREA command?