I’m afraid this does not fix the issue, I tried un-ticking the setting and I still ended up getting in the same situation where the bug selects almost everything in the explorer.
This was a fix just for the case where pressing the hotkey during gameplay would trigger select all. The bug is a separate issue that we still cannot figure out how to reproduce on our end
Oh alright, nevermind then, I appreciate the info nonetheless
Oh, much appreciated. I was not aware of this setting before you mentioned it. This will definitely come in handy.
Can confirm this is happening to me as well, it will select things above the part that was initially selected and freeze for a minute or so, at times it crashes. This bug usually occurs when I’m selecting all children from a model, there should be a shortcut for that instead of having to shift-click or using the select all children option in the right-click menu.
There is work underway on the Explorer pane which will fix this and many other small QoL issues. Closing this for now as we won’t be individually addressing these before the main change ships.
@Dogekidd2012 @thirdtakeonit Here are some examples of what happens when I try to union an object for example:
Hmm, I wonder where the part went, despite me not selecting it…
edit: mind you - this only happens when I union objects by selecting them from the explorer, and not when I click on them in the game.
and @Dogekidd2012 as well as @DeFactoCepti and @tnavarts
This has been happening for a looooong time for me when I select an item in the Workspace or Explorer window, then Alt Ctrl Left Clicked another item, then Alt Shift Left Click another item from the Explorer window.
First shot, I Left clicked the workspace window on the center floor area, and it selects the House in the Explorer window. This is normal behaviour.
Second shot, I Left clicked the blue line for the AlignOrientation, which selects just the AlignOrientation in the Explorer window. Normal behaviour.
Now here I Alt Shift Left clicked a Part from inside the Explorer window, which should select everything from the AlignOrientation to the bottom highlighted blue Part (the one I clicked). It now selects everything from the Doors Model, past the AlignOrientation, and down to the Part I clicked on in the window. Unexpected behaviour. I didn’t include the Properties window, but as you can see there are just 19
items highlighted in the Explorer window. The top of my Properties window (not showing cuz it’s on my 2nd monitor) says 21
items selected
In the past week or so it’s got MUCH worse:
- Usually it’s just the item I select.
- Sometimes its a few random Parts from the Workspace. Not necessarily in sequential order.
- Occasionally its a multitude of items in the explorer window. Again, it may or may not be in order.
As in the third picture there have been cases where I’ve selected one item from the Workspace using Left Click, or from the Explorer window using just Left Click, which should just reset and choose a single item.
I then select a number of individual items in the Workspace or Explorer using Alt Ctrl Left Click, which should add them individually.
In this example lets say I’ve selected 1 original & 4 additional items = 5 total.
When I look at the top of the Properties window it should read 5, but occasionally I’ll see a random higher number.
I’ll scroll through the items visible top to bottom (not the ones inside unexpanded items) in the Explorer window, but can’t find the other items highlighted, I just see 5 items.
In the workspace I have occasionally seen the blue selection box of these hidden items displayed. Those times I didn’t think to expand the item’s Parent in the Explorer window to see if it was highlighted there though.
The additional items have been picked from inside models, or folders but these items haven’t automatically expanded like they would if I Alt Ctrl Left Clicked on them in the Workspace.
I know it’s a long post but I’d like to give you as much info as possible.
Using sleitnick’s Parts Counter plugin the showcase I’m working in currently has 37,806 Parts, 22,502,050 Voxels, and 53,602 Instances.
My computer is an Acer
Device name | DESKTOP-G14D63F |
---|---|
Processor | 12th Gen Intel(R) Core™ i5-12400F 2.50 GHz |
Installed RAM | 12.0 GB (11.8 GB usable) |
System type | 64-bit operating system, x64-based processor |
Pen and touch | No pen or touch input is available for this display |
Edition | Windows 11 Home |
---|---|
Version | 23H2 |
Installed on | 2023-04-01 |
It doesn’t have any issues running Studio, and I only have Spotify and the DevForum open while I’m building.
Oh, and uninstalling/installing Studio hasn’t helped…
For god sake solve this already I’m afraid if I accidentally move all the parts and the studio crashes, I won’t be able to undo the moving objects.
I recorded this video to clearly demonstrate what is happening with this bug. I named the relevant objects to make it clear how I am selecting them. The bug is not random, it is entirely based on your previous selection, and only occurs when you transition from selecting objects in the workspace window, to selecting objects in the Explorer.
Thanks for getting us this repro video, a fix for this should be coming in the next release!
Update: this should now be fixed in the latest release. Thanks for the report!
Looks like it’s not fixed:
There’s a more thorough fix for this that should be available in the next release - will let you know when it’s live.
It mainly addresses the case mentioned here. lmk if you continue running into this bug outside of that case
The more thorough fix for this is live now. Please let us know if you continue running into problems with it!
This is still happening on version 636, I hold shift and press then deselect with esc as seen on the video
Before you do the shift-click, is anything already selected in the Explorer? Or does this only happen if nothing is selected before the shift-click
Nothing is selected before the shift click.
Gotcha, in that case we should be able to fix it so that it’ll just select the single instance clicked. I’ll look into finding a fix for this and will let you know when it’s live
This case should be fixed now in the latest Studio - lmk if you continue running into it!