Prepacked HDT-SM - HDT Skinned Mesh Physics with Modding Guide

zzz72w3r · July 6, 2015

ouch... So it could be that I'm using the wrong OpenCL? That kinda sucks. I know that my HD7990 might not be the newest, but for pure muscle it's great. I'll look into getting OCL2.0 tommorow.

You need the new SMP as well. Old SMP works with OpenCL1.2 and the new SMP works only with OpenCL2.0 or you will CTD. Use the links from HydrogensaysHDT's 3DM page in my above post.

Heavy CPU load, chances are you are using old, now obsolete SMP prior to 5/22.

CTD, chances are you are using post 5/22 SMP with OpenCL1.2 instead of OpenCL2.0.

passdummy1 · July 6, 2015

It's also worth noting, that naturally the more things are collision enabled with each other, the more calculating power is required. Like say, you enable every bone in the skeleton to be collision enabled with the boobs, and then that has to be calculated for all actors currently loaded, the CPU power required would be rather hefty, if it works at all. On my somewhat modest AMD FX 4130 Quad, even just hands, gloves and Schlong collision activated with breasts and vagina causes some noticable performance impact, even with the new HDTSM, compared to simply disabling all collision.

The best cost-benefit ratio I've personally found is to enable breast-hands, breast-gloves, breast-breast and buttcheek-buttcheek. Essentially what I'm trying to say here is that based on my experience with it thus far, that goes for HDTPE as well, collision should only be enabled where you really, really want it to happen. Although my machine is somewhat modest, so perhaps you need not worry about any of it if your hardware could do cancer research on the side while playing Skyrim and still be bored to tears

kyukatsuki · July 6, 2015

Oh I have absolutely NO worries when it comes to raw computing power. Intel i7 3770K CPU O.C. @4.2 GHz, AMD Radeon HD 7990 GPU @ 1100 MHz & 6Gb Vram, 32Gb DDR3 @1600MHz, and twin 840 Pro SSD's in Raid-0. I have all the muscle I need to run anything and everything in Skyrim. The program and mods are my limiting factor.

Edit: I really don't want to have to download this Chinese program just to get the files... baiduyuguanja.exe? fuck...

Double Edit: Just went through getting the files from the baidu site. Gonna try out the .DLL soon.

Tripple Edit: Fuck yeah seaking! Got it working! Thanks for the help guys!

kyukatsuki · July 6, 2015

I'm really glad that I've got this working now. Thanks for all your help guys! I do have one final question though. Which XML do I modify to change the bounce on my character? The butt is looking a bit floppy and twitching a lot. I want to increase it's firmness, and maybe the breasts just a touch as well. I just need to know which values to modify, and which XML's have the values I need to change. I'm using Bodyslide2 with the CBBEHDT body type and some "quite full" adjustments with racemenu sliders. I like 'em curvy.

jayp420 · July 7, 2015

I'm really glad that I've got this working now. Thanks for all your help guys! I do have one final question though. Which XML do I modify to change the bounce on my character? The butt is looking a bit floppy and twitching a lot. I want to increase it's firmness, and maybe the breasts just a touch as well. I just need to know which values to modify, and which XML's have the values I need to change. I'm using Bodyslide2 with the CBBEHDT body type and some "quite full" adjustments with racemenu sliders. I like 'em curvy.

If your using the .xml packaged by t3h0th3r then it should say baseshape.xml is the one for cbbe. If you use the default .xml's then cbbe-tbbp. If you have collision on body the .xml should have baseshape as the shape name where your collisions are setup which is what cbbe NiTriShape name should be in nifscope. If your body does not have that name in nifscope then you have to get the .xml with your shape name or make one. You can also just look in your defaultBBPs.xml for your bodies <map shape= which should be baseshape that is your .xml you need to change.

kyukatsuki · July 7, 2015

Ok, that's what I was wondering about. I didn't know if CBBE used Baseshape.xml or BaseshapeX3.xml or some other .xml. Thanks jayp420.

Kinky · July 7, 2015

So is this still in testing or is it proper mod by now?

Serithi · July 7, 2015

So is this still in testing or is it proper mod by now?

Both.

Shivalala · July 8, 2015

