Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Yeah, but shouldn't QA be fixing that? If the creator has created folders called "Female -> Acesoriez -> Joe Blow -> Green Necklace", shouldn't QA be renaming them "Genesis 8 Female -> Accessories -> Correct Product Name that is the Same as the Store"
The "scattered all over the place" discussion was, I thought, in reference to folders that are incorrect. I have absolutely no problem with creators who can't spell, or don't speak English at all, because that is something that QA should be fixing before it hits the store (or the creator's testers ideally, as QA should be the final last step, not general testers). From my understanding, QA is a small team, so yes, mistakes can be made especially when the pressure is on and they have a queue to work through - but incorrect folder names should not be slipping through as they are glaring mistakes (and that dang "lost and found" metadata should never ever have any reason to be used, so that one is totally baffling).
Yay! I finally managed to access my old hard drive and I found the manifest files folder.
So question: if I copy that manifest files folder over to somewhere on my new computer, all I should have to do is point DIM towards that new location and it'll see all my installed stuff (which is on an external drive)? That is correct? And the best location for the manifest files would be to put it with the DIM install folder?
Hmm, what is the "content cluster" folder? I haven't noticed that before?
Yes. Create a folder inside the DIM install folder called Manifest Files and put them there. Be sure there is nothing else in that folder. Then point DIM to that location. As for the content cluster, I really don't know. I have never futzed with it.
you need to edit the address to the installed files so DIM knows they exist. go to the PARENT folder so it see's everything "My DAZ Library" My Library is a sub folder within unless you moved it.
"My Library" should not be a sub folder of "My Daz 3D Library".
Lost a 1 year old Falcon build with 2 titanx Pascals, and since have two other new builds , so I've done this multiple times. I found it best to do the following. First off take screen shots as you go and save them in case you do things right and need to refer to this in future, (or use mine) and also to trouble shoot if you mess up (always fiixable).
Duplicate the manifest folders (make a copy/backup-see screenshot on far right below) and save the bup copy where it will be easy for you to find). Also find and copy-backup the Account file before you mess with it. Then copy the the real-working manifest file wherever you want it to lurk. Open the account file in a text file. Change paths lines referring to paths from old to desired. For me it was off of the c: drive because I was sick of doing this. I also do not use the word library at all. Daz doesn't care what you call the folder as long as it and DIM can find it.
Change only the drive and path (no other data) by finding the line that reads: DownloadPath= (from old path to new path). Also change paths below it that refers to current drive etc. Also change path for Installed Path. Not all paths are highlighted on screenshot so find old path by searching yhe phrase Path=
oops your right its "Studio"
Same here. Content previously downloaded to external drive plugged into new pc, but DIM can't see it and thinks I have nothing installed.
I cringe everytime I upgrade my computer as I do the hardware upgrades myself. The insane and most diificult part is not upgrading the hardware BUT migrating my DAZ content. I have well over 100,000 Photshop files in my Lightroom catalog. Migrating my Lightroom catalog is simple and painless. I also have a large library of 3D content for 3D Coat & also for e-onsoftware's Vue. Again a rather easy task. I have several runtimes for Poser Pro. Again it's easy.
BUT migrating my DAZ content is a BIG & difficult task. And there is NO REASON why it has to be. DAZ with it's insane databases has made this task WHY too difficult. DAZ needs to simplify the task.
I too went through the same issue as the OP. I moved over the database files and still every thing I had installed on my external drive did not show up in DIM.
The only fix was to go through the insane task of reinstalling stuff I already had installed.
DAZ PLEASE resolve this issue. Make it simple. Please!!!!
Are people suggesting that after downloading and install products from the online store, that the downloaded files and associated manifest files can not be deleted or moved from their downloaded folder?
The downloaded files can be deleted or can be retained - it makes no difference to DS, but does make reisntallation easier if they are kept (space permitting).
How about the manifest files?
All I'm saying is that the manifest files need to be kept and put somewhere, where you can then point DIM towards so DIM sees all your installed content.
Note that there are two different types of manifest (.dsx) files with the same file names - those that accompany the installer zips and which can be deleted together with them after installation, and then those in the ManifestFiles (default name) folder which DIM use to keep track of what is installed and therefore should not be deleted (and preferably backed up like other important files).
So kindly allow me to wrap my mind around this.... SO Daz Studio and DIM both use separate database systems? Why not use the same databases?
Has DAZ NEVER heard of relational databases. I did database programing (Clipper) in the 1980s and early 1990s. Surely this can still be done today!
So what exactly should be backed up (DIM & DAZ Studio) to assist suers when moving to a new computer?
AND sorry, I do not mean vague stuff like your DAZ database or your MANIFEST files. I mean exactly what files? What are their exact names and what folders (complete file path) are they located.
DAZ should provide information on stuff like this to assist their customers making transitioning to a new computer less painful.
In Lightroom all that is required is to backup a single database file.
DIM, Central, Connect and Studio all use the same database. They do not share configuration data.
So these ManifestFiles are not database files but configuration files?
Where exactly is this database located Ie: file path ?
What is the file name of this database?
Sorry, I'm not trying to be rude but vague responses will not assist anyone who has or had this issue.
Exact names and file paths would greatly assist.
Is there no DAZ documentation on moving conent to a new computer (steps to be taken, required files to be backed up, etc)?
Cheers & many thanks...
The database files (multiple) are in the Content Cluster directory, by default
%AppData%/daz 3d/cms/contentcluster/
but you can configure it in DS in Edit>Prefrences>cms settings or in the Content Directory Manager, or in DIM's advanced settings.
If you open the manifest files and look at them you'll probably figure out what they do, there are actually three types as there also is one in the zip. They're not config files as such (at least I wouldn't call them that) but contains data about the products and where they are installed, so DIM can keep track of what's installed, where, and which version.
Keeping everything in the database is not always the best solution, writing files to disk can be much faster than writing the same data to a database for example, each have their advantages depending on the context.
The CMS has files in several places, here are some paths, there may be others:
C:\Users\[user name]\AppData\Roaming\DAZ 3D\cms
C:\Users\[user name]\AppData\Roaming\postgresql
C:\Program Files\DAZ 3D\PostgreSQL CMS\bin\pgAdmin3.exe
The last path is to the admin app, here's the login data:
Name: dazstudio
Host: localhost
Port: 17237
Service:
Maintenance DB: postgres
Username: dzcms
Password: anything/nothing
Writing an entry to a database file is also writing to a disk file unless the db file is loaded into RAM but will be writen to disk once the db is closed or an event is triggered. So you point makes no sense.
My ContentCluster folder has 1,323 files and 21 folders. So are ALL of those files database and index files?
If not please post the exact name of the database and index files.
Again vague information is not helpful
It depends on the context I guess, I tested it a while ago and found it much faster to store certain data in flat files on disk than with SQLite. And it's often much simpler:
https://www.hanselman.com/blog/cloud-database-nosql-nah-just-use-csvs-and-csvhelper
Then if a database file is not written to disk, kindly explain how a database file is saved to your hard drive?
Thanks kindly for posting this info. It's much appreciated. It appears the database is quite a mess.
The database for Adobe Lightroom is a single catalog file. And there is an option in Lightroom to have this database backed upon existing Lightroom.
Why can not such an option be offered in DAZ Studio or DIM?
If they ALL use the same database then why does DIM require separate ManifestFiles?
It's 6.53 (feels like:5:53) in cold California, and although I've only had two sips of coffee, I'll give it a feeble go (big grin). Answer number one: DIM can be used to keep a second offline machine up to date via the manifest files and a portable external drive of DIM downloaded products/updates. In my mind, it's sort of like coding in PHP MySQL and JavaScript. JavaScript (client-browser side) is separate from PHP (server side) and runs after a server responds. Often it produces content stored in a database (MySQL or other). You cannot run PHP functions from JavaScript nor vice versa. The two are seperate animals, and the run times do not overlap. AJAX is simply a JavaSript driven request but it does create run time (execution) overlaps. In my mind the manifest file is much like using AJAX, it's useless withoutJavaScript, useless without a server, (JavaScript does not need a server) but it is a developers dream, and makes multitasking easier.
Answer B: Because the DAZ universe gods on Mount Olympus Kings Peak decided it would be so and bestowed a manifest file upon us.
Answer C: Manifest files are frequently used to keep track of contents. The pirates had one to keep track of crew and cargo loot. Kindle has one for eBook metadata but the book lives in a database. Software typically has one, to keep tyrack of metadata licenses and versions. It keeps track of those things and which updates are needed per user.
Lightroom writes metadata for each file that is edited via Lightroom or Camera Raw. The metadata is saved in the same directory as the photo.
When I backup my photos to an external drive, my metadata is also backed up.
So the only database file I need to backup is my LR catalog db. Which LR gives an option to occur whenever I exit LR.
WHY CAN'T DAZ do the SAME?
But this current system does not make it easy for users to upgrade their computer, replace an hard drive or install a secondary hard drive. Thus it FAILS!
Things should be made easier for the consumer, not more convoluted.
I've asked a few times exactly what files need to be backed up.
The only replies (for the most part) have been vague responses.
I am not anit DAZ. I think they run a fantastic market and awesome sales. I gladly pay my Premium membership.
However there are somethings which I shake my head at and this database mess is one of them.