Moving DIM package directory?
I'm in the process of reinstalling my computer (either to fix an issue, or rule out a possible cause), and as part of this I've got a lot of set-up to do.
Fortunately, the OS drive I'm rebuilding doesn't have any of my DS content on it (just the main DS program), so I haven't got to install everything all again, but I have got to relink libraries and such.
However, as one of my data drives is getting pretty full, I'd like to point DIM at one of the drives that's got my downloads directory backed up on it - as is, I've got copies of the packages on three different drives, which is excessive for something I could theoretically redownload if desperately needed. (Particularly as one of those copies is on the same drive as my library, so it's not a meaningful backup if the drive packs up).
The problem is that simply changing DIM's package folder causes DIM to think none of those packages are installed, and I don't want to have to run through installing them to convince it otherwise. What do I need to do to be able to point DIM at a new location (containing identical copies of the packages for the location it was in) and recognise that packages of those names are already installed?
Comments
I have to change my DIM download directory periodically because DIM apparently doesn't know how to install programs and plugins when your content downloads to a NAS. I've never had a problem with DIM thinking my content wasn't installed when I briefly switch my download directory to root drive. Are your install directories set up correctly? That seems to be how DIM knows which packages are and aren't installed.
The Package Archive only keeps a record of what was downloaded. You need to set your Manifest Archive (Installation settings) to point to the folder with the manifest (.dsx) files that were created when you installed the Products.
I have been downloading and installing DAZ3D content with DIM to an external hard drive (G:/ , 1 Tb). I also separately, manually download the DAZ3D zip files to an external hard drive (F:/ , 1.5 Tb). Weekly, I backup to my F:/ drive
My G:/ drive was only used for 3D content (Daz Studio, Poser, etc.). After several years, my G:/ drive was starting to get full, so I bought a 5 Tb external hard drive (H:/) and copied to it all of the content on the smaller G:/ drive. I then changed the drives letters in the Content Directory Manager from G: to H: and started using the H:/ drive. All of my content on the H:/ drive was seamlessly available in Daz Studio. The key is the manifest files.
If I have it set to point at my package directory on the E: drive, it knows that most of those packages are installed (there's a few I've not installed ultimately).
If I point it at the near identical folder on the G: drive (leaving the manifests directory untouched, which I have on one of my SSDs, because they're comparatively small and it speeds DIM up a lot), it starts populating the "Ready to Install" tab with everything it can find, unaware that these packages are installed.
Right - apparently if I let it get through that process (which is painfully slow with a library of many thousands of assets), it does eventually get its knickers untwisted and decide that the stuff is installed.