willdial posted at 8:35PM Wed, 22 June 2016 - #4273016

It looks like we need to create a tutorial on DAZ library and asset structure. Basicly, the data folder is like a geometry folder. But, the data folder hold morphs, UV info, and other stuff. A Content folder contains a Runtime folder. I have a Poser 11, Poser Pro 2014, Poser Pro 2012, and Poser 8 Content folders. Daz Studio puts its stuff into the Content folder.

For DSON Importer to work well, both Poser and Daz Studio need to be mapped to the same Content/Runtime.

I've already written one (with pics & checklists) a while back; I'd been working on it for the Genesis in Poser thread over at DAZ. I stopped development on it when DAZ permanently banned me from their forums.

I'm at momma's house for another week, but if there is interest, PM me after July 1.

P.S. Why do you guys insist on using DSON? It isn't the best way to use DS assets.

It will never be recompiled to run as 64-bit, and as such, you will always hit the 2Gb per process limit. (This is why g gets balky when you have more than 1 dressed figure in a scene)

It is so much easier to simply export out the g line as a Poser native figure. Mine only use 80Mb per figure. It isn't that hard once you bring a little organization to the abortion that is the DS file structure.

Did I mention that it doesn't take much to convert PCFs to Poser native Poser files? Again no need for DSON. It only takes about 5 minutes & it certainly speaks to the laziness of DS vendors that don't take the time to do it.