Getting OSOPTIONS to snap to intersections

[nrz13]

I was playing with AutoCAD today to improve performance until AMD releases updated drivers for AutoCAD 2015 and I seem to have broken the OSOPTIONS system variable.

We normally have the OSOPTIONS system variable set to "2" (only ignoring negative Z values).  It is occasionally useful to snap to a hatch pattern, but I changed the OSOPTIONS system variable to "3" to ignore hatches for now because passing over a hatch mid-command bogs the computer down for many seconds, sometimes over a minute.

Tiring of switching back and forth today, I added this to my startup LISP so I could toggle quickly back and forth:
(DEFUN C:HS ()(if (= 3 (getvar "OSOPTIONS"))(setvar "OSOPTIONS" 2)(setvar "OSOPTIONS" 3))(PRINC))

However, now when I try to set it back to no longer ignore hatch objects, the osnaps for midpoints and endpoints are the only ones that show up -- none for intersections or any other snaps anymore.

I tried setting it to the default of 7 and also 0 before resetting it back to 2.  I tried going through the options dialog to change it back that way, but still it won't snap to intersections anymore.  My Object Snap options show intersections checked and intersections for non-hatches still work (see attachments below).

Is there a way to reset this back to how it's supposed to be?

[nrz13]

Wow, this is really messing me up.  Not only do I need to be able to snap to hatches to set specific reference points, but now I can also no longer snap light fixtures to our ceiling grid hatch.  This is seriously impeding my workflow.

[nestly2]

Is the problem only with "running" OSnaps?  ie can you OSnap to them if you manually specify an OSnap override within a command?

[nrz13]

When I shift-right-click and select intersection, it gives me the intersection graphic and then snaps to every part of the hatch linework, so there's no way to snap it to an actual intersection.

[Anonymous]

Have you tried using the System variable Editor tool under Express tools?

[nrz13]

I have now, but the results are the same.

[nestly2]

Is the Lisp still running?

[nrz13]

No, I removed it.  I mean, it was still a manual toggle that needed to be activated, but I removed it anyway thinking that might possibly be the problem.  It didn't help, though.

[Anonymous]

can you log in to your PC as a different user and then try using OSOPTIONS? You might have created a variable under local user in the registry and it might only be affecting your user account,

[nrz13]

Unfortunately, when I created a new Windows user profile and opened AutoCAD, the problem was still there.

[zalant]

If the behavior happens within a different Windows user profile, that indicates that the problem is not related to any specific user profile settings (assuming that you've tested with both existing drawings and new ones from default templates).  There is either now something fundamentally wrong with the installation of the program, or it's possible that modified startup LISP files are still in the Program Files folder for AutoCAD and are loading up at launch.  

To fully restore original functionality, without picking through things, uninstall completely, be sure that the folder for AutoCAD within Program Files is deleted, as well as those AutoCAD directories under your specific user folder (Local and Roaming), and then reinstall.  At that point, all should be back to Square One.  Once things are working in their default state, make a back-up of your settings with the Export tool in the Start menu folder for AutoCAD.  Then, try things out again with modifying variables and see how things go.  

One thing to be sure of is that the PREVIEWFILTER system variable is at least 16. This will cause Selection Preview to ignore hatch objects. That could ultimately have been what was causing your minute-long delay when going over a hatch object, as opposed to the object snap holding things up. 

[nrz13]

If all that work is necessary, then I'll just use a restore image I have for my Windows installation.  Not ideal, but if I can't find another solution, that's what I'll have to do.  That would be a lot faster and reliable than trying to remove and reinstall AutoCAD.

By the way, setting PREVIEWFILTER to 16 did not reduce the lag going over hatches.  Setting the Object Snap Options to ignore hatch objects has been the only thing to work for me so far, which is not an ideal solution.

[nrz13]

I restored my Windows installation only to discover that the problem has always been there in my installation.  My coworker's computer is running an identical hardware configuration and I used the same installer for both of our computers, but his is not having this problem.

I then followed the steps from Zac Travis above to uninstall and remove the user files in the Local and Roaming folders.  After verifying all the AutoCAD folders and files had been removed, I restarted the computer and did a new install.  After the installation completed, I did another restart and booted AutoCAD straight up without making any customization or other configuration changes.  The OSNAP hatch problem was still present.

I'm still really hoping this is a switch somewhere in the program that I can adjust, because I'm out of ideas.

[GrantsPirate]

I am seeing the same problem with hatch and osnap.  The only thing that works is to use appintersection and pick twice at the intersection or on individual lines in hatch.

2015 is staying on the shelf for now, in fact I have shelved 2014 and am back to 2013.

[nrz13]

Thanks for the tip, GrantsPirate.  The Shift-Right-click > Select Intersection > Click Intersection > Click Intersection Again method is painfully slow compared to the Click Intersection method it should be, but at this point, it's better than nothing.

Also, glad I'm not the only one experiencing this peculiar behavior.  Maybe there's a chance it will be fixed.

[zalant]

After a bit of checking, the lack of hatch intersection snapping has been logged with our software engineers and they're looking to resolve it.

[nrz13]

Thanks

[Anonymous]

Hi Any update on this? It strangely worked for me once, now my customer is calling me a liar..

[zalant]

Nothing as of yet.  Research is ongoing for a potential future service pack release.

[Anonymous]

So the Service Pack 2 is released and the issue is still not fixed...... Zero kudos!