Quote - > Quote - The beginning to all these problems with Daz, the original canonical mistake, come from the installation process. The user don't know what that is installed or where it was installed. And now, when they finally are on their way to remedy this (why took it so long?), then they make the same mistake again, by not documenting the Dson installation process.

You are basically asked to transfer something you don't know what it is or where it is, convert it and place a new bunch of undocumented files somewhere you don't know.

 

Oh, god, this is so true. My reply may seem a bit off topic, but this also seems to cover the majority of newbie Poser problems as well.  (I don't think it's unique to DAZ). I sometimes think that actually installing the software -- and then the content -- is the hardest part.

Is it really that hard, if one sticks to the default install options, from day one?

A lot of the issues I have read, on these lines, seem to stem from people opting to customise their Poser program and separate content file installation paths?

There are some good reasons for doing this, I'm sure. But if you're not at least an intermediate level operating system user (e.g. on Windows, are you reasonably confident using regedit) its perhaps not such a great idea?

Regedit shouldn't be required of course! He he. Probably not a good benchmark of user advancement here...

But I guess, all Poser users must have run through setup (perhaps not the actual install, these days) for Windows or OS X. But how many can describe the file system layout of core operating system files?

Sorry don't want to get more OT here.

I guess the point you guys are making is that there should just be more detail in the readme about exactly what files install where, by default, for each part of the install... so that more advanced users can check this? (assuming there isn't more info tucked away in Daz's online readmes, that we all just glossed over)