My game uses deformable meshes and everything seems to be working really well - except for when I try to rescale a MeshPart with bones in it. These MeshParts are constantly rescaled as part of the game’s primary gameplay and seeing as there’s no scaling support for bones yet, this is the only way for people to resize deformable meshes. The MeshPart usually re-appears less than a second after you change the size of the MeshPart, but it’s very detracting in our game. The behavior occurs online and in studio on most peoples’ devices that have tested the game.
I have attached a minimized repro file with a single deformable MeshPart and configurable scale NumberValue in ServerScriptService so you can see the occasional flickering behavior. Change it a few times and you’ll see the mesh disappear for a brief second and reappear. The flicker time does not appear to scale with the number of meshes in the game.
Can confirm. I’ve been working on this Project with OP and have also noticed that mesh deformation will flicker if the color of the object or transparency is modified while said object is moving. Would love for this to be addressed so that we can continue to push and innovate with mesh deformation!
If it’s an issue of processing transformation changes on the mesh, would it be possible to keep the current geometry visible until the new geometry is calculated?
Here is a new repro file that constantly rescales the mesh part when run. It seems like the flicker happens almost every 5 seconds exactly. I’ve also attached a gif of what it looks like:
You can see it at the very beginning, 5.5 seconds, and 10.5 seconds.
Let me know if this issue is not reproducible or if you need any more information from me.
I have also been seeing this issue. I am seeing skinned meshes flicker whenever I modify the position of the bones. I have only been able to see this happen on the windows 10 version of roblox. This can ruin the look of meshes if it constantly flickers. Would love to see a fix soon.
I’ve also had this same issue for a while now. I’ve been unable to set properties such as transparency and color to a deformed mesh without flickering.
This makes for a very poor gameplay experience for users and results in a major loss in opportunity for mesh deformation.
Same issue here. Trying to update a decal welded and parented to the head/character, and this makes the mesh deformation parts on the character flicker
Sorry, my mistake, there is no easy way for you to enable flags. We have a fix for the skinned MeshPart update flickering issue that we will be releasing sometime in the next few weeks.
One thing to know, even when the flickering goes away, updating skinned MeshParts like this will be somewhat expensive and may make the game laggy if it happens too much. In the future we may optimize it further, but for now you will have to keep an eye on it.
I am moving around bones inside a skinned mesh, which works fine, but then there are these split frames where suddenly the bones lose all effect and the mesh plane becomes completely flat.
I haven’t actually gotten any of these issues for my own ocean. Do you update WorldPosition? I do that and receive no issues. Though it could also be because I have LoD and culling to only update a few bones, which can impact flickering.
I update worldposition, yeah. My bone count is actually quite low, and I cframe the ocean around to follow the player. Is it possible that having a 2048 stud ocean is the problem?
From my experience, there’s only a very select few properties on the MeshPart you can change without it triggering the flicker. Changing the CFrame of the parts has definitely caused it for me.
Skinned MeshParts flickering to the bind pose is a known issue that has been fixed in our internal codebase, but not released to production yet. The fix is part of a larger update that we are still working on, and we can’t release it until the entire update is stable and production ready. Rest assured this is one of our top priorities, thanks for your patience!