Migrating Heads and Accessories to be MeshParts

[Mystifine]

This is a big update, I’m tired of particles surrounding the whole player head box rather than the circle. Thanks for this update.

[Dogutsune (Dogu)]

I want to clarify few things though.

1. There’s hats with scripts. This one for example uses SpecialMesh in it’s script to alter it’s own mesh.
   You might want to check some scripted hats, redo their scripts as well.
   Example: Rbadam's Smokestack Top Hat - Roblox

2. There’s some hats with VertexColor. That means MeshParts require Color3 property.
   Example: Brainfreeze - Roblox

Wouldn’t it break those hats?

[Dogutsune (Dogu)]

I believe attachment could fix the issue!
Just put particle inside of it. There might be no offset variety like for part though.

[bt5191 (btt)]

I’m excited for this change, this also means exploiters will in future, be unable to delete the meshes in their accessories which means plenty of exploits which do things like make blocks won’t work anymore.

[Dogutsune (Dogu)]

I did a fix to address this future change.
Was fun!

https://www.roblox.com/library/5646283851/Rbadams-Smokestack-Top-Hat-MeshPart-compatible

[formy2kids (Infernus)]

You’re right, an attachment would probably fix the issue there. As for the changing mesh issue, that would still require 2 meshparts, as you can’t change the MeshId of a meshpart in game for some reason still. And yes, we 100% need Color3 in meshparts, I have wanted this for so long.

Adjusting the Color3 of a MeshPart Texture

As a Roblox developer, it is currently too hard to alter the colour of a texture on a MeshPart, meaning a developer would have to create alternate textures just to differentiate a texture’s colour appearance. One way to tackle this would be to add similar Color3 properties to MeshParts’ textures, making it increasingly easier to modify meshes with ease on the Roblox engine. An example of this would be to add the Color3 property (similar to a decal or texture) on a MeshPart texture property: [i…

[Dogutsune (Dogu)]

Yeah, that’s why I did a hacky fix for said hat out of pure boredom.

Migrating Heads and Accessories to be MeshParts

I did a fix to address this future change. Was fun!

[RobieTheCat]

@Noble_Draconian

Is there any chance that package ‘heads’ will be converted from hat accessories to actual head meshes? E.g. the crimson claw package’s head is currently a hat accessory. Will it be converted to a head mesh?
If this were the case, already existing packages could make use of the upcoming “facial animations” feature.

@CodeWriter Dev. reached out, Can you answer?

[Maximum_ADHD]

I noticed in this week’s update that characterR15V4.rbxm was added with a MeshPart head, but there seems to be an issue with the normal mapping seams around the face.

I’m sure this is known about, but I just wanted to post it here in case it was overlooked.

[DeathLilian (Alyssa)]

Is that R15V4.rbxm available to obtain it? also are these head on dummy models from the plugins will be changed to be a MeshParts?

[CodeWriter]

This will be fixed once the new code is enabled.

[Clueless_Brick]

What’s the update on the migration of MeshParts?

[ShutzCh (Shutz)]

What’s also the update on the addition of texture coloring for meshparts? I feel like this is a needed addition considering Roblox is embracing meshparts more and more as time goes.

[IdontPlayz343 (FPS_Enjoyer)]

@Osyris

Assuming everything goes well, within the next couple of weeks for heads, and soon after that for accessories.

Any updates on issues that are causing the massive delay?

[Osyris]

We’ve decided to ship MeshPart heads and accessories at the same time instead of as two separate releases. Should reduce complexity. Accessories took much longer because we had to convert the entire existing catalog of accessories (including UGC uploads).

[builderboy256]

This update seems to break acessories still using the deprecated ‘Hat’ instance

for example this: Ceremonial Guard of the Archduke of the Federation - Roblox now refuses to load in game

[Maxwell_Edison]

This feels like a weird setting to be put in Workspace’s properties. Feels like it should be in StarterPlayer properties or something, since it’s something that really only directly affects which type loads in when players join. Really nothing to do with the general game/workspace

[acreol]

It breaks this accessory, maybe because the SpecialMesh is called “SpecialMesh” not “Mesh”

[The_Potato97 (Potato)]

Equipped transparent MeshParts seem to be causing Z-Index issues

Unequipped MeshPart on the right

Equipped MeshPart on the left

Found this issue thanks to @Mr_Purrsalot 's Rainbow Wings

Repro Place

Repro zindex issue meshpart