Skipping keystrokes

[Anonymous]

I recently updated to Civil3D 2015, and when I am working quickly, it miss random keystrokes from my keyboard.  Often, I will type "PE" to initiate the 'polyline edit' command, and it will only register the "P", and invoke the 'pan' command.  Similarly, if I type "EX" quickly to initiate the 'extend' command, it will sometimes just register the "E" command and invoke the 'erase' command.  

This coincided with my update from Civil3D 2013 to 2015 - it did not happen in 2013, and does not currently happen in any other software.  If I slow down my typing, it seems to work fine, but don't really want to slow my production.  Any suggestions?

[ACADuser]

I have similar issues as well with 2015. For example when clicking on menu items or within the drawing window I have pause between clicks otherwise it only registers the first click. I am leaning towards my system being out of date with fingers crossed since we are looking into getting new PC's.  One solution to your problem is to type slower.

[annw2]

Are you sure it isn't the keyboard?

[Anonymous]

I had the same problem too, there's been many threads about the same issue. The problem is the program searching for suggestions on the command you are starting to type. It was very annoying. I turned off the command prediction and the problem has gone away, except the occasional command I wasn't sure of where the feature would have been useful. It really breaks the program for those of us who quickly key in command shortcuts often.  Here's a couple threads that dicuss the problem and fixes/workarounds in more detail than I want to rehash:

http://forums.autodesk.com/t5/autocad-civil-3d-general/civil-3d-2015-keyboard-command-hiccups/td-p/5...

http://forums.autodesk.com/t5/autocad-civil-3d-general/command-line-lag-2014/m-p/4842907/highlight/t...

There was a better one I found when I first researched the issue, but I'm having trouble finding it now.  Here's another:

http://www.cad-notes.com/autocad-activates-wrong-command/

#

[redtransitconsultants]

Have you looked at your Input Search Option Settings? This is a new feature I believe from 2014 that searches the command database as you type to help guide you to what you're looking for. It's caused some issues for those quick typers who already know what they need. On the command line, find the wrench icon, click on that and go to Input Search Options. Play around with the Auto Complete, Auto Correct, and the delay time to get it to your liking.

Hopefully this is a solution to your issue.