I find the DAZ installers much easier for me to use. I went to download some stuff I hadn’t downloaded yet from my account and all I see is Zip files. DAZ, PLEASE bring back the DAZ installers! With the DAZ installers, I can easily access my stuff. For example. If I want to load up hair, I load it up and then I see Materials right there right next to the file where I loaded my hair and I can click on it to see what colors to color my hair. Not so with these dumb ZIP files. Now I have to go to two completely different areas in my Runtime which is tedious and unneccesary. PLEASE bring back the DAZ installers! I never had this problem ever since Genesis came along. Now everything installs where I don’t want it to be.
I hear you Knight.
I liked the old installers. A couple clicks and you’re done. Perfect.
But so many other people said they couldn’t get the installers to work at all.
I hate ZIPs, but I guess now everyone can buy and USE the products now.
...my issues with some of the older installers was how they often made a mess of the Studio/Content folder which, unlike the Poser Runtime was also very poorly organised to boot. There would be folders in the tree like Data, Templates, and even Readme which showed in the Daz/Content tree in the application. Sometimes a prop was in “environments” sometimes an environment set was in “props”, sometimes Daz lights were under a vendors name, or some other unrelated folder instead of the “lights” one.
A lot of this had to do with sloppy packaging. For example, the Woodland Realms Playset 1 had an issue with the texture files installing to the wrong subfolder in Content/Runtime/Textures. This had to be manually moved to the correct location (after noting down said location from the “Can’t Find…” error message that would appear when one attempted to load the set).
With later content installers, much of this was cleaned up, particularly when there was no longer the need to separate Poser & Daz shader files.
I originally had no issue with idea of moving to .zip archives and even welcomed the change as I have a custom setup and actually preferred the drag & drop method since it gave me full control where everything went according to the instructions given. If something was amiss (which BTW never occurred with Rendo, RDNA or Xurge content), it usually meant I accidentally dropped it in the wrong folder (usually the one just above or below). Easy fix.
So I was all ready for the change, until 4.x and Genesis, which introduced entirely new layer of locations to deal with. Content/plugins specifically for 4.x and Genesis had to go into separate folders to work correctly. Ok so a few more steps but as long as there are good instructions as to what needed to go where, it was a minor inconvenience. Oh wait, there’s this thing called the CMS and Smart Content I have to be concerned about that rely on the Metadata files to work. Say what? You mean I need to suddenly become a DB manager as well and make sure the database is up to date so I can find things?
It was one thing to organise my caddy in the painting studio at college, Brushes here, paints there, mixers and medums in that drawer, etc, but now one misplaced piece of data and, “hey, where’s that dress I needed for Leela that I just bought?”.
Finally, along comes the DIM, an automated download and install tool (which by the way was in beta development) which just made things even more complex than they needed to be. Now I have to mess with setting all these filters, paths, library sets, get it to properly recognise my username, etc, etc, etc.
So back to the ol’ drag & drop again, until…
...whaddya mean there’s no readme.txt? Just about very .zip content file commercial and freebie I’ve ever installed before Daz changed to the installer format included a readme.txt. Where is some of this 4.x/Genesis stuff supposed to go so it doesn’t break when I try to load it? The ,exe installers used to handle all this for me, now unless I use the DIM (which I still am unable to get working properly), I have to guess at where to place things, and if I guess wrong I have to go back take it all out and all over try again.
A well organised runtime is the best means of content management especially if it is geared to one’s style of workflow. It’s not rocket surgery and doesn’t requires some background process to work. As long as the critical components like Data, Geometries, and Textures are in their proper locations there should be no path error issues.
The bottom line is, why is it so hard to simply distill the these instructions into a readme.txt that is included in the archive package? It would make this process so much simpler for those who choose not to, or cannot, use the DIM.
If that’s not to be, I’m with Knight22179 and tsarist: bring back the Daz installers.