Next Gen Studio - Preparing for Takeoff! [Beta]

I’ve been complaining a lot, I do apologise, I must sound super miserable.

Why is there a weird amount of blank space on the left alignment?

Even with the server tab open, it’s still a bit much.

1 Like

That’s not at all what I mean, I mean buttons like “select”, “material” etc., the buttons within each tab / ribbon (whatever the terminology is) being usable by plugins so we can insert plugin buttons into our custom tabs!

I do like that tabs can be duplicated though, that’s a nice feature!

1 Like

Didn’t think about undocking it, but if it is possible to hide it when it’s docked that would be great. :smile:

You can do this now with the JSON approach

Figuring out the UI for visually building complex controls is going to take a lot of work and is not a high priority for leaving Beta.

1 Like

I love that you guys are constantly attempting to improve the overall quality of the studio’s UI, but why did you guys have to throw “View” as a Misc Category of Studio to the top left?
Nobody ever looks at that location unless they want to publish or change something in their settings!

“View” deserves it’s place where it was before, I do not understand why you had chosen this to be done and it feels incredibly annoying that we constantly have to learn these never-ending Studio changes that just burdens us with having to learn the Studio’s hierarchy all over again to find each particular button for each particular purpose.
Worst part is, if a Developer installs Studio and has this new UI, is Snap to Object enabled by default? If that is so, then I’m extremely questioning the direction of this new major Studio change.

In short;
Add a feature just like Opera GX does with Google Chrome where you can import to the new UI the old feature structure so you don’t need to be left confused whenever each Studio redesign Beta comes out. (I swear it has become like a yearly thing!)

1 Like

Absolutely this. This is such a dangerous and awful design choice, especially when we dont have the ability to add viewports it makes no sense to be able to remove it when that’s the same as closing studio.

Well we call it “docking” but really it’s the same as the old toggle, IMO. Just give it a try!

2 Likes

Definitely should be customisable or atleast responsive, I feel like the space between with the server tab open is decent, but without its way too much whitespace.

1 Like

It fully depends on your window width and if your tabs are centered or not (you can choose left alignment). Beyond that, there’s some reserved space for the dynamic debugging controls when you’re running a test session:

image


Ah, there is definitely way less white space when in a playtest, like @BritishTrainspotting said though, should definitely be responsive to make it look less awkward.

1 Like

I see. Thank you for the clarity. We are starting to talk about how plugins can better integrate now that we have way more options beyond toolbars and simple buttons.

1 Like

Apologies for the rapid posts, I’m sorta navigating it again live as we speak,

I seem to have a lot of separators for seemingly no reason in the plugins section.
image

1 Like

Also where are your icons?? This is the standard Plugins tab? Not duplicated or customized?

1 Like

I’ve had that issue too, also sometimes the plugin icons duplicate. I’ve only had that happen with the Magic Wand plguin though, it sometimes just has 5 buttons. Not sure if thats an issue on your end though

Icons are because the plugins in this image are based of the legacy method of making plugins, which modern studio doesnt seem to support, newer plugins work fine.
image

1 Like

Got a question
Is tab changes save in local or cloud?
cause people might not want to edit tabs every time they open studio on other device😅

1 Like

Local… for now. But we save them in your user directory so they don’t get clobbered by Studio updates/installs. You can easily copy them from one machine to another right now.

But cloud sync’ed would be nicer. We would need to work out how to handle the UI and plugin dependencies in a robust way.

1 Like

I’ve given it a quick go and yes you’re right it is the same as the old one. Again, I think it would still function without the x (if the UI allows for tabs without them) since the window has its own x.

I did however come across something odd, if you full-screen the separated viewport window the right side gets cut-off slightly. It doesn’t happen if you put the window on one half of the screen. This also happens with the old studio ui too and I’m not sure if it has been reported already or not:

1 Like

One thing you could try is duplicating your Plugins tab and taking a look at the JSON to see what’s creating those separators. My wild guess is you’ve got a handful of local plugins causing that?

Ah ok. Thanks for the screenshots and details. I’ll make sure there’s a ticket for it.

2 Likes