This bug has been out for a while now, and it’s really annoying when working with SurfaceGuis for a neon effect.
Basically, here I have two parts, one with the size of <20, 20, 20>, and one with the size of <1, 1, 1>, with both edges perfectly aligning. On the smaller part, the offset is only noticeable when you zoom in close to it, but on the bigger part, it’s much more clear to see.
Same issue can be very clearly seen on the billboards at Ripull Minigames
Does it also get more pronounced the farther they are from the origin, or has that been fixed?
If you only want the glow effect, use BoxHandleAdornment, set the size of the adornment to the size of the face, and set the CFrame of the adornment to the CFrame of the face. The adornment isn’t affected by lighting, and it’s not offset from the part at all if you set the CFrame to the face’s CFrame. It’s also colored using Color3 so you have the same amount of customization you would with a SurfaceGui.
I can confirm this also.
That’s a feature.
That’s a feature.[/quote]
If it is really a feature, could it be removed? It is more hurtful then not.
Will you give a solemn vow not to use SurfaceGUIs far away from origin?
That… would technically require smaller or more compact maps. Since I use them in planes and such, I can’t really do that.
And other games like the Quarry can’t quite do that since you need to be at Y=5000 to be able to mine far down.
The problem is there is no cap to this rather annoying “feature:” there are a few places I visit where surface guis are a whole 2 studs away from the surface, which is really stupid.
I am wondering why it has to be a feature.
Is there any real reason why SurfaceGuis should be offset at all? It really makes things look ugly, especially when you have a long strip of a brick with a SurfaceGui on it.
[quote] I am wondering why it has to be a feature.
Is there any real reason why SurfaceGuis should be offset at all? It really makes things look ugly, especially when you have a long strip of a brick with a SurfaceGui on it. [/quote]
z fighting, float point’s in disguise.[size=1] I actually have no clue[/size]
I think the easiest way to fix this would be to have the offset be based on distance to the camera, and not the map origin. I’m not sure the extent it would effect performance, but it would solve this issue while not removing the feature. I don’t think anybody relies on this behavior so I dont think I tweak like this would hurt anybody (speaking more as myself than for a group).
If z-fighting with the part that it is on is an issue, I think the whole system needs to be remade.
Decals and Textures don’t z-fight with the brick they’re on, and this offset is either a really terrible feature or a straight-up bug that needs to be redone entirely.