So is this still in testing or is it proper mod by now?

I have been using the older version for two months now with no problems. Runs pretty stable for me (with about a 100 mods running alongside)

Knaeggchen · July 8, 2015

Well guys, for some reason I can't get the new Version running. I had an old version and decided to update it now. But no matter what I do, if I try to use the new dll it simply doesn't work. It doesn't crate a hdtSkinnedMeshPhysics.log, so it seems that isn't even trying to load at all. I also tried with different config files (my own as well as those provided in this thread), but still no difference. All works perfectly fine as long as I use the old dll.

Since I use Intel as well as nvidia I disabled opencl. Do I need to change some settings somewhere to make it work? Or do I need to put the dll into a different folder than it's used to be?

Just in case I'll drop my configs.xml in here as well, but I didn't touch it at all.

<?xml version="1.0" encoding="utf-8"?>

<configs>
    <opencl>
        <!--warning : not finish yet-->
        <!--warning : this can be slower because of the bad PCI-E transfer and bad schedule-->
        <enable>false</enable>
        <platformID>0</platformID>
        <numQueue>16</numQueue>
    </opencl>
    <solver>
        <numIterations>10</numIterations>
        <groupIterations>1</groupIterations>
        <groupEnableMLCP>true</groupEnableMLCP>
        <erp>0.2</erp>
        <min-fps>60</min-fps>
    </solver>
</configs>

Edit:

I've got another question. After toying around a bit more with it (still using the old version) I came to following conclusion:

If you want to apply it's physic to an armor/piece/whateva you have to options to do so:

1. you can add a NiStringExtraData directly into the nif (similiar to HDT PE) and point to a specific xml.

This way you can use all the bones used in the nif, but you can only use a single xml, using NiStringsExtraData for adding multiple xmls won't work at all. (Adding multiple NiStringExtraData Nodes doesn't seem to work either)

2. You can add physics by adding the shape name of at least one shape used in the nif into defaultBBPs.xml. All shapes will then use the same physics for specified bones in the loaded xmls and it seems that you can also use multiple xmls as long as you have multiple shapes in which you can trigger the loadings, but on the downside you have to add them manually into the xml if you download new armors as well as delete them again. And you cannot use bones, that aren't defined in your skeleton. Custom bones inside the nif won't be recognized unlike the first option. Also: If you have defined a specific xml via NiStringExtraData, this option won't work at all. (basicly you can choose only one option)

My idea is to add custom physics (i.e. skirt physics) into armor, while also using default physics for always-used parts like breasts. So basicly it will use the same breast physics for everything else by loading the same file, instead of having to define the same physics over and over again for every single armor while also having custom physics for skirts, or accessoires and stuff.

So finally my question: anyone got an idea how to do it?

Serithi · July 9, 2015

-snip-

... Your idea is how things work in the first place. "Regular" .xml's for handling the body physics and such, and then any HDT outfits (by which i mean, stuff like skirts and the like, not just breasts and butt) have their own individual .xml's for those HDT bits as needed (sometimes sharing one if the shapes are similar). PE and SMP are highly modular.

Knaeggchen · July 9, 2015

... Your idea is how things work in the first place. "Regular" .xml's for handling the body physics and such, and then any HDT outfits (by which i mean, stuff like skirts and the like, not just breasts and butt) have their own individual .xml's for those HDT bits as needed (sometimes sharing one if the shapes are similar). PE and SMP are highly modular.

I may be ignorant (or simply blind), but I never saw any armor approaching it the way I described above. As mentioned in my previous post, I don't know of any possibility to combine armor specific physics (i.e. a ribbon) that has it's own unique bones, not present in your standard skeleton that takes with pre-defined physics based for standart stuff like breast. All examples I have looked into didn't work that way either. Instead they always re-defined the same stuff in their unique xml instead of refering to the default xmls.

Same with HDT-PE, while I do know how to implement multiple xmls into one model, I ever only saw maybe 2 armors that were using the default xmls WITH unique xmls rather than just going for only the defaults or re-defining them in their unique ones.

So basicly all armors for both HDT Plugins I've found so far either used only the default xmls or implemented their unique xmls without using the defaults at all.

