Broken SurfaceGUI

Bug Reports Engine Bugs
#1

I made this thread earlier. I think I found the issue so I am posting it here.

[strike]My Surface GUI (AbsoluteSize of 800x800) is not displaying GUI objects that have a AbsolutePosition of 618 or larger. [/strike] I can no longer replicate this.

j7rRUGf.png1153×755 411 KB

MV93QJC.png1188×765 411 KB

EDIT: [strike]The issue can be avoided by not putting GUIs under 617.[/strike] However, I just noticed that GUIs are popping above the screen… Wut?

BUT WAIT! THERE’S MORE! It appears that Frame Borders are drawn off of the part?

L21S0cx.png333×665 202 KB

VoUjCww.png491×515 251 KB

The example model is an attachment.

1 Like
#2

Yes, it’s a part of optimization for the GUIs. It doesn’t render GUIs that are not on the screen. A simplified example would be absolute position and size summed up together and checking if the stuff is within screen bounds. It’s a tad irritating at times, when you have a big frame with rotation and it doesn’t show up. It’s not really broken I think, just needs a little refining.

#3

But the GUI is on the screen… ? The GUI disappears when I play or play solo but appears in edit…

#4

Huh. I misread that 800x800 as 800x600. That’s odd, no clue what’s happening over there.

Also you’re talking about surfaceguis, not screenguis, just pointin’ that out.

#5

[quote] Huh. I misread that 800x800 as 800x600. That’s odd, no clue what’s happening over there.

Also you’re talking about surfaceguis, not screenguis, just pointin’ that out. [/quote]

Herp a dorp; I changed it :stuck_out_tongue:

#6

Calling all admins! Calling all admins! :uhhh:

#7

Without a proper repro case clearly demonstrating the problem, I can only assume that you’re most likely attempting to abuse SurfaceGUIs one way or another.
Also, there’s ‘canvasSize’ property you might find useful.

#8

[quote] Without a proper repro case clearly demonstrating the problem, I can only assume that you’re most likely attempting to abuse SurfaceGUIs one way or another.
Also, there’s ‘canvasSize’ property you might find useful. [/quote]

I am aware of the Canvas Size property. I included a model of my SurfaceGui.

#9

Forum attachments are broken, can you upload it somewhere else?
Or just post a link to uncopylocked place.

#10

[quote] Forum attachments are broken, can you upload it somewhere else?
Or just post a link to uncopylocked place. [/quote]

#11

So, ok, um… I see nothing wrong with the thing. Anything in particular that should I look at?
What’s the bug?

#12

[quote] GUIs are popping above the screen… Wut?

It appears that Frame Borders are drawn off of the part?

L21S0cx.png333×665 202 KB

VoUjCww.png491×515 251 KB

[/quote]

#13

Neither of those is a bug.
The UI elements move out of SG bounds because your script moves them out of bounds. The absence of clipping is even mentioned on the wiki page, together with a recommendation to enable it

Same with border frames, that are supposed to encompass the entire UI element without obscuring any part of it.

So the next time before acting like a ************, consider doing some preliminary research first.

1 Like
#14

Wow. I get that you might be upset but is that really necessary? Nick is just trying to help out. Chill, dude.

#15

Wow. I get that you might be upset but is that really necessary? Nick is just trying to help out. Chill, dude.[/quote]

Yeah no offense Max, but if he were trying to be an "attention w**re, he wouldn’t have explained his problem as well as he did.

#16

Well I apologize for wasting your time. It seems extremely valuable and I flat-out wasted it. I’ll try not to mess up so much again.

EDIT: I apologize for my initial sarcasm. However, I would’ve found it more professional if you would have told me that my ‘bugs’ were not actually bugs and told me to do more research next time. I do admit I jumped the gun (even though my first issue that I can no longer replicate was genuine). Also, I would appreciate not being called an attention w**re next time I mess up.

#17

I apologize for the wording of the offending message. That was not how we do things; this won’t happen again.

This forum is meant as a medium for professional discussion about Roblox platform; whether or not the users make mistakes does not justify such behavior.

I’ve moderated the original message but left the discussion in tact to not sweep the incident under the carpet.

#18

Sorry guys, this is not how we intend to represent ROBLOX. This forum has been an invaluable resource for me and many engineers at ROBLOX, and I hope this doesn’t discourage anyone from posting questions or bugs. You guys make ROBLOX what it is and we are here to support you.

#19

So will the issue here actually be addressed? :?

#20

They were in the moderated message. The ‘bugs’ I pointed out were not real issues. The SurfaceGUI does no clip descendants so any GUI with part of itself on the surface with render the rest of itself off of the surface. It’d be nice to a have a ClipDescendants setting on the SurfaceGUI itself but that discussion is for another subforum.

@Admins/Moderators/Roblox Peoples

Thanks for addressing and moderating the issue. I had no intention to stir up unrest or attention; I only wanted to point out what I thought were bugs.