Spacebar problem - seems to click twice with one hit

Spacebar problem - seems to click twice with one hit

3d-labor
Collaborator Collaborator
475 Views
15 Replies
Message 1 of 16

Spacebar problem - seems to click twice with one hit

3d-labor
Collaborator
Collaborator

At least since AutoCAD version 2024, there has been an issue where the spacebar is often interpreted as a double-click. This naturally leads to command interruptions, etc. If you restart AutoCAD, it works normally for a while, but then the issue reappears. There is a trick to dock the command line at the bottom, which prevents this from happening, and it works. However, with three monitors, I need the command line in the center of the screen as a floating window. What else can be done to avoid this error?


Workstation: Ryzen 9 5950x@ 4,20GHz 64 GB RAM, Nvidia RTX 4090, Win10 Prof.
Rendernode: AMD Threadripper 2990wx@ 3,20 GHz 64 GB RAM, Win 10 Prof.
Autodesk Building Design Suite Premium 2025, VRay 7, ForestPack, RailClone, RichDirt, KStudio ProjectManager....
0 Likes
Accepted solutions (1)
476 Views
15 Replies
Replies (15)
Message 2 of 16

imadHabash
Mentor
Mentor

Hi,

How about trying another keyboard?

 

Imad Habash

EESignature

Message 3 of 16

pendean
Community Legend
Community Legend

You need a replacement keyboard: nothing more.

0 Likes
Message 4 of 16

3d-labor
Collaborator
Collaborator

When I dock the command line to the bottoms of the viewports all is fine. Also when I start with editing a drawing with a floating command line the first few minutes all is ok. The 3dconnexion keyboard is about 8 months old. In all other programs the keyboard works normal. May be, that the keyboard driver has an error in the AutoCAD section.


Workstation: Ryzen 9 5950x@ 4,20GHz 64 GB RAM, Nvidia RTX 4090, Win10 Prof.
Rendernode: AMD Threadripper 2990wx@ 3,20 GHz 64 GB RAM, Win 10 Prof.
Autodesk Building Design Suite Premium 2025, VRay 7, ForestPack, RailClone, RichDirt, KStudio ProjectManager....
0 Likes
Message 5 of 16

cadffm
Consultant
Consultant

You will find other threads with the same issue&solution/workaround!

It works with docked commandline (as I use only, with 4 lines visible)

 

You can check your productversion (command: ABOUT),

but I am not sure if it solved with the latest update.

Sebastian

0 Likes
Message 6 of 16

pendean
Community Legend
Community Legend

@3d-labor My commandline has been undocked since AutoCAD 2016 and remains so through 2026, and my space bar on my now third keyboard since then does not double-enter at all.

 

If testing with a plugged-in keyboard that does not use your keyboard drivers exhibits the same exact issue, then you'll need to open a support case with Autodesk direct yourself, post back if you are unsure how to do that.

0 Likes
Message 7 of 16

tramber
Advisor
Advisor
Accepted solution

Same for me... with a 2017 version.

From time to time. I dock and then undock the command line to fix that in a second.


EESignature

Message 8 of 16

TheCADnoob
Mentor
Mentor

Assuming you have dont the whole restart thing, 

 

You may be dealing with sensitive keys, or 'bounce' keys.

 

You can try disabling this in windows and see if it helps

 

TheCADnoob_0-1746452325989.png

 

CADnoob

EESignature

0 Likes
Message 9 of 16

tramber
Advisor
Advisor

@cadffm  a écrit :

You will find other threads with the same issue&solution/workaround!

It works with docked commandline (as I use only, with 4 lines visible)

I've been trying to find the thread with no success. Sorry. But I posted what I just said. It happens since many years on some PCs, including mine.


EESignature

0 Likes
Message 10 of 16

cadffm
Consultant
Consultant
0 Likes
Message 11 of 16

cadffm
Consultant
Consultant

@tramber  schrieb:

Sorry.

Hey, I posted earlier than you, so I didn't reply to your post - no need to PLEASE here 😆

 

Sebastian

0 Likes
Message 12 of 16

tramber
Advisor
Advisor

Thanks @cadffm  , for me and for all.

I was exploring my past messages hours ago, due to that present thread and didn't find.... as the pages are not very reactive, I didn't insist.

 

This bug made me nut at the time. Thanks to this place, I have a solution. Hope it is convenient for @3d-labor 


EESignature

0 Likes
Message 13 of 16

3d-labor
Collaborator
Collaborator

I will use this workarround and open an support case. When I heard that some users have this problem since Ver. 2017 I suddenly was thinking about the hatch command, which needed 20 years or more to work  the way I always imagined in Ver 2026  (the good old "A closed boundary could not be determined" problem)

 


Workstation: Ryzen 9 5950x@ 4,20GHz 64 GB RAM, Nvidia RTX 4090, Win10 Prof.
Rendernode: AMD Threadripper 2990wx@ 3,20 GHz 64 GB RAM, Win 10 Prof.
Autodesk Building Design Suite Premium 2025, VRay 7, ForestPack, RailClone, RichDirt, KStudio ProjectManager....
0 Likes
Message 14 of 16

cadffm
Consultant
Consultant

Do it!

But if you use my search phrase, you will see that it did not started with 2017,

also in older Version you could had this 'memory' problem!

Like a lot more problems, what can appear while working in one session.

 

Sebastian

0 Likes
Message 15 of 16

tramber
Advisor
Advisor

W10 and Acad 2017 on a PC I often use. Still.

It happens once a week, more or less. Not very much often. What is responsible ? Acad or W ? I donknow 😎

Not critical at all. Easy to fix. This is why it only became a story to tell... for me.


EESignature

0 Likes
Message 16 of 16

pendean
Community Legend
Community Legend

@tramber wrote:

...It happens once a week, more or less. Not very much often....


Then it's a local problem unique to you, aka unknown gremlins, you have "something else" going on at that same time that triggers it. There is never going to be a mass solution for something you cannot recreate on demand then show us how to repeat it on demand as well. Sorry.

0 Likes