If I am just blind or oblivious to something, please go ahead and explain it to me. As far as I am concerned, both HDT PE as well as HDT SMP don't look too "highly modular" to me as you are describing it.

jayp420 · July 9, 2015

Well guys, for some reason I can't get the new Version running. I had an old version and decided to update it now. But no matter what I do, if I try to use the new dll it simply doesn't work. It doesn't crate a hdtSkinnedMeshPhysics.log, so it seems that isn't even trying to load at all. I also tried with different config files (my own as well as those provided in this thread), but still no difference. All works perfectly fine as long as I use the old dll.

Since I use Intel as well as nvidia I disabled opencl. Do I need to change some settings somewhere to make it work? Or do I need to put the dll into a different folder than it's used to be?

Just in case I'll drop my configs.xml in here as well, but I didn't touch it at all.
<?xml version="1.0" encoding="utf-8"?>

<configs>
    <opencl>
        
        
        <enable>false</enable>
        <platformID>0</platformID>
        <numQueue>16</numQueue>
    </opencl>
    <solver>
        <numIterations>10</numIterations>
        <groupIterations>1</groupIterations>
        <groupEnableMLCP>true</groupEnableMLCP>
        <erp>0.2</erp>
        <min-fps>60</min-fps>
    </solver>
</configs>
Edit:

I've got another question. After toying around a bit more with it (still using the old version) I came to following conclusion:

If you want to apply it's physic to an armor/piece/whateva you have to options to do so:

1. you can add a NiStringExtraData directly into the nif (similiar to HDT PE) and point to a specific xml.

This way you can use all the bones used in the nif, but you can only use a single xml, using NiStringsExtraData for adding multiple xmls won't work at all. (Adding multiple NiStringExtraData Nodes doesn't seem to work either)

2. You can add physics by adding the shape name of at least one shape used in the nif into defaultBBPs.xml. All shapes will then use the same physics for specified bones in the loaded xmls and it seems that you can also use multiple xmls as long as you have multiple shapes in which you can trigger the loadings, but on the downside you have to add them manually into the xml if you download new armors as well as delete them again. And you cannot use bones, that aren't defined in your skeleton. Custom bones inside the nif won't be recognized unlike the first option. Also: If you have defined a specific xml via NiStringExtraData, this option won't work at all. (basicly you can choose only one option)

My idea is to add custom physics (i.e. skirt physics) into armor, while also using default physics for always-used parts like breasts. So basicly it will use the same breast physics for everything else by loading the same file, instead of having to define the same physics over and over again for every single armor while also having custom physics for skirts, or accessoires and stuff.

So finally my question: anyone got an idea how to do it?

Did you install the intel runtimes for opencl 2.0? The newest plugin did not work for me either same as you know errors or crashes but after I installed the runtimes for opencl 2.0 it started working. My 760's isn't supported for 2.0 either but the runtimes still worked to get things moving. I also don't use the disable config.xml and everything still works.

Also with HDT-SMP you don't have to link your .xml's in your .nif file just to your defaultBBP's.xml. So as long as your armors body's nitrishape is a universal name like baseshape. Which would be your default body physics. Then have second nitrishape for your skirt to whatever name you want like skirt or something. You will be able to have just that but when ppl start using different names for the body is when you need multiple xml just for body physics.

Knaeggchen · July 9, 2015

Well guys, for some reason I can't get the new Version running. I had an old version and decided to update it now. But no matter what I do, if I try to use the new dll it simply doesn't work. It doesn't crate a hdtSkinnedMeshPhysics.log, so it seems that isn't even trying to load at all. I also tried with different config files (my own as well as those provided in this thread), but still no difference. All works perfectly fine as long as I use the old dll.

Since I use Intel as well as nvidia I disabled opencl. Do I need to change some settings somewhere to make it work? Or do I need to put the dll into a different folder than it's used to be?

Just in case I'll drop my configs.xml in here as well, but I didn't touch it at all.
<?xml version="1.0" encoding="utf-8"?>

<configs>
    <opencl>
        
        
        <enable>false</enable>
        <platformID>0</platformID>
        <numQueue>16</numQueue>
    </opencl>
    <solver>
        <numIterations>10</numIterations>
        <groupIterations>1</groupIterations>
        <groupEnableMLCP>true</groupEnableMLCP>
        <erp>0.2</erp>
        <min-fps>60</min-fps>
    </solver>
