Unable to open model in explorer

[MisterObvious]

This was reported back in Dec 14 which was why I was curious.
Now I understand, thank you for addressing that.

[Lilly_S]

@MisterObvious

This was reported back in Dec 14 which was why I was curious.Now I understand, thank you for addressing that.

Dec 14 - Dec 18 was Hack Week and then most of the staff took off the next week.

[Scottifly]

I’ve had this for a bit as well. Selecting the arrow deletes it.
All I’ve done is select the item the arrow was in and right click to Select Children. Everything goes back to normal then.

[J_J]

@Scottifly

All I’ve done is select the item the arrow was in and right click to Select Children. Everything goes back to normal then

@LMADev

Another fix that doesn’t need Copy Paste is right clicking and choosing Select All Children.

Got it covered. You don’t even need to attempt to select the arrow.

[Scottifly]

Ah, sorry LMADev, didn’t see your reply there.

[Silent137]

Hey there everyone! Sorry this one took so long to reply to, we were all missing for awhile. We’ll investigate this and see what we can do!

Related topic: Explorer not showing all the children in an instance - #7 by sleitnick

[Partixel]

@Silent137

Hey there everyone! Sorry this one took so long to reply to, we were all missing for awhile. We’ll investigate this and see what we can do!

Thanks! This bug is a real pain, it’ll be great to be rid of it!

[twberg]

This should be fixed now.

[buildthomas]

Yep, thanks!

[EchoReaper]

@twberg Not entirely. More info here, but the CoreGui’s children can’t be expanded in Studio. After almost three months now of experiencing the bug, this is what my command bar tries to autocomplete with when I type in “fo”

I’ve been using that so frequently that just typing in “for” brings it up even though I’ve used “for” in lots of other cases.

I can right click > select children and it’ll select 21 items in the CoreGui, but I can’t actually expand the CoreGui to see its contents.

“Eh why do you need to see the contents of the CoreGui?”

Contents of CoreGui not shown in studio

• Take a quick glance at how other plugins’ GUIs are organized
• Get a copy of your own plugin’s GUI without having to insert your plugin as a model
• Make quick modifications to GUI in the CoreGui on the fly to see how it looks
• Visually check certain values in your GUIs to make sure they’re correct instead of printing them out
• Delete GUIs and 3D adornments that weren’t properly deleted by plugins without having to reopen the place (e.g. delete the leftover hover selection box left over by the animation editor)

[Silent137]

Changes to the XML file are not officially supported.

[EchoReaper]

@Silent137

Changes to the XML file are not officially supported

The importance isn’t that it’s happening to the CoreGui which I force-enabled through the reflectionmetadata.xml – that’s just where it happened to show itself to me. The significance is that the bug isn’t truly fixed. It’s plausible that down the road the bug may present itself to others in places other than the CoreGui that weren’t force-enabled through the reflectionmetadata.xml, so it’d be ill-advised to let it linger in Studio forever. It’s priority certainly isn’t high because as of current it’s only been spotted happening to the CoreGui, but it shouldn’t be assumed that it’ll remain exclusive to that.