Erase command doesn't work when cursor already on object.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I had a hard time explaining the issue in one simple sentence for the title, but here is what is happening: The erase command works fine normally, I will hit 'E', hit the spacebar, select my object, and right click to erase. The problem happens when my cursor is already on the object I want to erase, then I hit 'E', spacebar, left-click to select, right-click to erase, all without actually moving the cursor. The object does not erase. At first I thought I was just drafting too fast and creating issues for myself between keyboard, mouse, hand, etc., but after enough frustration I finally slowed way down and took a minute to find the source of it. Even if I do it slow as molasses, 'E' (wait two seconds), spacebar (wait two seconds), left-click (wait two seconds), right-click, object doesn't erase. If I leave my cursor in the same place, it can take five or more tries to get it to erase, but it will do it. That's the crazy thing is it doesn't happen every time. Only about 90% of the time. Very repeatable. After seeing this happen for myself and still not believing my eyes after doing it five more times, I went to my coworker's PC and the problem does not occur. It's not my PICKFIRST variable or my noun/verb selection as it still happens when those are changed.
For reference, I am working in a maximized viewport because that is how I usually do my plans, but the issue happens in both paperspace in and outside of a viewport, and in model space, and in every drawing, not just the project I am currently working on. It happens in our templates, and in a wblock I just made to make sure it wasn't something in our drawings (is this a pretty good method of testing??). I just checked and I could not recreate the issue on my coworker's PC. We are both using AutoCAD 2017 on fairly similar systems. We probably have different profiles, and I did not try resetting my AutoCAD back to defaults yet. Maybe tonight, after hours. I assume a full reset would solve my issue, and my system would probably appreciate it... But maybe there's an easy fix that someone knows that could save me some frustration? Thanks in advance.
