SurfaceGuis appearing absurdly far away from their surface?

Bug Reports Engine Bugs
#1

This wasn’t happening until recently. That gui is an entire stud off its surface. Anyone else seeing this?

#2

Does the block have any type of meshes in them? Because I don’t get this issue with standard bricks:

#3

Nope, even brand new parts are doing it.

#4

Does the problem happen in other games (i.e. RobloxPlayer) that have SurfaceGuis in them? It could be your end with this bug.

#5

That’s why I asked if anyone else was having this issue. It could just be a setting in one my control panels that’s doing this, but if other people are seeing it then it’s probably roblox.

#6

Confirmed in DR2. Our Capes use a Letter, that letter is like one stud anyway from there surface and there is nothing that I can do to actually fix it…

#7

SurfaceGuis appear to be adhering to their respective surfaces as they should for me. Both new and old.

Edit: since it’s possible it’s OS specific I’m on Windows 7

#8

Confirmed on Windows 8.1

#9

I’m on 8.1 too. Also using a nvidia GPU.

#10

Windows XP, happening at like 0.05 studs distance

#11

That should only happen if you put SG on a part that’s very far away from origin. I added this particular quick hack about a month ago to prevent Z-fighting.

#12

It’s like this in The Quarry Leaderboards, tried to move the initial parts that parented the SurfaceGui to ‘fit’ the GUI with the Leaderboard Frame, however it prevented use of the ScrollingFrame.

#13

The status of the bug:

mlBa0CH.png1278×660

#14

in my example, it was a newly created part, so it should have been at exact origin, right? and yet it’s still visibly away from the front, howabout instead of this hack, you just render the guis in order, so they don’t fight over the Z-space, or make a separate z buffer modifier for when the guis are checking depth between each other

#15

it seems that the distance away from faces scales with the overall dimensions of the place and not the actual distance from the origin. I’m working on a repro or two.

#16

Removing the -500 lower part limit would solve this problem for you.
All of the good floating point precision is near 0, 0, 0, and players need to go down

#17

Okay, I just got this bug too. Any admins on this?