I just wished they had used the word “NEW” instead of DIM ... it would make for less confusion.
I just wished they had developed an automatic installer that was compatable for all the programs this sites supports, gives you the option for selecting those programs, and actually installed the files IN those locations used by the programs….in other words: an installer that WORKS!!
Recently, I got PoserPro 2012. I didn’t want to import the Runtime from my old Poser—it’s a mess due to years of accumulation of items that are good only for non-commercial use mixed in among the stuff that’s useable in commercial works. What I did like with DIM was that they’ve begun to catagorize items—much like I’ve been doing with my stuff to keep the Mega-Gig-sized folder from crashing Poser, but the arrangements are significantly different from my way of doing it. I figured it’s much easier to restart with a new, slicked out folder using their catagory scheme than to resort all my crap to match theirs.
Taking that opportunity, I also wanted to do a clean sort of the D|S runtime folder, for the same reason. So I set up the new install locations, clear out D|S, reload the D|S & PoserPro as clean loads and got busy with DIM.
One thing I noticed was DIM seems to be desiged to cater only to D|S—there is a checkbox for loading into P9/PoserPro, but no options for pointing the installer to the Poser runtime—it only gives the option for the D|S runtime folder. “Fine,” I sigh. After DIM was finished, however, somehow everything showed up in my PoserPro runtime, absolutely nothing in the D|S folder! “WTF?” Wierd, but PoserPro works fine now….
.....Then I discovered an interesting feature; I recently got a morph for the DAZ Horse 2. “Great!” I thought. But when I installed, I saw it was a D|S-only morph—PoserPro can’t see it. “Okay, I’ll just use D|S”—so I start it up, found the Horse 2 in the list, go to load it….only no horse!! there’s some corruption of the install that I’m only getting some boxed-bodyparts figure of the horse…“WTFW?!?!?!?”
I think DIM is using quantum-computing for the install—our files are in a state of both there AND not-there for Poser & D|S—until you actually look! Then, the cat dies or lives depending on the observed state of the other program…..