Don't want to make another really long post, so I've shoved all the instruction text into the partcut_blender zip. This post will just be a summary.
Partcuts in Blender:
- The 16 bytes of each cut represent a magnitude and a unit vector (must be a unit vector to work properly in game).
- Preceding bounding box still seems to do nothing. Set it to (0,0,0) (0,0,0) at one point with no visual change.
- Included Blender file contains scripts for both "importing" and "exporting" partcuts.
- There still exists a very small difference between what you see in Blender and what you see in game, generally within a single unit of measurement. Easily corrected with some really small adjustments to the magnitude.
- I may improve the partcut creation side of things to simply calculate the magnitude and unit vector of a freely transformable plane in Blender to make it easier to work with.
Custom Partcut Sample:
- Two pacs, based on the Lahn body, intended to cut just the top or just the bottom off of underwear. Works nicely on accessories to toggle on and off (requires new entries in partcutdesc.xml).
- Would be cool if I could "erase" a partcut with another partcut. Not sure if this is possible or not, so hiding part of some underwear may reveal the underwear's own cuts into the body.
Other thoughts:
- Working with the partcut data can be a bit tricky. A fairly conceptually simple cut can result in having to make multiple cut groups to achieve the desired result. The topless partcut was a single group of three cuts, but the bottomless partcut ended up being three different cut groups, just to basically achieve a "reverse" cut.
- Started researching some files that previously confounded me, but so far have found nothing strange about them, now that I understand partcuts and partcutdesc.xml more. Mostly, it's just a matter of their weird, inconsistent use of partcuts.
Cheers.
