If you want to make them game-ready, you can only do it with the bone-to-empty trick or weight paint. My approach is generally to select the whole rigid object, and then a vertex of the surface I want it to be pinned to (making sure that the surface vertex is selected and active) and then copy all the vertex weights. Unfortunately, it is not as accurate as the triangle approach as it only copies the weights of a single vertex and clips, but is a very decent approach in most cases. The good thing with the copy weights method is that it follows rotation. For the three vertices is generally a good practice to select them a bit further apart so there is less chance to clip. Always a joy to see your content, thanks!
"Copy all the vertex weights to object" working excellent, thank you! But the most important thing for me is that it works in game engines when exporting to FBX. All other ways for me do not work because my character has no animation and without baking animation "parent to vertex" and "constraints" are not exported to FBX. "Copy all the vertex weights to object" is the only way (apart from weight painting) to rig additional objects on the character (like a knife on the belt) so that after exporting to FBX it would work in game engines? I want to rig additional objects on the character so that the rig works equally well both in blender and in Unity, so that when loading the character in Unity I can easily set the script with physics on the desired objects.
That's incredible. Now days, I'm wondering how to create a Rivet in Blender because Maya has this function in constraint menu. However, I couldn't find video like this. This video is so helpful. Thank you so much!
Big thanks for the tutor, it's really useful! Another thing is bothering me and I don't know where to find a solution. Let's say I want to reparent this knife to the hand during an animation. Or even lose it (unparent at all). Is it possible with rigify? M.b. you already have such vid? Thanks for all you are doing, it's really invaluable stuff!
Nooooo! 😲There is a much cleaner simpler way to do this! You can avoid separate objects, vertex parenting, the Child Of constraint, etc. The secret is the Armature Contstraint! 1. Create a prop bone (called "Knife Bone") 2. Add an Armature Constraint to Knife Bone. 3. Find the vertex near the desired pivot point of the knife. Look at its vertex weights. We'll pretend it's 0.25 pelvis and 0.75 thigh. 4. In the Armature contstraint add all weighted bones and adjust the influence of each (0.25 pelvis, 0.75 thigh). 5. Weight the knife mesh vertices to the Knife Bone. That's it! 6. You should not animate this the Knife Bone. If you want to animate it, create a new Control Bone in the same place and set the original bone as its parent. You can freely move the Control Bone. This method basically does the same thing as a vertex parent, except it's all contained in the same rig and same mesh. This method should replace this entire video! Sorry 😅
The Armature Contraint is designed to make an entire bone act as if's it's being deformed with the mesh. So any time you want a bone to move the same way that deformed verts do, use this constraint!
THIS! Is a much better solution. No need to avoid any possibly weird dependancy loops. I kind of just want to make a button which can copy the weights from a selected vertex over the constrain :D
When using the child of constraint I have found that it is important to have the object origin and the object at the world origin and then add the child of constraint and it will move to where you expect the object to be and it won't have funny movement behavior like you have seen. The child of is taking the offset from the world origin and adding that into the movement.
I am learning everything with your video...i really appreciate you. I have an important question: how i can use mixamo or other armature animation on blender Human armature? I know the problems are about the different name and characteristics of the bones...but there's is a way to solve these problems? Thanks for everything
I always enjoy your content. If the rivet-to-bone approach (around 10:12) isn't a dependency loop, could it be related to evaluation order? Especially since it "catches up" to where it ought to be once the scene/viewport is evaluated (such as nudging the view or advancing a frame).
It's a dependency loop because there are circular references, even if the influence is set to zero, still causes the issue. Whenever you see bones "catching up", it means the rig needs to be fixed. You can run into issues if you leave things broken
Software loops through instructions that make updates to the data and display the results. The software has to dictate what to update at any given moment. I've heard of problems in other software where the code to display a result isn't triggered until some scene update ("evaluation") like changing the current frame or beginning to tumble the viewport. A complete guess on my part, though. No expert here!
Sir you can move bone with copy transform with some constraint setting and there is shown mix and there you can choose after original full and you can move constraint bone individually...
@@AlexiosLairThis definitely exports to game engines 😅 When you export animation, you can choose to export only deform bones. You can also give deform bones their own hierarchy. Blender will bake the transformations of all bones, and doesn't matter how they get there, Blender handles all that
Baked animation can be exported to unreal but the constraint itself can't. Check out my game-ready rigs series to learn what can be exported and what can't ru-vid.com/group/PLdcL5aF8ZcJvCyqWeCBYVGKbQgrQngen3