</configs>
Edit:

I've got another question. After toying around a bit more with it (still using the old version) I came to following conclusion:

If you want to apply it's physic to an armor/piece/whateva you have to options to do so:

1. you can add a NiStringExtraData directly into the nif (similiar to HDT PE) and point to a specific xml.

This way you can use all the bones used in the nif, but you can only use a single xml, using NiStringsExtraData for adding multiple xmls won't work at all. (Adding multiple NiStringExtraData Nodes doesn't seem to work either)

2. You can add physics by adding the shape name of at least one shape used in the nif into defaultBBPs.xml. All shapes will then use the same physics for specified bones in the loaded xmls and it seems that you can also use multiple xmls as long as you have multiple shapes in which you can trigger the loadings, but on the downside you have to add them manually into the xml if you download new armors as well as delete them again. And you cannot use bones, that aren't defined in your skeleton. Custom bones inside the nif won't be recognized unlike the first option. Also: If you have defined a specific xml via NiStringExtraData, this option won't work at all. (basicly you can choose only one option)

My idea is to add custom physics (i.e. skirt physics) into armor, while also using default physics for always-used parts like breasts. So basicly it will use the same breast physics for everything else by loading the same file, instead of having to define the same physics over and over again for every single armor while also having custom physics for skirts, or accessoires and stuff.

So finally my question: anyone got an idea how to do it?
Did you install the intel runtimes for opencl 2.0? The newest plugin did not work for me either same as you know errors or crashes but after I installed the runtimes for opencl 2.0 it started working. My 760's isn't supported for 2.0 either but the runtimes still worked to get things moving. I also don't use the disable config.xml and everything still works.

Also with HDT-SMP you don't have to link your .xml's in your .nif file just to your defaultBBP's.xml. So as long as your armors body's nitrishape is a universal name like baseshape. Which would be your default body physics. Then have second nitrishape for your skirt to whatever name you want like skirt or something. You will be able to have just that but when ppl start using different names for the body is when you need multiple xml just for body physics.

Well thanks, it does work for me now.

About HDT-SMP thought: It's still no solution to my problem. As mentioned in my first post, xml loaded throught defaultBPPs.xml will only work on your default skeleton, custom bones included into your custom armor don't work.

And on a side note: I don't think its realistic to have uniform NiTriShape names, so i wouldnt call having to add multiple Shape names and xmls into defaultBPPs.xml handy.

jayp420 · July 10, 2015

Well guys, for some reason I can't get the new Version running. I had an old version and decided to update it now. But no matter what I do, if I try to use the new dll it simply doesn't work. It doesn't crate a hdtSkinnedMeshPhysics.log, so it seems that isn't even trying to load at all. I also tried with different config files (my own as well as those provided in this thread), but still no difference. All works perfectly fine as long as I use the old dll.

Since I use Intel as well as nvidia I disabled opencl. Do I need to change some settings somewhere to make it work? Or do I need to put the dll into a different folder than it's used to be?

Just in case I'll drop my configs.xml in here as well, but I didn't touch it at all.
<?xml version="1.0" encoding="utf-8"?>

<configs>
    <opencl>
        
        
        <enable>false</enable>
        <platformID>0</platformID>
        <numQueue>16</numQueue>
    </opencl>
    <solver>
        <numIterations>10</numIterations>
        <groupIterations>1</groupIterations>
        <groupEnableMLCP>true</groupEnableMLCP>
        <erp>0.2</erp>
        <min-fps>60</min-fps>
    </solver>
</configs>
Edit:

I've got another question. After toying around a bit more with it (still using the old version) I came to following conclusion:

If you want to apply it's physic to an armor/piece/whateva you have to options to do so:

1. you can add a NiStringExtraData directly into the nif (similiar to HDT PE) and point to a specific xml.

This way you can use all the bones used in the nif, but you can only use a single xml, using NiStringsExtraData for adding multiple xmls won't work at all. (Adding multiple NiStringExtraData Nodes doesn't seem to work either)

