New Clothing Body Style Converter Beta v0.89f (10-26-2014)

[gerra6]

Not a major issue, but Make Lattice refuses to convert the feet mesh from Sevenbase to my custom body from UNP. Log attached. Can provide files if it helps. This is in RC 79.

 

I'm not having any luck replicating the error. Would you be willing to send me the From and To files you were working with?

 

***Edit***

 

Never mind, I tracked it down to an issue with the 'Vertex Index' search. For now, disabling that feature should eliminate the error.

 

Question: can your script run with command-line arguments, bypassing the GUI altogether? I have 11 armor sets to convert, with lattices from 5 different bodies. Being able to compose all that in a script would make it much easier to test new versions.

At the moment no, but it's doable.

 

In the meantime, the settings files are plain text and can be manually edited by hand. When the tool is running 'Save Current Settings' can be used to generate a custom settings file and 'Load Settings' can be used to load.

[gerra6]

The update did WONDERS to the artifacts issue! Here's another "extreme" conversion to a crazy cup size. The difference in the mesh quality is insane.

That's just awesome.

[ger4]

Lattice converter CTDs if I try to create a HGEC D-CUP to GUTS lattcie using these

 

 

GUTS.zip

[ger4]

Also just got this when running the clothing converter

 

[gerra6]

It looks like my 'Index' search is bugging out.

 

Just disable Index Search and enable UV search and the tool should run fine. I'll see if I can track down why Index search is failing.

 

***Edit 2*** I've fixed the Vertex Index ugliness. I'll post the patch once I track the second error you reported.

[gerra6]

Also just got this when running the clothing converter

What the hell?

 

Pleases send me the lattice and the target files you were working with. That's...insane. No idea how that happened.

 

Unless...Hmm...were you by any chance converting an entire folder of files?

 

I wonder if the tool loaded a tri file. It *can* convert tri files from one body style to another, but honestly it's been ages since I've tested that ability. It's a major pain in the ass to actually test tri files after conversion. Plus, Tri files aren't skinned, so it is impossible to convert their vertex locations into worldspace unless I also load the nif that they are paired with and cheat off of it for the worldspace conversions.

 

*Edit* Nope...tri file couldn't cause that error.

[ger4]

 

Also just got this when running the clothing converter

What the hell?

 

Pleases send me the lattice and the target files you were working with. That's...insane. No idea how that happened.

 

Unless...Hmm...were you by any chance converting an entire folder of files?

 

I wonder if the tool loaded a tri file. It *can* convert tri files from one body style to another, but honestly it's been ages since I've tested that ability. It's a major pain in the ass to actually test tri files after conversion. Plus, Tri files aren't skinned, so it is impossible to convert their vertex locations into worldspace unless I also load the nif that they are paired with and cheat off of it for the worldspace conversions.

 

*Edit* Nope...tri file couldn't cause that error.

 

Converting a whole folder

 

 

[gerra6]

Thanks

 

I'll see what I can figure out.

[ger4]

Just a quick note, but when you select customize mesh, the menu sometimes goes off the side of the screen if ther are too many materials in a mesh and you can't click ok.

[Monsto Brukes]

Just a quick note, but when you select customize mesh, the menu sometimes goes off the side of the screen if ther are too many materials in a mesh and you can't click ok.

 

Sounds like it's time to either go tabbed or accordion. I suppose vertical scrolling would be easier.

[gerra6]

Yeah

 

I probably need to take a good long look at the auto-generated parts of the UI.

[Monsto Brukes]

alright so what do I do here right now? it's not running at all. 

 

first it errors out "no vertices", with UV Search on and Vert Index Search off. With UV off and Vert Ind Search off, it tells me

PermissionError: [Errno 13] Permission denied: 'g:\\Games\\Skyrim\\Apps\\Convert
Clothing\\Convert Clothing RC_79_Light\\Convert Clothing RC_79_Light'

[gerra6]

Try resetting the settings to default. It sounds like it's probably trying to access a directory or a file that doesn't exist.

[Monsto Brukes]

Try resetting the settings to default. It sounds like it's probably trying to access a directory or a file that doesn't exist.

Unless the settings is in a separate directory, that's not likely. I unzipped "light" to a new dir and ran the bat from there. So everything was fresh from the zip.

[gerra6]

Lots of fun Python things can go wrong with the 'Light' version, particularly if you have multiple versions of Python installed.

 

Did you edit the python.exe path in the .bat file?

[Monsto Brukes]

Lots of fun Python things can go wrong with the 'Light' version, particularly if you have multiple versions of Python installed.

 

Did you edit the python.exe path in the .bat file?

 

No. It's in my system path. I've been using this same python install since whenever. This is the first time to get this permissions problem.

[gerra6]

Well, basically the OS is throwing a permission denied error when the tool attempts to create and/or modify a file.

 

It might be happening when the tool tries to make a save directory, when it saves a config file, etc. No idea. As I mentioned before, it can also happen if the settings specify an invalid path that causes the tool to attempt to write to a folder that does not exist.

 

But, if you haven't yet done so, please restore the settings to default, select your To nif, your From nif, and your Output directory and try to run the tool.

[gerra6]

Clothing Converter Release Candidate 0.80

 

This update resolves several bugs

 

Note: Please generate new Lattices for use with 0.80. Older lattices will continue to suffer from pre-existing artifacts.

 

Download:

 

Portable Package 80 Upgrade (upgrades Portable Package v.7x to v.80):  Convert Clothing RC_80_Upgrade.7z

Light Download 80 (scripts only. Recommended if you intend to use 64 Bit version of Python):  Convert Clothing RC_80_Light.7z

 

 

ChangeLog

 

v.79 to v.80

1. Index Search function should no longer crash the tool

