No idea how you can say this gives better performance when scrolling inside it any distance will cause a major fps drop
1 Like
A few weeks after checking this out, I am very unpleasantly surprised that the glaring performance issues are still there and laggy as ever. Do you guys actually… do anything? Like, for a widget people use so often, wouldnt the priority be speed? Where the heck are your priorities???
Can you add show orientation indicator back to the context menu? I use that often and it not being included feels silly.
1 Like
I seriously hope these performance issues are fixed before this is made public. New updates that push UI that is unperformant add a lot of friction in my workflow.
Most of the huge frametime spikes when scrolling come from ‘SchedulerHostConfig.default’, which has already been reported in this thread. I assume this has something to do with the React scheduler, and if so, it may not be as straightforward to fix?
Even just expanding the children of a single instance (there were only a handful of children), the frame time would spike from ~4.2ms → ~17.5ms, which is a 4x performance degradation over the default frame time. For comparison, the Qt explorer would spike from ~4.2ms → ~9.5ms, making this ‘new’ explorer 1.8x less performant than Qt in this test.
Expanding and collapsing the children in the workspace? The Qt UI takes ~10.25ms. The new UI takes 34.7ms, which is 3.38x worse than the Qt UI.
The average frame time for scrolling in the Qt UI is 9ms, which is 2.14x worse than my average frame time and not really noticeable. The new explorer’s average frame time whilst scrolling is a whopping 48ms! That’s 5.3x worse than the Qt UI and 11.43x worse over my average frame time.
How can claims of ‘better performance’ be made here? How can we adopt a new explorer that can barely do its purpose without Studio dying in the background? There has to be a lot of room for improvement, right?
Along with this, the new UI introduces new frustrations when using it.:
- The hierarchy selection options got placed under a context menu, which now means you have to hover your mouse over a button, wait for the menu to appear, and then you can click an option like
Select Children. Such a little change, yet it’s extremely noticeable and annoying. - When accidentally selecting the parent property, you used to be able to just click off and the parent wouldn’t change. Now the instance gets deleted and you have to CTRL + Z to get it back.
- The
Show Orientaton Indicatoroption completely disappeared. Great. - Collaboration is increasingly frustrating. For example, when changing the name of an object in the explorer, if you have any other collaborators add or remove something in game (which causes the explorer to shift), it kicks you out of the text box. I’ve accidentally deleted items because of this when hitting backspace!
- The new UI is bloated and not as compact as the old UI.
Bugs:
- Plugins like Reclass break the explorer. When you ‘reclass’ an instance that has children, the dropdown for the instance break and you can’t view any of the children. You must restart Studio.
- This error:
I like the styling of the new explorer, but if it comes at the expense of performance and introducing friction when using it, I’d rather throw it away. This needs a lot of polishing before it gets force enabled.
2 Likes
This feature was auto enabled for me today, so I gave it a try and I have to admit it’s not very good…
Here are my main issues with it and why I’ve disabled it again:
-
Noticeably bad performance.
Not much else to say here besides that scrolling and dragging were particularly choppy. -
Unable to select / cycle items by pressing keyboard keys.
In the current explorer you can instantly navigate to and cycle through items by pressing keys on the keyboard.
If I want to find a part named “Temp” in a model full of parts with other names, I can simply press “T” and will instantly be taken to it.
This feature is a must have for me and is missing in this version of the explorer. -
Smooth scrolling is pretty annoying.
It’d be great to have an option to disable it or at least tune the sensitivity. -
Hover / selection colors while in dark mode are too similar / dull.
It’s difficult to tell what is selected versus what you’re hovering over, especially since it ALSO highlights all the descendants of the instance you have selected. -
Not a fan of rounded buttons on a frequent use development tool.
This is a very personal preference of mine I admit, but big rounded corners on buttons I need to very frequently and accurately hover over and click always messes with me.
It’d be great if they could be tighter or possibly optional all together.
Overall, there’s really nothing this new explorer has or does over the current one that would make me want to use it.
In fact after trying it for a while I actually ended up frustrated with how difficult it was to do things quickly.
1 Like
I’ve noticed that when I scroll in the explorer it tanks performance-wise even if I collapse all. Also please provide a setting to either disable or reduce the transparency on the blue selection on children of selected objects.
I’ve just double checked the different in scrolling. Please add a way to disable the easing/smoothing when scrolling, I much prefer the snappy scrolling over the smoothed scrolling. (It’s difficult to read moving text and I have to wait for it to stop moving)
Yeah. This “next-gen” explorer is just unbearably slow. Qt is so much faster it’s insane.
3 Likes
what even is this? “TBD”? happens when selecting basescripts.
what does it even stand for? “to be done”? then just finish it already, lol?
ah, I see now. yall don’t even care about this, right?
(it was reported on april 4 and still not fixed)
Update on scrolling: The smooth scrolling is gone again in the most recent OTA version.
2 Likes
TBD stands for “To Be Determined.”
Previously, when the Explorer tab wasn’t updated to this latest version, as you see in the announcement, it was called "Disable Scripts. " The purpose was to disable any script that a model could have inside, preventing the injection of any fishy codes during playtest publicly/privately in your Roblox project:
There’s a functionality in this beta that im really missing – if you edited an object’s name, then used the arrow keys to move up/down to the next selection, it would save and set the new name, and then move onto the next selection. this allowed for quick, keybind-based workflows that were very effective.
would be much appreciated if the behavior in old explorer could be brought back 
1 Like
This bug (being unable to scroll while dragging instances) is actively occurring for me as of May 8th, 2025. Studio updated the other day for me (when the next gen explorer moved into opt-out) so I don’t think an out-of-date Studio is the issue, I believe the issue may have just resurfaced somehow. This issue has lasted several days and has still persisted after multiple restarts, and it only happens with the next gen explorer beta.
whatever why it was named “tbd” it’s so unclear on what it does bruh
Batch-Replace Issue
I’ve got a very particular usecase that works on the old explorer but not the next gen one. My experience uses configuration instances for NPC"s and other components, which are often copy-pasted between instances and development places. Using the current explorer…;
- Search for an instance name in the Explorer
- All instances matching that name are displayed
- Select all the instances you want to replace and press [DELETE]
- The parent instances of the deleted instances will remain visible in the explorer, allowing you to easily insert the replacement instance.
This allowed for fast and straightforward ‘batch replacement’ operations. Especially by using the arrow hotkeys to select the parent of a selected instance. However, in the next-gen explorer, search results are updated as soon as you remove the selected instances, hiding their original parent instance as well.. This has been a major annoyance since trying out the next-gen explorer.
I can shoot a video but figured written instructions would get the point across - happy to provide other info if helpful @tnavarts
Letter-Selecting Missing
Additional issue I’m running into; I can no longer type on my keyboard to select instances (under the same parent) that start with that letter. I used to be able to select my Assets folder and type a D to have Roblox select the ‘Drops’ folder and cycle through other folders starting with ‘D’ on every consecutive press. This would be helpful to re-add when the arrow keys are brought back.
CTRL+SHIFT Selection Missing
You can no longer combine CTRL-Selecting with SHIFT-selecting. You used to be able to hold down CTRL to select multiple instances, and press SHIFT to simultaneously add a range of instances to the selection. This is no longer possible.
1 Like
It’s toggle scripts. The fix for it ended up being far more entwined and complicated than just this single action, but the fix should ship next week.
Having the place file or microprofiler dump for this would be useful. I can’t reproduce anything resembling these results on the several large places I have.
Are you referring to the new ribbon? I don’t recall any tooltip issues with Explorer. Nevermind, If you’re not talking about that then I might know what you’re talking about. I think we disabled what would be causing that.
It’s because Studio has a special path for when no Luau plugin UIs are being rendered. If you were to open something like Toolbox, you would see the same thing. Improving this is unfortunately quite complicated.
This should be fixed next week.
Interesting, I’ll look into this. Thanks!
3 Likes
@crusherfire Can you link the exact Reclass you’re using? There’s a couple out there.
I’ve experienced it with this one and his free version.
1 Like
I’m using Reclass Classic (the newest one has performance problems I’m not fond of):
Scrolling profiler dump (too large to upload here):
https://drive.google.com/file/d/1ci7OmQD37XqPb7rERkFLKDEUkn96wSyg/view?usp=sharing
Expanding workspace descendants dump (too large to upload here):
https://drive.google.com/file/d/1l0xcHeyz77U_RM8KfUE57C6PnI0qFvVK/view?usp=sharing
1 Like
Thanks, it looks like this is due to some pretty low level UI mechanisms. We’ll see what we can do.
2 Likes
Glad to hear! The current performance is less than satisfactory. Hopefully some fixes can be implemented.