2. You can add physics by adding the shape name of at least one shape used in the nif into defaultBBPs.xml. All shapes will then use the same physics for specified bones in the loaded xmls and it seems that you can also use multiple xmls as long as you have multiple shapes in which you can trigger the loadings, but on the downside you have to add them manually into the xml if you download new armors as well as delete them again. And you cannot use bones, that aren't defined in your skeleton. Custom bones inside the nif won't be recognized unlike the first option. Also: If you have defined a specific xml via NiStringExtraData, this option won't work at all. (basicly you can choose only one option)

My idea is to add custom physics (i.e. skirt physics) into armor, while also using default physics for always-used parts like breasts. So basicly it will use the same breast physics for everything else by loading the same file, instead of having to define the same physics over and over again for every single armor while also having custom physics for skirts, or accessoires and stuff.

So finally my question: anyone got an idea how to do it?
Did you install the intel runtimes for opencl 2.0? The newest plugin did not work for me either same as you know errors or crashes but after I installed the runtimes for opencl 2.0 it started working. My 760's isn't supported for 2.0 either but the runtimes still worked to get things moving. I also don't use the disable config.xml and everything still works.

Also with HDT-SMP you don't have to link your .xml's in your .nif file just to your defaultBBP's.xml. So as long as your armors body's nitrishape is a universal name like baseshape. Which would be your default body physics. Then have second nitrishape for your skirt to whatever name you want like skirt or something. You will be able to have just that but when ppl start using different names for the body is when you need multiple xml just for body physics.
Well thanks, it does work for me now.

About HDT-SMP thought: It's still no solution to my problem. As mentioned in my first post, xml loaded throught defaultBPPs.xml will only work on your default skeleton, custom bones included into your custom armor don't work.

And on a side note: I don't think its realistic to have uniform NiTriShape names, so i wouldnt call having to add multiple Shape names and xmls into defaultBPPs.xml handy.

Idk about custom bones. I was just referring to not having to use multi xml for one thing like body physics on the armors. The defaultbbp's.xml for HDT-SMP is not used like HDT-PE was its just a reference to link all xml for the plugin. Aleast that is how I've see how it works anyway.

Knaeggchen · July 10, 2015

Jep, that's exactly what I managed to find out. If you don't link to a custom xml inside the nif, it will look up all NiTriShape names for matches inside defaultBPPs.xml and if they find a match, it loads its corresponding xml. this way you can load as many xmls as you have NiTriShapes inside your nif, but it will only work with bones defined in your skeleton.nif.

I tried to convert HDT Tails into HDT-SMP. The tails have bonsed named from "HDT TailBone01" - "HDT TailBone09" (sometimes more, sometimes less, but 9 seem to be most common). While the skeleton does have "HDT TailBone01", "HDT TailBone01.1", "HDT TailBone01.2", "HDT TailBone01.3" and starts again with "HDT TailBone02" up to "HDT TailBone05.4". That means that if I dont change the names of the bones inside the nif, it will only load load 5 out of 9 bones, and bone 6-9 won't have any physics.

On the other hand, if I load the same xml directly via pointing on it through my nif file, all 9 bones will work perfectly fine without renaming them. But I won't be able to load more than one single xml.

In case of tails it is no big problem, because they don't share any physics with any other models, only between themselves, so there would be no drawback if I just point to a custom nif for every nif file. But in cases of armors, where you might share the same breast, or any other physics, it will be quite a problem. Because you have to choose between custom physics unique to the model (like ribbons, longer skirts, etc) or uniform breast and butt physics for all armors.

And the fact that it is triggered via shape names might also be quite a hassle because you would need to enforce a standart naming system on all modders, which isn't realistic, combined with possible manual edits of defaultBPPs.xml

jayp420 · July 10, 2015

Jep, that's exactly what I managed to find out. If you don't link to a custom xml inside the nif, it will look up all NiTriShape names for matches inside defaultBPPs.xml and if they find a match, it loads its corresponding xml. this way you can load as many xmls as you have NiTriShapes inside your nif, but it will only work with bones defined in your skeleton.nif.

