Since using SketchUp 2025, I’ve suddenly noticed that the Alt key and the Ctrl key don’t always work properly. For example, when I want to use the eyedropper with the ‘paint bucket’ tool, I used to do that with the Alt key, but now it doesn’t work correctly. I have to first use the orbit tool, and then it works again. I also have this issue with ‘undo’ — when I press Ctrl+Z, SketchUp often doesn’t respond. Is anyone else experiencing this? Is there anything I can do about it?
Yep, very irritating, and I extremely surprised you are the 1st reporting it.
It doesn’t always happen. Often, everything is fine at first, but after a while, I suddenly have this problem. Really very strange and indeed quite annoying.
Multiple su sessions might trigger it, but it’s not for sure
Will try that right now!
(I most of the time have more sessions running)
I have the exact same issues. Did you find any solutions?
I have the same issue and it’s extremely irritating, and a big time waster. @sketchUp-developers any update on this?
Occasionally there are problems with Alt and Eyedropper: Eyedropper remains (got stuck) - no matter how many times you click Alt (the workaround is to press Paint shortcut again); or, it’s impossible to activate Eyedropper - some orbiting needed.
I have the same problem here, very annoying.
My workflow isn’t as efficient because of all the extra clicks… Ctrl+Z doesn’t work properly, the pipet and bucket tool don’t work properly, …
Please come with an update to fix these problems.
Interestingly, this Alt bug affects Fredos PaintThru as well
I hope someone at Trimble is reading with us because it’s getting really annoying.
The forum is not a place for guaranteed answers, best you can hope for here is that somebody from support/the right team notices your post. Also good if you put it into the bug report subcategory (and a title that suggests this is a bug rather than an opinion on a change):
Having said that, it looks like somebody has reported this issue to us in Centercode so we are aware.
A change has been made to the Alt behaviour for ticket SU-60286 so hopefully that will help with that in the next release.
There is however no mention of Ctrl-Z issues in that ticket so I’m not sure if it will help with that.
I reported this in 2025 as well and it was so bad that I never used 2025 at all. I am noticing a similar issue in 2026 but not as bad.
@TedVitale_SU Could QA department create a script that’d try to assign all imaginable keabord shortcut combinations (incl. numpad!) to some command and then try to execute it? Lots of shortcuts are impossible to assign for no reason and this black list randomly expands (which means old shortcuts aren’t working anymore) from release to release.
Have you turned on sticky keys by accident?
Press shift 5 times on windows - to toggle it
https://www.microsoft.com/en-us/surface/do-more-with-surface/defining-sticky-keys
2 brief examples: try to assign [ shortcut
Or Numpad. - it will act as Delete anyway. There’re many others that worked in 2024 and misbehave in 2025(6). And I hardly understand why PageUp and PageDown gotta be locked to Scenes
the [ key is reserved for VCB, which is why it’s disallowed for assigning as a shortcut. That list also includes: 0-9 < - ( Shift+, and Shift+9
Numpad- is distinct from the normal dash though, so you should be able to use that as a shortcut.
@Phil_K Thanks for your attention,
[ is reserved and ] isn’t? [ worked fine literally fot decades. I might be mistaken but nothing has changed in 2025+ VCB syntax.
Perhaps I describe the problem not so clear: Numpad. key is executed as Delete in SU 2025+, - we didn’t have this issue in 2024
Yea, that’s the full list for VCB, ] and ) are not reserved. + and . should also probably be reserved, but right now they’re not. You’re right though, these haven’t been changed since at least 2017.
For shortcuts that aren’t able to be modified, we almost exclusively do that for OS shortcuts, like Ctrl+C / Ctrl+V being mapped to copy / paste clipboard actions. PageUp / PageDown does technically fall into that category for scrolling, and it being used for scenes was probably because of the overlap. Personally I do think some of the restrictions can be loosened for the more obscure OS shortcuts, but I can’t guarantee if that will happen or not.
Numpad. does work as a delete for me on 2024. In what context are you using it where the behavior is different in 2025+?
Please take a look if PageUp/Down, Cntl+P etc could be set free - we don’t have such heavy restrictions in other DCCs. Could you please remind me in which cases [ being utilized in VCB?
Numpad. key in conjunction with highlited NumLock button acts as Numpad. in 2024 and older. In 2025+ it’s unalternetavly Delete.
Thank you
