Studio environment/script editor viewport stuck outside of Studio client

Has there been any updates regarding this bug? Studio is entirely unusable for me in this state, there seems to have been no bug fixes in the past few months, its getting rather frustrating.

cc @R14GENIE, @JorusRetorak

Resetting my studio layout seemed to fix it for me. Try that first maybe?

Nah. No luck. This exclusively happens to any and all additional studio instances I open, which is incredibly annoying when I want to copy + paste some models from one of my games to another. Resetting layouts didn’t work for me

1 Like

Post a reply here:

Can you show a video of the steps you are taking to reset and then the bug? Did a dialog come up requesting you to reset your layout? It should look like this
image

I do that too, but this is not fixed… But still happend… This is kinda a critical issue…

1 Like

still having the same problem with the latest version

Hi all, just an update on docking corruption. We have drastically reduced the occurrences of this over the past few months, but we know there are still people affected by this daily. We have gathered a lot of data since the most recent changes and have a complete picture as to how this occurs and who it affects. At the current time we’re working to drive our instance count of this to 0 via a series of changes we’ll roll out in the coming weeks. There’s been a number of open threads on this from users experiencing this problem, and we’re consolidating them down to one to focus our messaging here. Please watch this thread for updates!

1 Like

I don’t know if this is a fix, I couldn’t get my studio to bug again, but when I was in play mode, and I made my Output float, which is docked at the bottom of my screen, the viewport snapped back to original position. This probably works with any “things” you have docked on your screen. Sorry if this doesn’t work cuz I couldn’t get my studio to do the bug again.

EDIT:
I’ve done this twice and it worked again. can confirm it works, took a few times tho

I have the exact same issue tbh

Hi all, please see this important announcement for our new Studio Docking beta. This was aimed squarely at solving this issue. Try it out and let us know how it’s working!

3 Likes

I sometimes have the exact same issue you are talking about

sorry for the bump, but this happened to me as recent as April of 2024, this bug still isn’t fixed and my Roblox studio just updated. I have been getting this bug for quite a while now but it wasn’t an issue to me since one of my least used plugins would “take the bullet” instead of the editor window, but after the update it has seemed to affect my editor window.

Example:
Normally the ThreeDText plugin would never undock in this way, and when the plugin doesn’t load in by default, the game editor window would instead get affected by this.

turn on the newer docking beta, it has fixed this issue

This thread remains alive for roblox staff to point to when reported again at all as they work on getting the final version of the new docking style done.

1 Like

Hi all - I’m going to officially close this thread. We recently disabled the mitigation for this that resets Studio once this issue occurs because we believe we’re only seeing false positives on corruption at this time, in which case the “cure” is worse than the “disease”.

If you are seeing this, please please respond to this thread and we’ll open it up again. Its possible there’s some odd edge case out there with layout that we haven’t anticipated, we’ll want to hear from you to figure out how to work around this.

1 Like

In the newer docking I’ve experienced times where docking certain things, usually the animation editor crashes studio.

Still experiencing this, I can even send registry or idesettings if needed.

Hi, can you send (DM me if you prefer) screen shots of your layout, screen shots of the issue showing up, any description you have around occurrence rate, etc. Does resetting Studio fix this, or are you reinstalling? Registry, logs, etc whatever data you can send would be helpful. Thanks!

Just following up here - the issue turned out to be some odd flag settings with ModManager. If you’re still using “old docking” you are still susceptible to this error.