I tried to convert HDT Tails into HDT-SMP. The tails have bonsed named from "HDT TailBone01" - "HDT TailBone09" (sometimes more, sometimes less, but 9 seem to be most common). While the skeleton does have "HDT TailBone01", "HDT TailBone01.1", "HDT TailBone01.2", "HDT TailBone01.3" and starts again with "HDT TailBone02" up to "HDT TailBone05.4". That means that if I dont change the names of the bones inside the nif, it will only load load 5 out of 9 bones, and bone 6-9 won't have any physics.

On the other hand, if I load the same xml directly via pointing on it through my nif file, all 9 bones will work perfectly fine without renaming them. But I won't be able to load more than one single xml.

In case of tails it is no big problem, because they don't share any physics with any other models, only between themselves, so there would be no drawback if I just point to a custom nif for every nif file. But in cases of armors, where you might share the same breast, or any other physics, it will be quite a problem. Because you have to choose between custom physics unique to the model (like ribbons, longer skirts, etc) or uniform breast and butt physics for all armors.

And the fact that it is triggered via shape names might also be quite a hassle because you would need to enforce a standart naming system on all modders, which isn't realistic, combined with possible manual edits of defaultBPPs.xml

I was just looking at a outfit i got from 3dmgame that is hdt-smp and it looks like she has custom bone in her xml. They may not be idk but maybe if you link the bone like she does it in there maybe it will work. http://bbs.3dmgame.com/thread-4663510-1-3.html

So the xml setup my work for what your trying atleast I hope if not Idk.

<per-triangle-shape name="VirtualGround">

<tag>ground</tag>

</per-triangle-shape>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

<generic-constraint bodyA="NPC L Breast" bodyB="NPC L PreBreast">

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint>

<generic-constraint bodyA="NPC R Breast" bodyB="NPC R PreBreast">

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint>

<generic-constraint bodyA="NPC L Breast01" bodyB="NPC L PreBreast">

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint>

<generic-constraint bodyA="NPC R Breast01" bodyB="NPC R PreBreast">

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

</centerOfMassTransform>

</bone>

<generic-constraint bodyA="NPC L Butt" bodyB="NPC L PreButt">

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint>

<generic-constraint bodyA="NPC R Butt" bodyB="NPC R PreButt">

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint>

<per-triangle-shape name="UNP TM">

<no-collide-with-tag>body</no-collide-with-tag>

<no-collide-with-tag>ground</no-collide-with-tag>

<weight-threshold bone="NPC L Breast">0.1</weight-threshold>

<weight-threshold bone="NPC R Breast">0.1</weight-threshold>

<weight-threshold bone="NPC L Breast01">0.1</weight-threshold>

<weight-threshold bone="NPC R Breast01">0.1</weight-threshold>

</per-triangle-shape>

<bone-default>

<margin-multiplier>0.1</margin-multiplier>

</bone-default>

<bone-default>

</centerOfMassTransform>

</bone-default>

<bone-default>

<margin-multiplier>0.2</margin-multiplier>

</bone-default>

<bone-default>

</centerOfMassTransform>

</bone-default>

<bone-default>

<margin-multiplier>1.0</margin-multiplier>

</bone-default>

<bone-default>

</centerOfMassTransform>

</bone-default>

<bone-default>

</centerOfMassTransform>

</bone-default>

<generic-constraint-default>

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint-default>

<generic-constraint bodyA="SR1" bodyB="SR0"/>

<generic-constraint bodyA="SL1" bodyB="SL0"/>

<generic-constraint-default>

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint-default>

<generic-constraint bodyA="SR2" bodyB="SR1"/>

<generic-constraint bodyA="SL2" bodyB="SL1"/>

<generic-constraint-default>

</frameInB>

<useLinearReferenceFrameA>false</useLinearReferenceFrameA>

</generic-constraint-default>

<generic-constraint bodyA="XFL1" bodyB="XFL0"/>

<generic-constraint bodyA="XFL2" bodyB="XFL1"/>

<generic-constraint bodyA="XFL3" bodyB="XFL2"/>

<generic-constraint bodyA="XFL4" bodyB="XFL3"/>

<generic-constraint bodyA="XFL5" bodyB="XFL4"/>

<generic-constraint bodyA="XFL6" bodyB="XFL5"/>

