Have you ever been working in studio and go to press Ctrl+D, Ctrl+X, Ctrl+P, or any other Ctrl+Key shortcut, and it doesn’t work? For some reason, ROBLOX doesn’t recognize it as a keyboard shortcut? The bug that seemingly happened randomly with no successful repro steps? Yeah – that bug.
It happens because you inserted something from the toolbox. Something that simple has been causing this infuriating bug that broke keyboard shortcuts. I remember us complaining about it to Khanovich a while back and he wanted to fix it, but couldn’t because he couldn’t figure out what was causing it. Now, we have a 100% success repro on how this happens.
ROBLOX, now it’s your turn
Edit: Dragging out of the toolbox doesn’t seem to cause this bug, but clicking on anything (whether it be a single part, a model, or a script) and having it insert into the game causes the bug.
Nice find! From what I’ve found, this occurs until you select the item in question or perform another operation on it. Are there any other cases where this happens?
I’m having trouble reproing this. I’ve inserted stuff from the Toolbox and I’m able to duplicate them (through CTRL+D) without any errors. Is there something I’m missing?
[quote] Nothing in this thread is helping me to reproduce this error (and I am still plagued by ctrl+D breaking very often, and I don’t recall even using the toolbox beforehand)
70% of the time the shortcuts break are when I’m merely switching between studio instances [/quote]
Try these exact steps:
Left click Quenty’s Destructable Observation Tower in free models
Right click the render window (don’t left click anything)
Try to use Ctrl+X on it
Thinking about it though, re-selecting the item fixing the issue doesn’t sound like the bug I’ve experienced before, because even if I had inserted something from the toolbox prior, I don’t recall any of the items I couldn’t use shortcuts on being inserted from the toolbox – they were already in the game. Since re-selecting the item fixes it, my best guess is that it has something to do with Studio not properly detecting selection changes, and that’s why it doesn’t work for models inserted from the toolbox. Upon further testing, it seems that using game.Selection:Set() on something that wasn’t already selected causes the same issue. It has to have something to do with items not being properly selected. I would imagine that either CmdUtl (only plugin pretty much everyone uses, unless someone can confirm experiencing this bug without CmdUtl) or something in the ROBLOX selector tool that doesn’t select the item properly. This is odd.
“Try these exact steps:
Left click Quenty’s Destructable Observation Tower in free models
Right click the render window (don’t left click anything)
Try to use Ctrl+X on it”
Didn’t repro the bug for me using system menu or alertcoderf using ribbon bar ;~:
What other variables haven’t we controlled? [strike]Did you start fresh by opening a first studio window then doing these steps?[/strike]
Edit: I just started fresh by opening a first studio window then doing those steps and it reproduced the bug. O:!!
Yes – using both SystemMenu and RibbonBar, in a new place (Ctrl+N) as soon as Studio was opened, inserting something from the toolbox and following those steps I am unable to use keyboard shortcuts on that object until I re-select it.
I wouldn’t think so – I’m putting the render window back into focus. Either way, how does that explain the same behavior we get with game.Selection:Set()?
