Empty model showing in explorer even though the model has children

Bug Reports Studio Bugs
#1

Reproduction Steps
The following video illustrates how to replicate this bug.

Steps:

  1. Insert multiple parts
  2. Group a couple of the parts.
  3. Group the model with a few extra parts.
  4. Repeat step 3 a few times so you have a hierarchy that is a few levels deep.
  5. Drag the parts into the deepest model of the new hierarchy.
  6. Ungroup the top-level model.

The hierarchy should now show a model with another empty model inside. Selecting any of the parts in the workspace will not update the hierarchy either, so these objects can no longer be found in the explorer.

Expected Behavior
When ungrouping the top-level model, the hierarchy should correctly display a model that has children instead of a model that has no children.

Actual Behavior
What actually happens is that the hierarchy shows a model with no children, even though it does have children.

Workaround
The work-around would be to ungroup the top-level model and regroup it.

Issue Area: Studio
Issue Type: Other
Impact: Moderate
Frequency: Constantly
Date First Experienced: 2021-08-05 00:08:00 (+02:00)
Date Last Experienced: 2021-08-05 00:08:00 (+02:00)

7 Likes
#2

I’ve been experiencing this past bug for over a year now, I’m not sure if it’s the explorer or studio in general. For me, I just close out of studio then re-open it and it’s fine again.

3 Likes
#3

I normally cut and paste the model

#4

This started happening to me within the last month or so - only in our large map with a lot of stuff going on, but it’s really annoying to have dozens of assets selected to edit something in the lower children, and have them not be seen, resulting in me guessing that I have everything selected.

Ungrouping isn’t the work around I use because I’m working with a lot of assets simultaneously, and that’d get messy quick. Once I deselect all the models, they usually populate with their usual children again.

2 Likes
#5

Hey, sorry for the late response, I am unable to reproduce this issue on my end, can you confirm this is resolved on your side aswell?

1 Like
#6

I am able to recreate the issue on the latest build on my end as well

1 Like
#7

I am still experiencing this issue on my end as well. I have asked around and it seems like some users are able to reproduce it through the video I posted and other users are not. I will try to find a second method to reproduce this issue that will hopefully have a higher success rate.