ArmorAddOn Bug, doesn't save texture for female 1st person

[Paulimposteur]

I've been spending a long few days making my mod, and getting everything dandy. But All of a sudden it is as though everything broke down.

 

What I did was create new clothing but without NIFs, simple texture addOns using ArmorAddOn, which was relatively simple once I understood the controls/concept of CK.

 

However, I now have a real odd problem out of no where, one that I did not have recently. The mod suddenly won't save textures for female characters on their first person model. It also removed all of my textures that previously worked on those very same first person models. The odd part though, is that this bug does not affect the males AT ALL. So has anyone seen this bug? And if so, how would I got about fixing this so 1st person can be seen with the correct textures.

 

I'm not sure if this is only a bug with CK or something more. But it could be possible I'm doing something wrong I suppose. I tried re-applying all the textures to the first person bodies again. But after saving, if I start the game or reload the ESP in CK, it's as though the information never saved.

 

Also I have removed the original esp out of the DATA folder, and resaved in the ESP to be assured that it was saving. It produced a new file in the DATA folder, so it is saving, but the information on the changes to first person, seem to not be.

 

Edit; I also remade a completely brand new ESP and tried making ArmorAddOns on the new file, and it still failed to stay attached to the female models.

 

I also reinstalled Skyrim and the CK completely, this did not rectify the situation.

Edited April 24, 2013 by Paulimposteur

[IsharaMeradin]

I'm guessing that you created a texture set and are applying that texture set to the node entries on the assigned nif in the armor addon form. My experience when working with armor addon forms is that the nif file needs to be present in the data folder. You may want to try pulling the nif out of the BSA file and see what happens when you save the plugin. Shouldn't need the nif in the data folder to play the game, but when making the plugin you probably do.

 

It's just a guess, but worth a shot if you've not tried it.

[Paulimposteur]

I am currently using a body vanilla outfits mod that provides all the nifs. However I never actually changed the nif path at all. Also if this were the case, the Male 1st/3rd person and female 3rd person nifs wouldn't recieve the texture changes. However, they all do. The only one that does not change, is the first person female texture.

 

So if I change it it shows the changes. But after saving/reloading inside ArmorAddOn the path to the texture then appears blank again.

[0Prime0]

Interesting. I just noticed the same problem today with my mod. At first I thought I had just missed one or two, but then I found they all had beeen set to the default for the robe model. And as you say I can change it, even close and reopen the armor addon and the change, but saving does not make it stick.

 

You are not alone!

[Paulimposteur]

Yes, I'd like to know a solution to this.

 

Question, did you get the CK from steam as well?

Edited April 25, 2013 by Paulimposteur

[0Prime0]

Yes I did.

One thing that works is to delete the female first person model in the addon, so that the entry is black. Then it either picks up the make one or the 3rd person model. Not sure which.

 

Also, have you found that some inventory items such as robes don't show the texture set on the model, but just uses the default texture?

Edited April 26, 2013 by 0Prime0

[Paulimposteur]

The texture issue only effects the first person body, as for the Mesh I need to use the default path for the mesh, but I will try your method.

[Paulimposteur]

I'm shamelessly bumping this.

[mjharper]

Having exactly the same problem. The really weird thing is that the alternative 1st person female texture info shows up in TES5edit, apparently correctly. But the field is blank in the CK.

 

I will confirm that just deleting the whole Female 1st Person model solved the problem--but there's got to be a better solution than that, hasn't there?