Need help with Creation Kit body mesh addon!!

[nakrulz]

Creation kit experts, please help!

 

So I am creating some customized armor on skyrim which uses a personalized body mesh created from CBBE body slide tool. Then I would create an armor to fit that body mesh. It would make sense in order to minimize the file size you seperate the body and the armor into two different mesh (hence the same body mesh doesnt need to be included into every single armor mesh I create). I just need to add the armor mesh and body mesh into ArmorAddons in creation kit, then include both Addons into the Armor.

 

This is where my frustration begins...the body mesh addon which is loaded from my customized location (eg. custom/femalebodyedit_1.nif) was added in creation kit.

 

The creation kit will normally auto detect the femalebodyedit_0.nif within the same folder and use it to morph between weights.

However in the game it shows the body constantly at _1 and does not load the _0 even when my character weight is at 0 (hence creating gap between neck, arms and leg).

 

Then I went ahead and changed the custom body ArmorAddon to the default vanilla ArmorAddon (NakedTorso) at location (Actors\Character\Character Assets\Femalebody_1.nif) and it morphed perfectly between _0 and _1!!!

 

I then modified the same vanilla ArmorAddon and switched the location of the .nif to (custom/femalebodyedit_1.nif) and it still doesn't detect the _0 of the nif.

 

Am I doing something incorrect here?? 

The nif femalebodyedit_1.nif and Femalebody_1.nif is the exact same .nifs. Only the name and the file location are changed.

[Shaydow]

First off, I would always recommend including the body as part of the .nif as NOT including it causes a LOT more problems. If you include it, anyone WITHOUT your specific body mod can still use it, you don't have to worry about clipping errors and CTD's, just a lot of problems solved. I know you think it makes sense to NOT include the body in the armor .nif, but it makes more sense for you TO include it in it.

 

Second, are you 100% SURE that your _0 and _1 are NOT the exact same? Double check.

 

ASIDE : You can even have armor types that use different body set textures and and still be fully compatible. What I mean is, say you use a CBBE body as a default and I say " here is a UNP armor ". I can still make that armor work for you, and all the textures work correctly, you just have to assign a specific texture set to that armor in the creation kit and it will work for EVERYONE, regardless of what body mod \ skin mod they use. In some of my mods, I have both CBBE AND UNP armor types for the user. I simply make the texture location easy for them to find and replace at will, this way, while they still have to deal with the armor being UNP even if they use CBBE, they can replace the body texture of said UNP armor in the mod with whatever UNP body texture they like.

[nakrulz]

Thanks for the reply. Yup I checked a few times, the two meshes are different but share the same vertices etc. and it was generated by the body slide tool so there shouldn't be any problems with the .nif.

 

I just thought it would be a good idea to save yourself the hassle of having to blend two different mesh files _0 and _1 for the same armor using the same body (except for the little differences the _1 makes for wider neck, arms and legs). Thought it would be a good idea to attach the armor (same mesh for _0 and _1) to the different bodies using armor addon.

 

And I got the texture part where you can modify using creation kit to use different textures on the same .nif. Thanks.

 

[nakrulz]

Ok, mystery is solved. I managed to find the problem in http://forums.nexusmods.com/index.php?/topic/621992-weight-slider-not-working/ where people are experiencing the same problem.

 

Basically creation kit is buggy and does not detect the _0 nif.

To fix it, you will have to remove the current nif from your addon, save the esp, reload the esp, then reload the nif _1 back to the addon then save. Tested it in game and it worked for me! So anyone who is having similar issues that the game is not detecting your _0 .nif, try the steps above.