Mesh Rigger (Skyrim, Fallout, Oblivion) Beta.89.f (10-26-2014)

[Z0mBieP00Nani]

 is that a new vampire lord texture? 

 

I don't know but it looks damn creepy, lol.

[medic975]

Possibly a dumb question, but wasn't quite sure after reading the use. 

 

To add in HDT or TBBP to an armor or clothing mesh do I.

 

a. Select file, template, and a the body which I'm using, in this case the project citrus body at zero weight, preserve skeleton, then target, mesh, the zero weight armor mesh I'm wanting to be HDT or TBBP? With search distance 10, vertex 4, replace weights, delete all weights, replace bones, replace partitions, female only, and all materials selected all of the others not selected.

 

b. Same as above but using a CBBE HDT weighted clothing item zero weight, to a UNP non weighted clothing item zero weight. Same armor.

 

I'm not really seeing any results and I'm sure it's user error.

[Monsto Brukes]

is there any way to get the python screen to stay up after it's done? I THINK it's generating an error message, but I can't tell...

 

I'm using the version of your toolbox with all the batch files.

[movomo]

is there any way to get the python screen to stay up after it's done? I THINK it's generating an error message, but I can't tell...

 

I'm using the version of your toolbox with all the batch files.

There are two ways. For everyone who wants to know what's going on behind there when mesh_rigger crashes:

 

1. quickly screencapture the moment that it crashes. you must be really, really nimble.

 

2. do not use the batch files that come with this package. instead, open the cmd window, and specify the pythonpath and the script path by yourself. then the window will not close after crashing.

for example,

C:\Users\your_name> d:\path\to\mesh\rigger\Python\Python-Portable.exe d:\path\to\mesh\rigger\Python\App\Scripts\mesh_rigger.py

- or -

C:\Users\your_name> d:
D:\> cd d:\path\to\mesh\rigger\Python
D:\path\to\mesh\rigger\Python> Python-Portable.exe App\Scripts\mesh_rigger.py

- or if you have python such as python3.4.1 64bit, just something like -

C:\Users\your_name> C:\Python34\python.exe d:\path\to\mesh\rigger\Python\App\Scripts\mesh_rigger.py

hope this helps!

[foreveraloneguy]

I've run into an odd bit of a problem. I'm trying to add bbp bones to the exeter meshes, and after running mesh rigger, the offsets are incorrect. In game, the mesh is high and behind where it should be. I looked through the log, but nothing seems unusual. Anyone else seen something similar, or otherwise have any ideas?

 

I'm using the default settings for rigger if that makes any difference.

[gerra6]

Which version of Mesh rigger are you running?

 

0.46 on the front page, or one of the more recent experimental versions deeper in the thread? (I probably should update the OP with a more recent build, but every build so far has a problem with *something*)

 

Adequately compensating for the *shockingly* wide variety of methods used to position meshes in Skyrim was one of the main drivers behind the latest versions.

 

Here is the most up-to-date public version of my experimental tools package, including Mesh rigger.

 

Portable Package 0.89.e (includes Mesh Rigger):Tools RC_89.e.7z

 

Scripts Only Package 0.89.e: Tools RC_89_e_Light.7z

 

Changelog:

 

Lots of stuff.

 

Enjoy.

[Joedpa]

I used this to replace the SOS Body Mesh with bones from the vanilla body. It worked, but now in the CK when I apply that body to an NPC, I cannot change the weight of the body mesh.

 

Can someone help me?

[gerra6]

It sounds like the _0 and _1 weight bodies did not get re-rigged during the same mesh rigger run.

 

When the tool runs, it will check the end of the file names to determine which mode it should operate in. In order for Mesh Rigger to properly handle weight slider compatible nifs:

 

Here's what you want to do (Skyrim nifs only)

 

1. Ensure that both the _0 and _1 nifs that you want to re-rig are present in the same folder. This ensures that the tool will recognize the nifs as being components of a single weight slider.

 

2. Ensure that the template nif that you use ends with either _0.nif or _1.nif. This tells the tool which body should receive the copied weights first.

 

When the tool runs, if it detects weight slider compatible nifs, it will perform a few additional steps.

 

A. First, it compares the base locations and normals of each vertex on both nifs and stores the offsets. This gives the tool the ability to seamlessly convert one nif into the other.

B. Next, it attempts to determine whether the template matches the _0 or _1 nif. The weights will be copies between the most compatible nif (file name comparison only).

