The easiest way to do this is to make your original skeleton rig inside Blender, and then export it to the other tools. You can standardize your work on a Blender-compatible skeleton with all bones pointing in +Y direction. I know of two ways to deal with this presently. However, the skeleton is no longer the same as the one in the FBX file, so exported animations will not match up with that original skeleton in UE4. If you use Blender FBX Import's "Automatic Bone Orientation", it may fixup each bone individually, and they may look fine in Blender.
For example, in the UE4 mannequin, one leg's bones should point in +X while the other should point in -X. If you turn on the bone-axis display in Blender, and think about which axis the bone should be in your model, you'll see that in your skeleton it's different for each bone. There is no way for Blender to represent a bone-orientation per-bone, so there is no way to correctly import/export an FBX with unique bone orientations per bone. The reason the bones point in weird directions in your screenshot is that Blender only supports bones pointing in a uniform (+Y) orientation, while FBX allows each bone to point in a unique orientation. Anything would be awesome, thanks for taking time to even consider the post.There is no support for importing IK setups from FBX. Because this is a Daz proprietary model (victoria 7) I am not allowed to distribute the blend file.Īny suggestions or ideas would be welcome or even references, I've scoured the interwebs but I really don't have any idea of what I should even look into to find a solution or even the cause for this. I really tried to make this as clear as possible, if you want more information I can give you pictures. This unique node group works in the original torso.004 material as well, just not when I disable Torso.004 Material and try to use the Anna_Body Material instead. I even made sure to make a copy of the image as unique so there wouldn't be any cross over conflicts.
In this picture you can see into Anna_Body Material group. Even though in the nodes, they reference the same images as the original materials do.Īs above, you can see my new Anna_Body material doesn't have any of the kd.91 texture files, even though I do in fact reference them in the node group I made and put into the custom Anna_Body material. I find it peculiar that it doesn't seem to have the same data children as the other materials. The only difference is that I created a new material to house those same nodes that worked before.Īnna_Body is the new body material I wanted to use so it could house my different node groups into a combined single material for the mesh body. Independent of my newly created material I will show you next.Īs you can see, the newly created material, is using the same exact nodes from the torso.004 material imported from DAZ. The above image shows my Torso.004 Material working, even though I made the material a unique copy. The bikini strap example was used with two imported materials from DAZ, the only materials that seem to work. The logic is working.īut if I copy and paste that same logic into another material, even if it was originally generated like the other materials. As long as I use the original generated material slot directly imported from DAZ, my custom node group works. The major problem seems to stem from the objects inability to deviate from the materials directly imported from DAZ, for a reason that I don't know. Effectively only allowing me to use certain materials, excluding me from the new ones I created. My thought was that there was some kind of UV or extra data that I wasn't seeing, that somehow connected to the materials, making them specific to the nodes.
In this picture we can see the data pane as well. In the above picture you can see how I put both the Node group along with the parent material into a mixed shader. I have copied the nodes into the Bikini Bra material from the bikini strap material. The above image is a picture of me disconnecting the Bikini strap material, because its not necessary. When I put it into another material and use the necessary UV Input node and connect it to that materials output node, I get a black mesh error. The problem occurs when I try and take exact node groups of a material, and plug them into another material in order to effectively combine them. Im trying to simplify the materials and I'm trying to work my way to only a few materials for the model. I'm currently trying to materialize a DAZ Imported OBJ Character and the process was difficult, but I'm making good progress in the translation.
0 kommentar(er)
