Is it absolutely necessary to parent SurfaceGuis and BillboardGuis to the PlayerGui?

Help and Feedback Art Design Support
1

:wave:

I was wondering if there was ever any circumstances where SurfaceGuis and BillboardGuis shouldn’t be parented to the PlayerGui? I know it is standard practice to parent them to the PlayerGui and then adorn them to the part but I am starting to have problems with navigating the explorer.

I know that if I parent the SurfaceGuis and BillboardGuis to the instance they should appear on, and that it removes the functionality of them but they still look correct, but are there ever circumstances that it doesn’t render properly? For example, if I wanted to make a leaderboard that refreshes every so often, it can be scrolled but not interacted with. Is this a case where I could avoid parenting it to the ScreenGui without any risk of rendering issues?

2

I have my leaderboards directly on the Instance they’re from. I haven’t been having any issues with rendering, not sure what you mean, I thought it was standard because you can tween and stuff without it skipping because :sparkles: replication :sparkles: .

Like I said, I haven’t been having any major issues with the exact thing you just said, so yeah.

I know that from far away I do have some rendering artifacts or something? But it’s from far away enough that it wouldn’t matter, so? But I’m pretty sure that’s a normal issue anyway even with the ones inside PlayerGui.

1 Like
3

It’s never necessary to parent them to the PlayerGui, I personally don’t do that.

The only thing that you should parent to PlayerGui is ScreenGuis but Roblox will move them to that location automatically when your game loads up.

1 Like