Although with the way so many are used to running very customized runtime setups I have a feeling many will opt to download files manually from the Product Library.
You can just use DIM to download.
The point wasn’t about how to download though it was about trusting the DIM to install for you. So yeah you could use DIM to just download but I’m inclined to believe that if it’s an issue of having control as I suspect it is for many, then they’ll be more inclined to use the Product Library. Now if the day comes that the Product Library option is taken away from customers then those people may start using DIM to download but I suspect the type of people I’m talking about will resent being forced to do something differently then they used to be able to do and preferred.
The down side is that so far the DIM doesn’t appear to be using any quick way for users to determine if they in fact have the latest version and this will be very frustrating for those same folks who like to do things their way.
Do you mean if stuff they installed with the old installers is up to date? Yes, a perpetual problem. What I’ve done is install using the installer and the DIM zip to dummy locations and compare them—found quite a few updates I didn’t know about. After that, you can either (a) install to a dummy location with DIM—you can then delete the dummy location and DIM will still know if you have the latest, or (b) keep the downloads in DIM’s download folder. Either way, DIM will then let you know if there are updates.
Not necessarily stuff that is installed. To illustrate an example I’ll talk about how I used to do things and how this impacts me. Every so often things happen that I have to rebuild my runtime. I like to have just one central runtime under poser although another runtime is created for Studio. I rarely use that though since most of the time when I use Studio I can just access things from the Poser Runtime with Studio (after I’ve let Studio look on my drives for content). Given the size of my collection and how big my runtime gets with everything installed I’ve not been able to find an affordable effective way to back up my runtime. So whenever I rebuild a runtime or used to before these changes, I’d compare each items installer with the file sizes that used to be listed on the product pages. If they matched I’d install what I had and if they didn’t I’d reset the download on that item because it had been updated. Now it’s a hassle to have to do it this way but Daz stopped notifying customers with emails about updates, then they stopped automatically resetting downloads for updated files, then they stopped having a sub forum specifically for notifying customers of updates (all three methods of which were preferable to how I had to do things and/or the method you’re suggesting above). Now yes one could do as you suggest but it’s a lot more work and greatly slows things down. The way I used to do things (going to the product page and comparing file sizes before installing) slowed things down a lot too causing it to take me months to rebuild a runtime complete. The way you suggest is much slower because of the process of installing to dummy folders before comparing and would likely increase the time to rebuild my runtime from months to more then a year and likely by the time I finished a number of the items would likely have been updated again. Really the best solution though would be for Daz to come up with a new way of doing things such that every time they update Studio or improve Genesis they don’t create a need for so many products to have to be updated to keep working. Before Studio 4 and Genesis this almost never happened and updates were mostly to fix errors in products that should have been caught before release but weren’t. I never had to update Victoria 1,2,3 or 4, Michael 1,2,3 or 4, Freak, David Stephanie, Aiko, etc just because a new version of Poser came out.
If so then Daz will start hearing a lot of complaints soon if they’re not hearing them already. I don’t see why it should be an issue and daz couldn’t just use the same naming convention before which did indicate version number, I mean all you’re doing is changing the file extension from .exe to .zip
I’ve asked for this, although given how rife with errors the file naming approach has been, I’m happy to have DIM’s checksum-based system.
I’d be happy with a checksum-based system too if I could also visually tell version numbers by looking at the file name. I’m sorry but Daz has had too much trouble with things that were supposed to work a certain way but didn’t for me to completely trust the accuracy of DIM.
As to the issue you had yeah the DIM only handles content which is best since people also like to have control over where programs are installed for performance reasons. Also as I understand it the DIM is currently only installing Daz Studio and Poser content and that for now it won’t install content for Carrara or Bryce.
Near as I can tell it sounds like DIM still is having issues with Carrara and Bryce. I certainly don’t get the impression from that change log that it’s ready for prime time with those programs. Besides many of the old installers didn’t properly install things in Bryce and Carrara to where they would work without the user having to do things first (import materials and objects into presets in the case of some Bryce files and some shaders and objects also had to be imported in the case of Carrara) so if the files have been simply changed from exe to zip then even if DIM is now able to install Bryce items it wouldn’t do it correctly without requiring further user intervention. Which might not be a problem if one just had a handful of files but when one has hundreds of files it is a problem, a big problem.