2. Unskinned nifs will no longer crash the tool

3. New option added to template folder ('exclude ground meshes'). This tells the tool to skip nifs that end with gnd.nif or GND.nif.

4. Clothing Converter and Template Maker now properly categorizes and matches neck, hand, waist, and foot seams.

[xarathos]

"Template Maker?" He said, his ears twitching in curiosity and excitement?

 

Good thinking on the exclusion thing, that'll skip a series of (at first fairly scary looking until you realize which meshes set them off) errors. ^^

 

EDIT: Have an experiment I was thinking to try and was wondering if you'd stated, what happens if one of your templates is only available in one weight? :/

 

Eh, suppose I'll find out. Worst case scenario I discover a new way to fail spectacularly!

 

Better question. Does anyone have any thoughts on how to make a decent template mesh for converting from vanilla?

[gerra6]

"Template Maker?" He said, his ears twitching in curiosity and excitement?

 

Whoops...I put the wrong name in the changelog, although the name 'Template Maker' probably makes more sense than 'Lattice Maker'.

 

Good thinking on the exclusion thing, that'll skip a series of (at first fairly scary looking until you realize which meshes set them off) errors.

 

EDIT: Have an experiment I was thinking to try and was wondering if you'd stated, what happens if one of your templates is only available in one weight?

 

Eh, suppose I'll find out. Worst case scenario I discover a new way to fail spectacularly!

Well, for Skyrim weights, here's what the tool does.

 

The first step when starting a brand new conversion is to make a lattice. The lattice is the template that tells the tool how to convert future meshes from one body shape to another. If you're working with Skyrim nifs, the lattice will check the nif for either _0 or _1 and remember which weight nif was used when it was created.

 

When you later use that lattice to convert a set of clothing, it will check whether any currently selected nifs are _0, _1 weight pairs. At that point, it does something kind of neat. In a nutshell, it first converts whichever _0 or _1 nif matched the lattice morph type. Once that's complete, it automatically generates the other weight morph.

 

Better question. Does anyone have any thoughts on how to make a decent template mesh for converting from vanilla?

Sure. The current generation of the Clothing Converter can generate nearly perfect body conversions between any two body styles that share the same texture standard (UV Search).

 

So, for optimal results, simply extract the vanilla astrid body from the BSA and set it as your From nif. For the To nif, simply select any UNP compatible body. The default settings should otherwise be fine. Generate your lattice.

 

Once you have a lattice, simply run clothing converter, load the lattice, and select the files or folders that you wish to convert.

[Nightwynd]

Any idea what causes this error when generating a new lattice? It began to happen after I upgraded to 0.80

[ger4]

Don't know if this is caused by the already discussed under boob issues, but some mesh have clipping just at the very base of the boob even if they are high poly. the faces in tha area seem to be 'folded' if you look at them if blender.

 

 

 

 

 

SUPbody.nif

 

 

I also have some kind of artifact in the center of the mesh where 2 vertices are jutting out.

 

 

 

With this DMRA to GUTS conversion, there seems to be some distortion on the converted breasts (in the under-boob area and in the center between the breasts where some vertices seem to have merged).

 

DMRA.zip

 

[gerra6]

Yeah, I did a couple of experimental things in v.80 that may not have been good ideas.

 

For one, for some dumb reason I decided that the Left/Right search was no longer needed since the 'find nearest point on face' algorithm was working so well. Which is the sort of stupid idea that comes to me when I've clearly spent too much time coding.

 

So...RC.80 is likely to have a problem with artifacts near the center x-axis for certain types of transformations. The reason is fairly straight-forward. For cleavage heavy nifs, the nearest face to an arbitrary point on the X-Axis has a chance of belonging to the side of either the Left or Right breast, rather than a face directly on the x-axis, on the body.

 

To compensate for this, around v.60 or so I added a fairly crude feature that, essentially, forces any vertex near the x-axis to search for a match on both the left side and the right side of the x-axis.

 

Now...this was kind of a hack-ish solution. I didn't like it...that's probably why a not-entirely-sober version of myself thought it would be a good idea to take it out.

 

Which leads me to an idea.

 

I want the tool to do a better job handling conversions between nifs with cleavage and those without cleavage. I haven't yet worked out all of the details, but I'd like to add an end-user customize-able option that allows you to force vertices with certain characteristics to either favor matches near the x-axis or to favor mirrored matches far away from the x-axis.

 

The basic idea is this...for a given piece of armor or clothing, this setting will allow you to decide whether the material between the breasts should be stretched between them after the conversion, or whether it should follow the contour of the body.

[gerra6]

With this DMRA to GUTS conversion, there seems to be some distortion on the converted breasts (in the under-boob area and in the center between the breasts where some vertices seem to have merged).

I'll take a look and see if there is room for improvement in the tool for these types of cases. Unfortunately, part of the problem is probably the mesh that is being converted.

 

The cleavage in 'origonal.nif' is actually fused together. This is a fairly common birth defect in certain DMRA tops. If a DMRA top is converted to a body style with less cleavage, the fused vertices in the cleavage wills till be fused.

[gerra6]

Any idea what causes this error when generating a new lattice? It began to happen after I upgraded to 0.80

Yeah.

 

That will happen if there is a degenerate triangle on the nif (a 'triangle' with one side that has a length of exactly 0). For some silly reason I disabled the degenerate triangle test in my zeal to eliminate every possible source of artifacts. In my defense, the degenerate triangle test was also a speed optimization/shortcut. I just neglected to account for its absence later on when the tool needed to normalize the length of an edge.

 

Oops.

 

V.80 was a...weird...update.

 

I was trying a few too many experimental things in a single update, and really didn't test them enough.

 

Sorry about that.