C. Finally, after the first nif is re-rigged and saved, the tool will apply the saved offset data from A to convert a copy of the re-rigged nif into the second nif.

 

This ensures that the linked weight slider compatible nifs are completely identical in every respect except for vertex location and vertex normals and should ensure full weight slider compatibility.

[foreveraloneguy]

Which version of Mesh rigger are you running?

 

0.46 on the front page, or one of the more recent experimental versions deeper in the thread? (I probably should update the OP with a more recent build, but every build so far has a problem with *something*)

 

Adequately compensating for the *shockingly* wide variety of methods used to position meshes in Skyrim was one of the main drivers behind the latest versions.

 

Here is the most up-to-date public version of my experimental tools package, including Mesh rigger.

 

Portable Package 0.89.e (includes Mesh Rigger):Tools RC_89.e.7z

 

Scripts Only Package 0.89.e: Tools RC_89_e_Light.7z

 

Changelog:

 

Lots of stuff.

 

Enjoy.

 

Looks like I had 85a, but was using a copy of mesh rigger from this thread. Not the one in the OP, but one further in. I'll give it a go with this version and see what happens.

 

if there's still a problem, what would be the most useful data to provide back to determine if it's a whacked mesh, or if there's a problem with the tool itself?

[gerra6]

The log file (found in the save folder) is a good start.

 

If that doesn't tell us enough, upload the template nif and the nifs that you are rigging.

[foreveraloneguy]

Well, .89e is a huge improvement over whatever version I was using before. Conversions are much more accurate, and weighting is greatly improved as well. Dude, I'm just about ready to offer to bear your children, as physically impossible as that might be.

[Morra]

The last update works amazing. Conversion indeed was never before so easy. Thank you.

[xarathos]

Oooooooooooo a new version to test~

 

Gonna go put it through its paces right now. Will update when I've got some results to share. Thanks again!

[movomo]

Looks like your new work is rock solid.

Nice work!!

By the way, do they all work, or some of them remain broken? I mean things other than the mesh rigger?

[gerra6]

Dunno.

 

Seam Mender should work...but...well...you know about the issue there.

Clothing Converter should be rock solid when starting with UV compatible nifs

 

The rest...shrug...maybe?

[Cattpride]

Yo man I'm using v89 to weigh an armor set and it closes with an empty output folder every time. I ran the mesh rigger script through the python shell and it gives me this error: 

Any ideas as to what's wrong?

[gerra6]

A memory error generally means that you are attempting to run the 32 bit version of the tool (like the portable version) with a *very* high poly count mesh. One of the drawbacks of Python is that it can be a bit of a memory hog.

 

The solution, unfortunately, is to install the 64 bit version of Python, install Pyffi, and then run the scripts only version of the tool.

[Cattpride]

Kind of at a dead end here right now.

Can you please tell me what the correct procedure/commands are to install PyFFI  and run the rigger script through the 64bit Python? I looked this up already but I do not know a thing about using python, so most of the help I found just results in more questions.

[gerra6]

Yeah...it can get a bit ugly.  In particular, the pyffi installer doesn't always recognize the more recent versions of Python.

 

So let's just do a manual drag-and-drop installation of pyffi.

 

Step 1: Install a 64 bit version of Python 3.  Do a full install.  Note: My primary internal testing platform is Python 3 64 bit, but the tool should be compatible with any 3.x versions.

 

Step 2: Go to the folder where you installed Python.  Drag the Lib and Scripts folders from the attached pyffi.7z file into the folder.

 

At this point, running the tool should be as simple as doubleclicking on meshrigger.py.

 

pyffi.7z

[Cattpride]

I installed PyFFI and gave it another go, but no success I'm afraid.

[gerra6]

Would you post the config file and the log file.  That looks like the sort of message that you might get if something went wrong with either the template or target file selection.

[Cattpride]

http://a.smt-dds.net/save.rar

It might be the target for some obtuse reason. I'm not sure how to check the amount of vertexes without importing it into Blender, but the .nifs themselves are only like 6MB in size.

[gerra6]

OK, it looks like no target file is getting selected and the folder:

 

S:/Skyrim/Tools RC_89_e_Light/Mesh Rigger/target

 

is empty.

[Cattpride]

I put the same files in there twice with different names to try and prevent that. Does the tool require a different/more specific target name than "cuirass_"?

[gerra6]

That looks good.  That *should* work.

 

*edit*

 

Would you be willing to send me the template and target files.

 

I need to figure out what's going on.  That error message makes no sense in this context.