Is there a reason for why SurfaceAppearance properties cannot be modified in-game? And why can SurfaceAppearance properly detect color behind transparent textures whilst MeshPart.TextureID’s can’t?
Let me set an example of my issue:
Here is a blood decal with a transparent background, on a flat brick:
In the image below, the left part of the roblox limb is using a SurfaceAppearance property with that same blood decal applied to the colormap, while the right part is using MeshPart.TextureID with the blood decal’s ID.
Both are using the same color. The left part is how it SHOULD look (but can’t use this because you can’t change ColorMaps ingame to apply, lets say, the current player’s shirt), yet for some reason MeshPart.TextureID won’t show the part’s color behind the transparent texture. It’s blocked me off from being able to add a couple of features (like custom liveries people can put on their UV maps with the car’s color underneath).
Here’s another example for another post I’ve made, not sure if this can describe it better or worse for the staff/other developers MeshPart TextureID doesn't support transparent textures?
With that in mind, I’d like to know whether if you guys will fix MeshPart.TextureID’s transparency, and/or explain why SurfaceAppearance properties cannot be run in-game.
Please just unlock ColorMaps ingame for SurfaceAppearance I need them so bad 