Stopping Studio can cause widgets to be in an invalid state

A recurring bug I’ve had for a long time now (one that a lot of other devs have also echoed similarly) is that when you stop running your current instance of studio, many widgets will go to an invalid state seemingly at random (big emphasis on Random). This bug seems more reproducible when you start/stop really quickly, but will happen nonetheless.

Invalid State can mean a few things here:

  1. Opening previously closed widgets (even plugin widgets)
  2. Opening widgets that were only supposed to open on studio startup (most commonly plugins, but others like the toolblox love to open themselves all the time).
  3. Stacked widgets displaying the wrong widget (ex: properties and asset manager are stacked, it’s selected/highlighted properties, but shows asset manager instead)
  4. Setting the currently selected window to a widget instead of viewport (or whatever was selected before running).

Luckily all you have to do for most of them is just click them once or twice and they’ll update to the correct state, unless it’s moved/closed/opened a widget, then you have to re-organize it yourself.

1 Like

Thanks for the report! We’ll follow up when we have an update for you!

2 Likes

Hi, can you be more specific about some of the behaviors seen here? If you have widgets open in edit, then hit play, then close them, then stop, what’s your expectation as to what should occur?

Are you working across multiple studio processes (either multiple places editing, or server/client test)?

Are you using the new docking beta?

1 Like

Hi,
Effectively the widgets do this behaviour while being completely untouched.
Widgets are fine → hit play → hit stop → Widgets have issues

I can give some more specifics about the issues I’ve suffered.
I often have issues where stacked widgets like in this image:
image
will have 1 currently selected, and then once studio stops the session, it will inexplicably swap to a different one (in this case, toolbox), while the displayed UI would be unchanged, thus requiring some clicking around to force it to update to the correct state.

Toolbox often re-opens frequently by itself on stopping the session, though I haven’t heard too many complaints from other devs about that specific issue, so I’m not too sure about that one.

Widgets that are created by plugins that are only supposed to open on startup will randomly open up and dock in very random spots when stopping a current session. I’ve even talked to some of those specific creators of the plugins and they absolutely cannot figure out why this is occurring.

I mostly work in solo tests, but I tend to have multiple instances of studio open on average. Usually my main file I work on is a team create place, and my other instances tend to be local files, though that’s not always the case.

Also, I did not know about the new docking beta. I wish I had known about it before making this post so that I could have done a more accurate A/B test before writing this bug report.

Cheers.

3 Likes

Hi, just following up on this and if you’ve gotten a chance to get into the new docking beta and see if it resolves some of the issues?

1 Like

Hi,
I’ve tried the beta for a little bit, and I still get the issue where stacked widgets will often display the incorrect when stopping/starting. Same issue for some widgets randomly opening up.

I’ve been suffering from a new bug that is somewhat similar in nature.
Sometimes widgets get autodocked and do not have any form of header/footer to be able to drag them out of their docked location.

Here’s an example with bitwise andreas UI Previewr plugin

The only way to fix this is to stack another widget on top of it, triggering some kind of internal update that fixes the issue.

I’ve only seen this happen with plugin widgets and none of the native ones so far.