Boni posted at 1:05PM Mon, 31 October 2016 - #4288368

I personally don't use the DIM ... but you can direct where all your files are installed based on whether it is Poser or DS ... or at least 3 years ago when I used it regularly it did. I am not up to date as I am now by personal choice primarily a Poser user. Someone more up to date can help you with this .. and please. Let's not have a software debate, just the facts. Ok?

Have you spent 1 - 4 hours a day for 6 months trying to figure the best way to use the golum and associated products in Poser? I have.

It isn't a software debate Boni. It is an accurate statement of what happens when you have more than a handful of native DS items. Do you think I liked having to come up with the setup I mentioned above? The DIM is why I ended up reworking all of the subfolders.

As of today, I have 1,042 packages (according to the very appropriately named DIM) installed in DAZ's default layout (99% are genesis 1 & 2 - a couple of V4 products may have slipped thu ). It is breathtaking how many subfolders have only another subfolder in it, along with how many products are unhelpfully hidden away inside of an ego subfolder. Unless the enduser takes active steps to bring order, they will spend most of their time blindly drilling through subfolder after subfolder, looking for a product they know they have purchased.

Every genesis product install is a snowflake, Male_M3dia's poor attempts a deflection won't change that - every single install is different, and unless the enduser memorizes what every single product goes with, they are going to have to do cleanup to actually find the products they purchased.

One other piece of advice - Poser Companion Files - I have over 1000 DS packages installed - Not 1 product has all of the PCF files in the correct folder. Not 1.

I'd also recommend resaving those out as Poser native files.

The DAZ vendors could do it (and a couple do provide native Poser files for their Companion Files), but for the most part they don't. It only takes a couple of seconds, and once you have done it, you have even less need to use DSON while in creative mode.

The add-on framework in Poser isn't really designed to do the kind of heavy lifting that DSON requires. This is an issue with Python, not Poser (or DAZ, for that matter) - Python is 32-bit (with the 2GB per process limit - this is why Poser slows to a crawl when using DSON - EVERYTHING has to go through that 2Gb, unless you save stuff out as Poser native) and the folks that maintain the Python language aren't doing very much to migrate it to 64-bits. Not surprising, Python is designed to be a light weight scripting language.