Layered Clothing - Changing Order Failure?

Help and Feedback Scripting Support
, ,
#1

I’m posting this here because I’m unsure if this is a bug or just a failure on my part.

I’m trying to remove the textures from a Layered Clothing jacket so the player can set the texture themselves, as well as change the WrapLayer.Order themselves. The only way I have found to make changing the texture work is put the SurfaceAppearance inside of the WrapLayer instance and change the MeshPart’s TextureID (I know, bootleg). This must be done because if you try to change the textures in SurfaceAppearance - Roblox spits out the following error: The current identity (2) cannot ColorMap (lacking permission 1). In this particular case I set the TextureID to nothing and the MeshPart to have a Pebble material + green color.

The problem is that when I do this, changing the WrapLayer.Order no longer works. You can see in the video that I’m wearing 2 of the same jacket. The 1st jacket is green/pebble with no SurfaceAppearance. I attempt to set the Order of the 2nd jacket to be higher than the 1st jacket but it won’t work. The green jacket is still on top.

So my question to anyone reading is this - is this a bug? Is there a way to change the texture of Layered Clothing to have no texture or an alternative texture without breaking the functionality of WrapLayer.Order? Any response is greatly appreciated!

#2

Since the WrapTarget documentation doesn’t include the Order property and since this is the first time I am seeing WrapTarget (hasn’t worked with it anytime earlier), but I quite understand Roblox studio, I will be mostly guessing.

The documentation does say, though, this at the top:

The WrapTarget object defines a target. A target is the 3D body with only
an outer surface, or an Outer Cage.

This target, often an Avatar, is what 3D accessories (using WrapLayer) will be
applied to, allowing multiple accessories items to naturally layer over the source
target.

My idea is then that the WrapTarget and the Order property is, as stated, only taking in account any other WrapTargets parented to the same source (MeshPart). You currently have 2 MeshParts and each of them has its own WrapTarget.

Since this is my first time see with the WrapTarget and similar stuff, I don’t know if this worked earlier. If you are certain it did work earlier, you should reach out to Roblox Studio development staff through Roblox Support, or you can create a post in #bug-reports:studio-bugs.

Hope this helps!

1 Like