NOTICE: You can disable this feature in “Beta Features” up until June, when they will fully delete the old Ui. Check the solution on this post for more info
After almost a decade, roblox has “updated” their studio gui from figure 1 to figure 2.
To start off, this has been a beta feature for literally about 2 years, if you don’t remember seeing anybody use it, it’s because they did not care at all. However, with the recent release of the new explorer, which is fine, they released the ENTIRE NEW GUI. Not only is the structure heavily different from what we’ve been used to for about a decade, it has so, so many bugs, like random ui’s popping up, the topbar ui leaking into other applications, etc.
This image shows the topbar UI leaking into another app, however it is hard to see. Look at the edges.
For users: I have linked a possible solution to this issue, however in June, we will not be able to use “Legacy” studio UI anymore. Enjoy it while it lasts.
Expected behavior
Fix the bugs, maybe allow us to reformat stuff, or just let us choose between the two. I get that this is “the future” but I’m not liking it much.
The structure of the Roblox Studio ribbon has changed many times in the past 10 years.
This feature is optional, it is a beta feature. If we removed every beta feature because it was in beta and had bugs, Roblox would never get anywhere. Please do not use bug reports for this kind of criticism. Bug reports are for bug reports, not feature requests. You made a point about the UI’s popping up or spilling into other applications; report that, not make a rant about how “buggy” a beta is. The point of the new studio ribbon is for customization and performance, and you could eventually make it similar to your original Ribbon muscle memory. Changes happen, you have to adapt, this is for the better. People will complain, eventually people will accept it. Humans don’t enjoy change.
Not really a bug report, methinks. Roblox won’t just remove, or make a feature that they’ve spent years on “optional” just because a vocal minority dislikes it. Many of the bugs you’ve pointed out are already known, and will be fixed by the time the UI fully releases. If you have any specific bugs that aren’t already known, then you could make a specific bug report about that. But this? This is more of a feature request, if even that.
As of now? Opt out. This is still a beta feature, so if you wanted to opt out before it fully releases next month, then you can!
You’ll get used to it, it grows on you. Sometimes you have to be open to change.
When I meant 10 years, I really was exaggerating. Sure, they swapped a few things here and there, improved icons, etc. But this is just straight up moving things into different places.
Not really.
I get that this is all new and fancy, but us long term developers are used to the old layout, and not this one. It feels like Unity.
Ok, so file a single, detailed report on each of these issues individually. Right now you’re just going on tangents about how you want it reverted and “destroyed”. This is not how you file bug reports.
Change is one thing, but this is not just about change. Roblox is shipping their new features in an unfinished a buggy state, just having the new ui set as default is kinda ridiculous right now, and my third eye tells me it will still be buggy and unfinished in june, when they will remove the old ui, and everyone will be pissed.
It took them years to actually add ChannelTabs and to partially fix the performance issues of TextChatService, and it still isn’t up to par with the Lua Chat System.
I understand that roblox is updating their legacy codebase to make it easier to build upon. The problem is that remaking features from scratch takes a lot of time, especially in the details, to get them up to par with the existing feature, and thus their introduction should be taken slowly
Saying people don’t like change is true, but it also became a lame excuse to dismiss any criticism people have about change
This is the point I am trying to make. The new UI is inherently flawed. It’s a good idea in retrospect, but they need to move a few things. We shouldn’t be oversimplifying features, especially in a game engine. Yes, it is also extremely buggy. I had provided 3 images of bugs that I and others have encountered multiple times. There are 100% way more bugs.
Bug reports shouldn’t be used as a space to rant about upcoming features, it’s a bug report. Also, most of these bugs will probably be fixed by June, it’s usually a situation where they release all the bug fixes at once. This is a beta, the point is to report bugs, it will be buggy, that’s the point of a beta. The reason I believe they opt’d-in everyone is so that we can catch more bugs before the estimated release. There is no excuse for constructive criticism, but destructive criticism doesn’t get us anywhere.
I absolutely agree on that one, this is a poor bug report
Thing is, after reading responses in #development-discussion and the recent #updates:announcements topics, I keep seeing the same excuse of “people don’t like change” and you were the unfortunate victim of my annoyance with that excuse. I’m too lazy to post that again and again though…
If you want my opinion, my guess would be that the developers are under too strict timelines to finish their features. They often state that “this will be ready before the release” or “we hope that this will be ready before the release”, this last one shows that the release date is likely not dependant on the readiness of the feature, but rather a more fixed timeline
Making it opt-out right now probably wasn’t for more bugs as they don’t seem to be lacking stuff to work on, they have yet to release the update that makes the ui more condensed (and imo makes it look much nicer), and to me it’s really weird that they opted everyone in before that
