Jump to content

Issue With DD Device: Chastity Corset


Recommended Posts

I have also CBBE. Was there an update for DD recently? I remember i had this problem after i added a patch for corset & belt (in the last public release for certain corsets & belts it would CTD if combined) buried somewhere in a thread. I could build the patched files in bodyslide but i don't remember how, it's possible those don't appear in the groups, possibly you need to look for them in unassigned or manually add them via group manager or something.

Link to comment

ok for CBBE there was a patch made for an issue with belt and corset but i do not know where to find it, however it was fixed in the development builds

(links below DD Assets, DD Intergration, and DD Expansion).

 

https://github.com/DeviousDevices/DDa/tree/Development

 

https://github.com/DeviousDevices/DDi/tree/development

 

https://github.com/DeviousDevices/DDx/tree/development

 

when you go to the links make sure that the branch is listed as development (it should be but make sure). this is on the left side of the screen.

then click the green button on the right (clone or download) and download the zip files.  all you need from the downloads is the Bodyslide files.

you will have to open the zip files and copy the bodyslide files into your Bodyslide installation and let them overwrite what is already there,

then just run Bodyslide and rebuild all the DD stuff (if you do a batch build it all has a prefix of DDA for assets and DDX for expansion), and make sure

to build the stuff for your bodytype (CBBE right??).  some of the items are the same for both bodytypes and will list both bodytypes on the same item.

 

hope this helps

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use