Problem with importing .nif to Blender

[hauntedpassion]

so, i'm a total noob and i'm rather untalented i making new models. However, instead of constanly requesting something i wanted to try if i can at least convert some CBBE armors to UNP. This way i could give something back to the community.

I wanted to start with the Tera Castanic F H02 Armor.

 

I first followed this tutorial step by step on how to install Blender and all the required tools: http://wiki.tesnexus.com/index.php/Installation_of_Blender

 

Then i followed this tutorial on how to convert armour to another body (i firgured if you can port oblivion armors to skyrim with that method, changing cbbe to unp should be possible too):

http://wiki.tesnexus.com/index.php/Converting_an_armour_to_another_body_for_Skyrim

 

Everything works until the point where i'm supposed to import the armor into Blender. I followed all the steps mentioned in Nifskope, i checked that twice.

 

When i'm importing the cuirass into Blender, i get a phyton error - this is the console info:

 

 

 

Traceback (most recent call last):

File "C:\Apps\Blender\.blender\scripts\bpymodules\nif_common.py", line 1227, i

n gui_button_event

self.gui_exit()

File "C:\Apps\Blender\.blender\scripts\bpymodules\nif_common.py", line 1579, i

n gui_exit

self.callback(**self.config)

File "C:\Apps\Blender\.blender\scripts\import\import_nif.py", line 3750, in co

nfig_callback

importer = NifImport(**config)

File "C:\Apps\Blender\.blender\scripts\import\import_nif.py", line 274, in __i

nit__

self.import_root(root)

File "C:\Apps\Blender\.blender\scripts\import\import_nif.py", line 352, in imp

ort_root

b_obj = self.import_branch(root_block)

File "C:\Apps\Blender\.blender\scripts\import\import_nif.py", line 543, in imp

ort_branch

n_child, b_armature=b_armature, n_armature=n_armature)

File "C:\Apps\Blender\.blender\scripts\import\import_nif.py", line 439, in imp

ort_branch

b_obj = self.import_mesh(niBlock)

File "C:\Apps\Blender\.blender\scripts\import\import_nif.py", line 2348, in im

port_mesh

bodypart_wrap.set_value(bodypart.body_part)

File "C:\Python26\lib\site-packages\pyffi\object_models\xml\enum.py", line 120

, in set_value

raise ValueError('invalid enum value (%i)' % val)

ValueError: invalid enum value (32)

 

 

 

The armor does open in Blender, however, apparently only a part of the upper legs, as you can see in this picture:

 

 

 

 

 

Google told that some people had this problem too, but it didn't tell me how to solve it.

 

Please, can anyone help me with this?

Excuse me if this is a dumb question, but as mentioned above, i have never modded anything before.

 

[anubis]

Make sure you have correct blender version and all required apps to work with nif file especially skyrim nif.file, might want to check this Blender NIF Import - Export Tutorial , so far that tutorial works for me...

 

i'm using

Blender 2.49b

Python 2.6.6

PyFFI 2.1.10

Blender Nif Scripts 2.5.8

Nifskope 1.1.0-rc4

 

In nifskope..

- If you do some mash up (another body with another armor from another nif file) make sure you change the string names after you paste branch if its using Bones name.

- Delete BSLightingShaderProperty on every each mesh.

- Change user version to 11 and user version 2 to 34 in niheader.

 

 

[hauntedpassion]

hi, thanks for your fast answer.

 

updating the tools to the versions you reccomended worked, i can now open the nifs without problem. Also to pointing out that tutorial, i will follow it's steps.

for a noob like me this is gonna take a while to figure out, so thanks a lot for your answer.

 

i don't know what this means:

 

 

- If you do some mash up (another body with another armor from another nif file) make sure you change the string names after you paste branch if its using Bones name.

 

 

can you maybe explain it to me?

 

[on1wl]

Make sure you have correct blender version and all required apps to work with nif file especially skyrim nif.file' date=' might want to check this Blender NIF Import - Export Tutorial , so far that tutorial works for me...

 

i'm using

Blender 2.49b

Python 2.6.6

PyFFI 2.1.10

Blender Nif Scripts 2.5.8

Nifskope 1.1.0-rc4

 

In nifskope..

- If you do some mash up (another body with another armor from another nif file) make sure you change the string names after you paste branch if its using Bones name.

- Delete BSLightingShaderProperty on every each mesh.

- Change user version to 11 and user version 2 to 34 in niheader.

 

 

 

I have the same problem, and all the right versions. It used to work, now it fails. I even uninstalled everything and reinstalled them, still get the invalid enum value on files I was able to import in the past. ANy ideas? Thanks!

[anubis]

can you maybe explain it to me?

 

huh' date=' pardon me, totally forgot about this post, what i'm try to say is when copy branch a mesh from different nif file (mash up) into your custom armor, it will mostly using random string names or even bones name after you paste branch it, which might give you weird animation or worst, CTD. so make sure after paste branch you renamed it again into something.

 

I have the same problem, and all the right versions. It used to work, now it fails. I even uninstalled everything and reinstalled them, still get the invalid enum value on files I was able to import in the past. ANy ideas? Thanks!

 

are you sure you have all version right ? try reinstalling the nifscript for blender and what nifskope version that you curently using ? and what model that you want to import (clothings/Weapons/objects).

 

 

[on1wl]

can you maybe explain it to me?

 

huh' date=' pardon me, totally forgot about this post, what i'm try to say is when copy branch a mesh from different nif file (mash up) into your custom armor, it will mostly using random string names or even bones name after you paste branch it, which might give you weird animation or worst, CTD. so make sure after paste branch you renamed it again into something.

 

I have the same problem, and all the right versions. It used to work, now it fails. I even uninstalled everything and reinstalled them, still get the invalid enum value on files I was able to import in the past. ANy ideas? Thanks!

 

are you sure you have all version right ? try reinstalling the nifscript for blender and what nifskope version that you curently using ? and what model that you want to import (clothings/Weapons/objects).

 

 

 

Thanks for your help, Anubis. Here are my versions:

Blender 2.49b

Python 2.6.6

PyFFI 2.1.11

Blender Nifscripts 2.5.8.09855eb-windows.exe

Nifskope 1.1.0-rc4

 

I am trying to import femalebody_0.nif like I've done dozens of times in the past. I took a break for maybe two months, came back using the same tools and keep getting the enum error. Pulling my hair out trying to figure out what changed. I follow the tutorial line by line to be sure I am doing it right. (startup 20.2.0.7, change user version 1 to 11, 2 to 34, delete shader, save, try to import into blender, fail.) I've even tryed 2 other versions of Nifskope, and tried importing files that I had imported in the past. Since that fails too, I am guessing the problem is in the Nifscript. Thanks again!

 

So it turns out, the enum error is not important. I continued on and was able to import my edited nif back into Skyrim, despite Blender complaining about an error. Go figure.

[hauntedpassion]

can you maybe explain it to me?

 

huh' date=' pardon me, totally forgot about this post, what i'm try to say is when copy branch a mesh from different nif file (mash up) into your custom armor, it will mostly using random string names or even bones name after you paste branch it, which might give you weird animation or worst, CTD. so make sure after paste branch you renamed it again into something.

[/quote']

 

ah i see...thanks for the answer! i will keep that in mind!

[Firedoom]

I believe you still have to trick Blender into opening Skyrim nifs. There is a tutorial all about that here.

 

Edit: Nevermind, the tutorial you used already tells you that... but maybe there's a difference between the two, I don't know.