studio will exit the test, and you are left with a very confusing layout; the 3D view is missing, nothing is interactable, and if you minimize the window then you can see the non-interactable 3D viewport as a separate entity on the taskbar and desktop.
the only way I’ve found to fix this is to restart studio entirely.
The bug does not happen every time.
Today I was able to reproduce this a few times in a row by opening 2 baseplate places in separate studio instances, and having 2 scripts open in each before testing on the 2nd baseplate.
I started noticing this bug a couple days ago.
Windows 10
Studio Version 0.621.0.6210527 (64bit)
Latest Studio version available 0.621.0.6210527
I’ve restarted my computer between sessions
This infamous bug was squashed for a while. It has come back. Here is an old thread:
I’d love to be the one to narrow down consistent repro steps. Since it doesn’t happen every time, and some days it happens multiple times in a row, best I can do is give an update on what I was doing the next time it occurs
This is a different bug. We pushed a new update to the docking system this week to decrease the chance of this one occurring. It was caused by a combination of having a lot of plugins and some bad luck. Hopefully our update resolves your issues.
Hi, for this issue please refer to this thread which is where we track this long standing “docking corruption” issue. The good news is that we believe this is solved. Please respond to that thread if you still see this issue.
