I prefer to save under a new file name again. Default settings are fine, don't worry about the Collision options, there is none. Remember above where we changed the User Version of the nif to equal Fallout? This is why. The only difference here is to export the mesh as a Fallout mesh, not an Oblivion mesh. When you're finished editing the mesh to your liking, export as nif like you normally would.
The only important step to point out here is to apply a material and texture to the mesh. If you receive an error, double-check you've done everything in Step 1.Īs this is NOT a Blender tutorial I am not going into detail of what to do once you're there. Import as nif into Blender like you would any other mesh. So in this example, I've saved it as skyhandcart01.nif.
I like to prefix my "Skyrim ready" meshes with Sky so I know immediately what it is. When done, we have left a very bare bones mesh. We've removed all those lines because, as mentioned above, the nifscripts to import into Blender currently does not know what those blocks are and will throw errors. The mesh will lose all it's texturing but don't worry. Right-click on the line BSLightingShaderProperty, go to Block > Remove Branch to delete the entire block. In the Block List, right-click on the line bhkCollisionObject, go to Block > Remove Branch to delete the entire block.Įxpand the NiTriShape block. In the Block List, right-click on the line BSXFlags, go to Block > Remove to delete it. What we're doing here is changing the values from a Skyrim mesh to a Fallout mesh so Blender will recognize it. In the Block Details, expand the NiHeader arrow. Again I'm using clutter\carts\handcart01.nif as an example. Working with armor/clothing is a whole different ballgame and can be found here. This tutorial is specific to static meshes. There are other ways to import/export meshes, this is my preferred method. The nifscripts for the latest 2.6x are not yet up to par and would require extra workarounds.ģ. For that same reason, Blender v2.49b is used.
We need to be patient, and use workarounds such as this for now.Ģ. This is understandable, it takes a team of volunteer developers time and effort to get there. This tutorial is necessary due to the Niftools nifscripts not being current and up to date with Skryim information.
0 kommentar(er)
