Oh, I see. So its basically like taking an old Descent II HOG or MN2 file, with the exception that a DAZ project can have many more components, and breaking it up into an insane number of separately editable files, sub files, etc. Its good to hear that you don't have to figure out where everything goes. Beyond that, when does the file structure become an issue? It sounds like it was necessary for you to spend some time learning and navigating their file system in order to accomplish some of your projects.

Well I got Daz 3d installed on my system and fired it up without any errors or problems. I guess the filing system they use really won't be an issue unless I try to install something manually. Now comes the fun part of watching videos and learning how to use it. =|
On a side note, their forums seem kind of dead compared to here.

Sorry -- might have missed this.  I've been a *touch* busy for the last week or so <g>.

I've had to learn the structure because my routines in Blender that import all the rest of the files needed in iClone have to understand where those maps are located.  And the other thing that almost anyone will need learn is how to actually find your content.  It's stored in strange places sometimes, most likely due to lack of standards among their 3rd Party Devs.  So you might be looking for a nightclub in the "Environments" folder when it's actually in Props (?).  Or perhaps you think a character you want would be in the character folder -- but it's actually in a sub-folder of characters.  

You'll learn and when you don't know you ask (that's what we're here for).

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley