Bug regarding SpecialMesh's VertexColor Property

[OceanTubez (GK_OceanTubez)]

I was recently adding an update to my game when I think I may have stumbled upon a bug. SpecialMeshes with a Texture (property) don’t seem to get affected by VertexColor once inside a tool.

PC Info: Windows 10, 21H2
Date First Experienced: July 22, 2023
Date Last Experienced: July 25, 2023

Reproduction Steps:

1. Open Roblox Studio and add a Tool
2. Inside the tool, make a new Part called “Handle” with ForceField as its material.
3. Insert a new SpecialMesh inside the “Handle” part with any MeshId and TextureId of your choice.
4. Change the VertexColor property to anything different than (0, 0, 0)
5. Upon Using the Tool in the experience, the VertexColor is not changed.

Video of the issue (too big, had to post it on youtube):

SpecialMesh VertexColor Property Issue

Expected Behavior: The Mesh’s VertexColor Property should change the color of the Mesh, regardless of whether it is in Studio or In-Experience.
Actual Behavior: The Mesh’s VertexColor Property only changes the color of the Mesh inside Studio, not in-experience.

[Judgy_Oreo (phoenixwhitefire2000)]

@OceanTubez

SpecialMeshes with a Texture (property) don’t seem to get affected by VertexColor once inside a tool.

This is actually a bug with Humanoids, not Tools (as shown by how it works fine when it’s outside of a player character and in the Workspace in Edit Mode).

It has already been reported here:

VertexColor not working when a Descendant of a Character

Reproduction Steps This occurs on any system. Make a part with a SpecialMesh inside of it. Set the texture and mesh to anything. Set the “VertexColor” of the mesh to 2,2,2 or anything else that would alter the appearance of the texture. Parent the Part into the character. Or… use this place file which does it for you tryitout.rbxl (41.8 KB) Expected Behavior I expect that the VertexColor displays the same unconditionally. Actual Behavior It does not, as shown in the video below. …

You could add to the report with how it interrupts development so that it gets higher priority.

[OceanTubez (GK_OceanTubez)]

Ah. Thanks for the info. I initially thought this was a Roblox rendering issue as in workspace, it rendered fine but in game it just… well became not working.

Also, by the way I have found a fix. Albeit annoying, it does cope.

(This is taken from my own post that I made in the topic @Judgy_Oreo provided)

@OceanTubez

For the time being… I’m coping by changing the ‘emissive’ values to percentages of the ratio I decided on. Basically, one of my textures uses (1.5, 1, 2), I can instead use (0.75, 0.5, 1) or essentially halving it to keep it inside the (1, 1, 1) - (0, 0, 0) Color3 weird setup.

[thirdtakeonit]

Thanks for the report! Just to confirm, we have a ticket for this in our internal database.