I'd like to add that: Once our content is installed, if we go into the Installed tab - we can hover over a product to see which path it's been installed to, which is Very handy. There have been times when I was in a hurry while installing a lot of different content that has to go to different directories, and I made a mistake. So now I can't find the product I'm looking for - even though it's installed. I turn to DIM's Installed tab, locate the product and verify the path it was installed to. If I indeed made a mistake, I simply uninstall it, select the correct path this time, and install it again. Done. And done very Very quickly!!! :)
interesting, i didnt find what i was looking for but it was interesting. I am trying to find information about how to create Daz Installed Manager package from a zip file without any .dsx file.
@@xianzhu-jg7ck Which, the product I've linked in my previous reply? I'm not sure. I haven't tried it yet. If, however, you're asking if it's worth it to install to custom paths, I think the answer depends on how we like to work, and what we have available as far as purchased (or free, from someone else) content. In my situation, I started collecting content assets back when I was using Poser 5, and have been collecting ever since. So here's where the importance is for me: Around or before the release of Daz Studio 4.0 (first release) there was a clear separation between how content was delivered to the library depending upon whether it was Poser Runtime assets or Daz Studio Content. Install Manager as well as manual methods, we could still just install everything to one main path. But since the locations of assets for Poser and Daz Studio differ so much - and I have an enormous collection of Poser Runtime assets which is still growing as much now as it was then, I find it incredibly beneficial to divide all of my Poser format products into their own categories of Runtime structure: Environments - Holds not 'only' environments, but everything associated with them, like structures, furnishings and furniture, plants, rocks, etc., We could further divide that between genre - or even use "Sci-Fi", for example, as a category instead of "Environments" and put everything from Sci-Fi environments and vehicles to Sci-Fi weapons and props into this Runtime Structure - whatever system works best. The main point being to be able to find specific things when the list of what we have grows for years and years. The Daz Studio format is a bit different and, for me, is a Lot easier to just install everything into the same (I use default) library, and let DIM (Daz Install Manager) help us to sift through our purchased products. Of course, we could simply install Everything to the same library, since we can use DIM to help us find anything we own - which is nice too - so it really depends on how we like to work. I have a separate Poser Runtime for "Renderosity", which holds all of the Poser content I buy from them - making it really easy to locate my coflek-gnorg stuff, for example. Quite a lot of my Predatron content is now considered "Legacy", as it came out before Iray and uses the Poser Runtime structure. So I have a single runtime structure called "Predatron", where I can find all of his monsters, droids, animals, and people - which is Super handy for me. Dragons that are in Poser format all go to my "Dragons" runtime structure, making them very easy to work with. This may seem tedious, but once we start getting addons for everything that might have names and library locations that are not very obvious, having the runtime structures condensed to specific types of things makes all of the installed content a lot easy for me to find - which means that I'll actually use it a lot more often - because I can go right to it - even if the product name escapes me at the moment. Now, once I'm in Daz Studio, I can make any structure I what for my Content pane - organizing things just how I like it - so things that I use a lot and want quick access to (basically anything I spend time on making it the way I like it to be) I save as a Scene Subset (not Scene) which only stores the data necessary to load what I've created - leaving the original "Installed To" data untouched, so my saved Scene Subset is a tiny file, even if it loading something huge. I do this after I convert Poser format assets to Daz Studio and Iray. I could save the whole thing if I wanted to, but that dramatically increases the size of the library on the machine side of things, so I prefer to only save my optimized data. An example of this: Let's say that Daz 3D's Millennium Dragonling 2 is going to be a star in the production I'm working on. That figure is still in the older Poser format, with an option to also install the DS supplement. I load the Millennium Dragonling 2 directly from the Poser runtime "Dragons" and apply any of the presets from that library that I want for my young dragon. After I'm all done loading everything I need for this dragon from the Poser runtime, I convert the material to Iray shaders and tweak them to my liking, add any of my own custom dials that I demonstrate in my Dynamic Character Animation course, and then save this wonderful, Iray-optimized little dragon as a Scene Subset called "Imlofryrax" in my "Animals > Dragons > Dartanbeck" location of My Daz 3D Library. Now when I load that subset into any scene, I get everything I've saved in the subset - but the file that launches doesn't have to hold the actual heavy asset data, only the paths from which to load it - so it's a nice small file. Hmmm... I hope that makes sense.
I'd like to add that: Once our content is installed, if we go into the Installed tab - we can hover over a product to see which path it's been installed to, which is Very handy.
There have been times when I was in a hurry while installing a lot of different content that has to go to different directories, and I made a mistake. So now I can't find the product I'm looking for - even though it's installed.
I turn to DIM's Installed tab, locate the product and verify the path it was installed to.
If I indeed made a mistake, I simply uninstall it, select the correct path this time, and install it again. Done. And done very Very quickly!!! :)
interesting, i didnt find what i was looking for but it was interesting. I am trying to find information about how to create Daz Installed Manager package from a zip file without any .dsx file.
I haven't tried it, but I bought this which is supposed to do what you want:
www.daz3d.com/content-package-assist
@@Dartanbeck is it work it?
@@xianzhu-jg7ck Which, the product I've linked in my previous reply? I'm not sure. I haven't tried it yet.
If, however, you're asking if it's worth it to install to custom paths, I think the answer depends on how we like to work, and what we have available as far as purchased (or free, from someone else) content.
In my situation, I started collecting content assets back when I was using Poser 5, and have been collecting ever since. So here's where the importance is for me:
Around or before the release of Daz Studio 4.0 (first release) there was a clear separation between how content was delivered to the library depending upon whether it was Poser Runtime assets or Daz Studio Content.
Install Manager as well as manual methods, we could still just install everything to one main path. But since the locations of assets for Poser and Daz Studio differ so much - and I have an enormous collection of Poser Runtime assets which is still growing as much now as it was then, I find it incredibly beneficial to divide all of my Poser format products into their own categories of Runtime structure:
Environments - Holds not 'only' environments, but everything associated with them, like structures, furnishings and furniture, plants, rocks, etc.,
We could further divide that between genre - or even use "Sci-Fi", for example, as a category instead of "Environments" and put everything from Sci-Fi environments and vehicles to Sci-Fi weapons and props into this Runtime Structure - whatever system works best. The main point being to be able to find specific things when the list of what we have grows for years and years.
The Daz Studio format is a bit different and, for me, is a Lot easier to just install everything into the same (I use default) library, and let DIM (Daz Install Manager) help us to sift through our purchased products.
Of course, we could simply install Everything to the same library, since we can use DIM to help us find anything we own - which is nice too - so it really depends on how we like to work.
I have a separate Poser Runtime for "Renderosity", which holds all of the Poser content I buy from them - making it really easy to locate my coflek-gnorg stuff, for example.
Quite a lot of my Predatron content is now considered "Legacy", as it came out before Iray and uses the Poser Runtime structure. So I have a single runtime structure called "Predatron", where I can find all of his monsters, droids, animals, and people - which is Super handy for me.
Dragons that are in Poser format all go to my "Dragons" runtime structure, making them very easy to work with. This may seem tedious, but once we start getting addons for everything that might have names and library locations that are not very obvious, having the runtime structures condensed to specific types of things makes all of the installed content a lot easy for me to find - which means that I'll actually use it a lot more often - because I can go right to it - even if the product name escapes me at the moment.
Now, once I'm in Daz Studio, I can make any structure I what for my Content pane - organizing things just how I like it - so things that I use a lot and want quick access to (basically anything I spend time on making it the way I like it to be) I save as a Scene Subset (not Scene) which only stores the data necessary to load what I've created - leaving the original "Installed To" data untouched, so my saved Scene Subset is a tiny file, even if it loading something huge.
I do this after I convert Poser format assets to Daz Studio and Iray. I could save the whole thing if I wanted to, but that dramatically increases the size of the library on the machine side of things, so I prefer to only save my optimized data.
An example of this:
Let's say that Daz 3D's Millennium Dragonling 2 is going to be a star in the production I'm working on.
That figure is still in the older Poser format, with an option to also install the DS supplement. I load the Millennium Dragonling 2 directly from the Poser runtime "Dragons" and apply any of the presets from that library that I want for my young dragon.
After I'm all done loading everything I need for this dragon from the Poser runtime, I convert the material to Iray shaders and tweak them to my liking, add any of my own custom dials that I demonstrate in my Dynamic Character Animation course, and then save this wonderful, Iray-optimized little dragon as a Scene Subset called "Imlofryrax" in my "Animals > Dragons > Dartanbeck" location of My Daz 3D Library.
Now when I load that subset into any scene, I get everything I've saved in the subset - but the file that launches doesn't have to hold the actual heavy asset data, only the paths from which to load it - so it's a nice small file. Hmmm... I hope that makes sense.