Page MenuHome

Armature not deforming meshes in Windows 10 - Blender 2.93
Closed, ArchivedPublic

Description

System Information
Operating system: Windwos 10 Home
Graphics card: AMD RX VEGA 56 8GB

Blender Version
Version 2.93.5

The Armature is not deforming meshes.

Exact steps for others to reproduce the error
First - I've added an armature and extruded 2 more bones.
Second - I've added a cilinder mesh.
Third - I've parented the mesh with the armature deform automatic weight.
Four - Its worked but was horrible because I didnt subdivided it.
Five - I've turn back some steps with ctrl Z and subdivided the cilinder, than the bug appear: the parent armature was not working animore. I've used the ctrl P, and nothing in the menu for armature deforming. Than I selected the object menu parent armature deform and it was there. I've activated it. But the pose mode has disappeared. I've only selected the armature and the pose mode was back. In the pose mode only the bones was moving, The mesh that was parented was not deforming and doing anything.

Help.

Event Timeline

It seems that the version 2.92.0 is working better in this case than 2.93.5. I've got this working in a previous version. But It only works for the first time. Its like working only when you want to finalize the project, because if you use control Z to reverse the steps it bugs again. The Blender aplication stop working with armature deforming when the bugs happens. I've got to reinstall or maybe to start a new project to work again. Its a bug. It works once and than stops when I try to change something and correct a mesh. Please someone check it. I don't know if it is the operational system or a virus or a bug.

Omar Emara (OmarSquircleArt) changed the task status from Needs Triage to Needs Information from User.Mar 23 2022, 8:35 AM

Your description seems to be a confusion about the active object. The active object (Last object in selection order) has to be the armature, not the mesh. The same goes for the pose model issue.
Can you try this again noting the above and check if it works correctly?

I will assume the issue is as I described above, which is not really a bug. If it is not the case, we can look into this further.