<generic-constraint bodyA="XFL7" bodyB="XFL6"/>

<generic-constraint bodyA="XFL8" bodyB="XFL7"/>

<generic-constraint bodyA="XFR1" bodyB="XFR0"/>

<generic-constraint bodyA="XFR2" bodyB="XFR1"/>

<generic-constraint bodyA="XFR3" bodyB="XFR2"/>

<generic-constraint bodyA="XFR4" bodyB="XFR3"/>

<generic-constraint bodyA="XFR5" bodyB="XFR4"/>

<generic-constraint bodyA="XFR6" bodyB="XFR5"/>

<generic-constraint bodyA="XFR7" bodyB="XFR6"/>

<generic-constraint bodyA="XFR8" bodyB="XFR7"/>

<generic-constraint bodyA="XBL1" bodyB="XBL0"/>

<generic-constraint bodyA="XBL2" bodyB="XBL1"/>

<generic-constraint bodyA="XBL3" bodyB="XBL2"/>

<generic-constraint bodyA="XBL4" bodyB="XBL3"/>

<generic-constraint bodyA="XBL5" bodyB="XBL4"/>

<generic-constraint bodyA="XBL6" bodyB="XBL5"/>

<generic-constraint bodyA="XBL7" bodyB="XBL6"/>

<generic-constraint bodyA="XBL8" bodyB="XBL7"/>

<generic-constraint bodyA="XBR1" bodyB="XBR0"/>

<generic-constraint bodyA="XBR2" bodyB="XBR1"/>

<generic-constraint bodyA="XBR3" bodyB="XBR2"/>

<generic-constraint bodyA="XBR4" bodyB="XBR3"/>

<generic-constraint bodyA="XBR5" bodyB="XBR4"/>

<generic-constraint bodyA="XBR6" bodyB="XBR5"/>

<generic-constraint bodyA="XBR7" bodyB="XBR6"/>

<generic-constraint bodyA="XBR8" bodyB="XBR7"/>

<per-vertex-shape name="Foot:Body 1.002">

<tag>skirt</tag>

<no-collide-with-tag>hand</no-collide-with-tag>

<no-collide-with-tag>skirt</no-collide-with-tag>

<no-collide-with-tag>hair</no-collide-with-tag>

<no-collide-with-bone>NPC L Forearm [LLar]</no-collide-with-bone>

<no-collide-with-bone>NPC R Forearm [RLar]</no-collide-with-bone>

<no-collide-with-bone>NPC L ForearmTwist1 [LLt1]</no-collide-with-bone>

<no-collide-with-bone>NPC R ForearmTwist1 [RLt1]</no-collide-with-bone>

<no-collide-with-bone>NPC L ForearmTwist2 [LLt2]</no-collide-with-bone>

<no-collide-with-bone>NPC R ForearmTwist2 [RLt2]</no-collide-with-bone>

<weight-threshold bone="NPC L Breast">1</weight-threshold>

<weight-threshold bone="NPC R Breast">1</weight-threshold>

<weight-threshold bone="NPC L Breast01">1</weight-threshold>

<weight-threshold bone="NPC R Breast01">1</weight-threshold>

<weight-threshold bone="NPC L Thigh [LThg]">1</weight-threshold>

<weight-threshold bone="NPC R Thigh [RThg]">1</weight-threshold>

<weight-threshold bone="NPC Spine [spn0]">1</weight-threshold>

<weight-threshold bone="NPC Spine1 [spn1]">1</weight-threshold>

<weight-threshold bone="NPC Spine2 [spn2]">1</weight-threshold>

<weight-threshold bone="NPC Pelvis [Pelv]">1</weight-threshold>

<weight-threshold bone="NPC L Clavicle [LClv]">1</weight-threshold>

<weight-threshold bone="NPC R Clavicle [RClv]">1</weight-threshold>

<weight-threshold bone="NPC L Butt">1</weight-threshold>

<weight-threshold bone="NPC R Butt">1</weight-threshold>

<weight-threshold bone="SL1">0.1</weight-threshold>

<weight-threshold bone="SR1">0.1</weight-threshold>

</per-vertex-shape>

<per-vertex-shape name="Foot:Legs:3">