this DIM version is broken.
support will dance around this reality in the forums, but somebody in back knows.
test the next one better guys/gals. it’s a good tool when it works.
Broken how? Generic complaints with no supporting information cannot be fixed - and as a former sysadmin/software support type, this kind of statement gets dumped into the trash without a bit of remorse.
Operating system? What is failing - download? Install? Path Setup? Any information in the log? (Click on the gear icon, top right, and then ‘view log’, bottom left - scroll to the bottom for the most recent information).
The only problems I’ve had so far have all turned out to be self-inflicted - and fixable, once I figured out what I’d done wrong.
Give us something to work with, and we may be able to help.
Sure - I’m glad you fixed your self-inflicted problem.
To wit - while less-than-useful, my in-transit post was written to save others some needless hair-pulling.
Technically, this has all of the symptoms of a permissions problem that isn’t seen with simple content installs, but cripples folks with plugins and other default base-directory install packages, as this version of the DIM will happily install content in a non-system area (like a ‘D:\’ drive), but it will not install anything in either of my 32/64 ‘program files’ directories, which is pretty basic to making a complete installation from scratch - given plugins, etc.
From a cold-boot start-up and DIM open, any attempt to install anything that goes under the default ‘program files’ space, is met with the new-to-me-with-DIM, but-not-uncommon Windows7 “must be done by admin, continue?” dialog (I say “OK”), then DIM fails with no message, and the ‘install failed’ label on the button. The generic logs indicate a process dying.
After numerous experiments, every-so-often, a rational pop-up log is presented indicating a failed attempt to install things in what are auditably rational and existing (but protected) ‘program files’ sub-directories. But that dialog appears inconsistently at best, and its messages aren’t obviously available for post-mortem analysis, and aren’t in the default DIM log that I can find.
Again, this is as COTS an install as is possible, other than the content being set to a D:\ drive location, where it happily resides and is maintained.
Given this apparent permissions constraint, DIM will also fail to install Bryce, Carrara, Photoshop, and Vue content/plugins under their respective default base installation directories as well.
Info for the ‘folks in back’, this is a completely fresh COTS Win-7 x64 patched install, w/ Daz products being the *first/only* products installed up to the point of the error. The download directory (zips and dsx files) is on a network mounted drive (mapped as a lettered drive). My previous (pre-disk-crash) installs (from the first DIM version released, and all follow-on versions) had no problems with this install model - just this newest version.
Final hint (where I’d start to look) - once the DIM process requests and becomes privileged, I believe it can no longer read the network source drive (theory). This would account for much of the DIM confusion and mixed messages. Given the history of it working in the past, I’ll let Daz try to fix it first, before I muck-up my in-house permission schema.
Perhaps related to a recent windows security patch, or a code problem in the DIM. Don’t know, don’t really care, so long as mere-mortals don’t get all bent fixing a problem that likely isn’t theirs to fix.
A simple test would be to remove and re-add a system plugin (mimic-live, etc.) and see if it re-installs OK.
Lastly, you may notice that I’m generally pretty ‘short’ with Daz. They went from a great small company to a POS corporation, and are slowly pulling it back together. If I’m bothering to write something in these forums, it’s likely I’m pissed. I don’t have time or inclination to pussy-foot around BS anymore, and this place was thick with it not-so-long-ago. Walk a mile in a man’s shoes before responding to this point.
And for god’s sake, don’t even think of preaching at me to open up a ticket. This is as much of my life as they get. They know what to do from here.
DIM has a problem. I expect Daz folks will fix it soon. I wait with optimism, but little patience for BS. And my Daz products are functionally ‘Down’ until they fix this. But it’s all good, my fresh Poser and Vue installs are working fine… Plenty to do.