Osnap misses the mark

[Anonymous]

In Civil 3D 2020 the Osnap commands are slowed down and it makes you wait till the magnet grabs the intended point. If we work at our normal speed as learned in previous releases, sometimes the intended points are snapped incorrect. Is there a work around for this problem? I see on-line that others are having this issue also.

[AllenJessup]

If you're working with running osnaps. Setting OSNAPOVERRIDE to 1 will make it so you can't pick a point that isn't an Osnap point.

One thing to remember is that you want to set OSNAPOVERRIDE to 0 as soon as you’re done. That’s because it will affect every pick. If you leave it set to 1 and try a copy, move, offset, etc. you will only be able to pick an entity at a point that matches your running Osnap.

[Anonymous]

This doesn't only happen with the running osnaps. It happens constantly even from the cursor menu and is very bad in our line of work, as it can create very costly errors. When a point is close, but not in the correct location, you cannot pick this up on a check print.

[AllenJessup]

I'm working in Civil 3D 2020.2 / AutoCAD 2020.1.2 with a running osnap of Node. I don't notice any lag or have a lot of misses. You could try updating your graphics card drivers. 

[Anonymous]

s happens with all of the osnaps, not just Node. We have gone back to Civil 3D 2018 to fix the problem. May look for another system in the future.

[AllenJessup]

I was only using Node as the current example. I tried with End also with no lag. If you haven't checked the display drivers. I'd suggest giving it a try. I've seen a lot of problems fixed that way.

[Anonymous]

Our drivers are up to date. Remember, we are not the only ones experiencing this condition.

[AllenJessup]

Well. I thought it would be worth a try if they weren't. How many thousands of user don't update their drivers.

Usually if some users are experiencing a problem and others aren't. It points to a problem or a difference in the machines the software is running on.