Using snaps mid-command with spot elevation labels

[Anonymous]

I've had an issue lately where mid-command (move, copy, etc.) the snap marker doesn't appear. My snaps are on and if I click where the snap marker should be, it snaps. But the marker doesn't show, so there's no way of knowing I've snapped to the correct snap point. It also seems to only happen with spot elevation labels. I've tried all the typical stuff (restart CAD & computer, audit, purge, recover). There doesn't seem to be anything wrong with any one particular dwg either as I've tested on multiple dwgs with the same result. 

[Anonymous]

Update: it's not just spot elevations. So far it's also anything tied to a surface including feature lines. Again, it's not just one dwg.

[AllenJessup]

See if this helps: 

Autodesk Civil 3D Help: AUTOSNAP (System Variable)
https://help.autodesk.com/view/CIV3D/2020/ENU/index.html?guid=GUID-BE7947EB-2A08-4406-A169-4C5E125B1...

Specifically you want to check the AutoSnap Marker and Magnet.

Also if you set OSNAPOVERRIDE to 1. You then cannot pick a point that does not conform to your running osnaps. IOW If you have a running OSnap of Node. You cannnot pick any point that isn't a node. If you do use it. Remember to set it to 0 when done.

You have to type the complete variable name to get it to work,

[AllenJessup]

I think I've seen this but it was on a drawing by drawing basis. If IRC the solution was to do a recover on the drawing. But I haven't seen where it would fail for every drawing.

Strange thought. Have you updated your graphics card drivers lately? 

[Anonymous]

Thanks Allen. It's not a problem with the snaps themselves...all of those settings you mentioned below were the first things I checked. To reiterate, it's only an issue with surface labels and feature lines that I've noticed so far. Moving any other object (polylines, blocks, etc.) there's no issue.

1. Click spot elevation, feature line, etc.

2. Type "move" command

3. Crosshairs disappear and can't hover over a snap which should be visible per all of my settings.

[Anonymous]

It's actually a brand new computer that I've had for a couple months...it just started doing this though. Lucky me!

[Anonymous · Accepted solution]

Ended up restoring my settings to default and that solved it.

[AllenJessup]

---

@Anonymous wrote:

It's actually a brand new computer that I've had for a couple months...it just started doing this though. Lucky me!

---

The computer being new would be a reason for me to suspect that the drivers are not up-to-date. Unless your IT works on them before you get them. The loads on off-the-shelf computers can be many months old.

Glad you got it fixed.