Probably, It’s only arts. You can get new explorer by Flags, but It can kill your studio.
i know, but by 2025 we should have the full new UI according to OP in the first post
as for the new explorer, it doesn’t work anymore at it just errors
That is an estimate.
i know, but estimates say that the full Next Gen Studio will come in the next 2-3 years
So basicaly we will expect to customize the tabs? And will give current and old users the same tab layout?
Some of the old ribbon buttons seem to be missing from the new version, including the “take screenshot” button. In the old ribbon, it’s under the View tab, but it isn’t anywhere with the new UI; I checked all of the tabs and menus, and couldn’t find it.
I would use a keyboard shortcut to work around this, but for some reason, it isn’t listed as an action in that window, as shown in this composite screenshot (two screenshots):
Why would anyone need to use this action? Just use the print-screen key, ShareX, or Snipping Tool, Mary!
Native screenshots just capture what’s on-screen, not what Roblox Studio is rendering in its viewport. When emulating a device, if I view the game at its “actual resolution” then use the “take screenshot” action, it’ll actually save a PNG image at that size!
For example, this is a 4K picture of Crossroads, captured using this method:
Note about this upload...
Unfortunately, the DevForum downscaled the image to 1080p, but the original PNG file was a 4K image.
I like to use the Device Emulator (which is in one of the dropdown menus) to temporarily increase the viewport’s size to save very high resolution “renders”, and I wouldn’t like if this became impossible once the new UI completely replaced the old ribbon. It would be nice if “Take Screenshot” was added as a keyboard shortcut action (and a ribbon button once custom tabs are added).
I know you weren’t asking me, but I personally find the Quick Access Toolbar undo/redo buttons useful because of their tooltips. Roblox Studio doesn’t always handle undoing and redoing actions properly (somehow), but these buttons’ tooltips give me an idea of what property will be affected if I were to click it. Unless this info was shown somewhere else in Studio’s UI, removing the undo/redo buttons would make doing those things feel risky, not knowing what I’ll be changing.
There will be the default set of “system” tabs that we will maintain and update where it makes sense for most users. But yes we believe the best way forward is to spend our limited time making Studio much more easy to customize/personalize.
We have to migrate a lot of old tools to the new actions system we developed. Right now we’ve got about 200 moved already and we will keep working on those as we can. Screenshot will remain available based on the great use cases you and others have provided. I need to double check with the team but I think this migration would also make it bindable to a shortcut as well.
Someone else also pointed out they like the undo/redo visual state as a way of working. You should be able to add those back to your custom tabs.
RDC 2023 was showing mock ups/concepts and those remain the north star we are working towards.
Completely overhauling Studio is a massive task because we have 10-12 years of legacy to migrate, new features getting added every week by numerous different teams, and millions of active users.
We don’t have a big enough team to build a whole new Studio off to the side and then switch over (this is also why we can’t support old and new UI for an extended period of time). This forces us to make our way towards the north star in stages and unfortunately there will be some awkward mixing of new/old while we do that.
None of us want to stay in that awkward state so I hope most people trust us that things will continue to improve slowly.
Yes we need to get back to working on the docking again soon.
iirc there’s a flag to turn them on, if anybody knows feel free to share bc i’d like to in hope it solves a few of my wine bugs with the explorer (and gradually getting darker dark everywhere js nice)
The new Explorer and Properties are under heavy development. Definitely not ready for any sort of use… nobody is using them internally yet and I’ve barely seen it. I couldn’t even tell you what flags are required to properly turn them on (we almost never have just one clean flag that turns a complicated feature on)
you mean this?
someone apparently had a darker Explorer & Properties widgets in the post talking about the new Controller Emulator
is this signs that work on the new Studio color scheme has begun???
I think I managed to turn it on before, though it was so early in development that I think it was more like a plugin, I had to run it on a full window and it was barely usable.
Yes this does not look like the overhauled Explorer (which, like I said, is under very heavy development currently)
We are absolutely sorting out how to get Studio on a consistent color palette and moved over to the new color system!
Here’s a peek at a proof of concept where we’ve been evaluating how much work that’s actually going to be (actual screenshot, not a mockup):
Also as an unrelated question; will the current docking implementation be thrown out in favor of something Lua? As a Linux user it’s been really painful ever since the update a few months ago and I’m still holding out for a fix
I don’t know about the Lua part but I would love to revisit docking. We burned a ton of time just trying to get rid of the corruption issue and our primary engineer working on it left. I’ve never been fully happy with the compromises we had to make. We’ve been talking about going back into it with fresh eyes.
A docking re-implementation would be amazing. (Especially to address the issues above, I’m not too fond of it when I have to be careful not to cause a window I’m trying to resize or move to be docked) Though IMO you should visit it after a majority part of the new gen studio UI has been completed and transferred over.