SOLVED - Anyone else having DIM troubles today?
1st - I picked up a bunch of stuff in the PC anniversary sale, so thank you very much Daz.
However, and this is a big however, when I went to the DIM to install my purchases, I left, and when I came back, the DIM was uninstalling lots of my content. Now, my first thought might be that I inadvertently hit uninstall instead of install - except some of the DIM settings had changed. For example, I had hidden Bryce-related content, but now it was not hidden.
Now, I have been tryng to reinstall my content, and the DIM stops whenever my screensaver starts. Furthermore, it uninstalled Carrara, and even though I have reinstalled Carrara, it won't load. It is hanging in the startup and says (not responding).
See attached
Comments
I've been using DIM heavily on PC Sale stuff and all the updates Jen has been doing, without problems. Is it possible you have hard drive corruption? Your settings should be in an .ini file in C:\Users\[username]\AppData\Roaming\DAZ 3D\InstallManager\UserAccounts (on Win7) -- if you haven't tried to save changes (or you have and they aren't taking), we can see if that file is corrupt.
Thanks for your quick reply. Well, now I have uninstalled and reinstalled Carrara and its related content - it is up and working again. The other content that DIM had uninstalled, I have reinstalled. A few tests have shown that it is working so far, except....
When I open a Genesis 2 Female in Studio or one of its characters I get a "duplicate formula" error." See below. The character does load in Studio even though there is the error message. I do not get this error for a regular Genesis, Genesis 2 Male, or one of their characters. For the G2F, I get that error in Studio, but not in Carrara.
Did you have, and install a recent update for, Growing Up for G2F? If so you are seeing a problem caused by "left-overs" from the old version that DIM, or a manual install, won't have tidied up. I would remove the \Data\DAZ 3D\Genesis 2\Female\Morphs\Zev0\Growing Up folder and then reinstall the product
Thanks, Richard. That seems to have fixed it.