EditableMeshes that have vertices with non 1 alphas (non 0 transparency), are either not transparent at all (when the linked MeshPart’s transparency is <= 0.01), or have their faces layered incorrectly, and thus certain faces get rendered on top, even though they aren’t supposed to (when the linked MeshPart’s transparency is > 0.01).
Here is a video of it happening: Watch Desktop 2025.08.10 - 17.07.22.01 | Streamable
Replicating this issue is extremely simple, make an editable mesh with 2 unconnected faces (no shared vertices), set the vertex alphas to something below 1, link the EditableMesh to a MeshPart. Then set the MeshPart’s transparency to 0, which will result in the mesh being solid, and then set the MeshPart’s transparency to 0.02, which will result in the layering issue.
4 Likes
Hey it is not a bug but by design unfortunately 
. This behavior is consistent with importing a mesh with transparent vertices. I understand it is annoying, but we have to keep it backward compatible and consistent over the platform.
1 Like
Thank you for the response, is it possible to work around this somehow?
1 Like
I managed to find a workaround for my use case, I just separated the fully opaque and the transparent editable mesh, making this issue a lot less prominent.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.