Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
And is it still in your Product Library on the site here? Have you tried checking Show Hidden in Install Manager?
In the past, just using the transfer assistant the Mac OS supplies, I've been able to copy over the DAZ Studio Content libraries (with data, Materials, People, Props, etc., and even the DAZ3D folder with the InstallManager/Downloads/Filters/ManifestFiles. I've never noticed any problems. Of course, the application itself, DAZ Studio, I would again download. [Some of the other apps worked fine; some had to be re-downloaded as well.]
Now, and I'm not at all a computer savy person, so I'm asking for guidance, not trying to argue, but now I seem to be reading that this shold not be done.
Yet, above, from Doctor Jellybean, I'm also reading: "Yes, the Content folder is the folder containing the downloaded files. You can copy over the Library, which contains the installed content. However, the application and plugins should be installed from scratch. You will need to install PostgreSQL, but don't copy the actual database over." And:
"Well, if you copy over the Library as well, and mapped the paths in DAZ Studio, then you can re-import the metadata in DAZ Studio by clicking on the menu icon (top right) of the Content Library pane, select Content DB Maintenance and select Re-Import Metadata."
So, will this not work? I do have my own content mingled in, such as Scene Subsets, Poses, etc. I'm not lazy, so I've been making duplicates of all of these things. Then, if I have to just copy over the InstallManager/Downloads files, I could then install my own files where I want them.
But I'm hoping the simplier approach will work: That is: copy over the Content folder, too, download the applicaiton, the plugins, PostgreSQL, but not the cms database, and re-import the metadata. The database, I'm guessing, will be reformed as DAZ Studio runs.
Anyway, Please: more guidance.
Good news! The updated Daz Studio build (4.15.0.30) has been promoted to the general release. So now you can install it from DazCentral or from DIM without having to do any work to get a beta going on your system.
Found that if I manually download the Holt 8 file, I could put it into the DM download area and it would show up as "Ready to Install".
So, how does one recover from being in a Beta mode to using the general release?
I've seen reports from other users on this thread about auto-mounted drives in /volumes not being accessible. You can create a new CMS anywhere; just F2 in DAZ Studio, go to the "CMS Settings" tab and change the "Cluster Directory"; make a new directory and select that. This gives you a clean CMS. DIM should automatically pick up the new CMS (there is just one configuration file; it's cms/cmscfg.json in your DAZ .config directory) but check that it has after making the change in DAZ Studio.
You shouldn't need to download the package Zip files; just share them from the Mac Pro (while not running DIM on the Mac Pro) or copy them. They have a checksum that DIM validates against your product library.
Okay :-)
............
And with the 1st test render it did not crash :-)
{and yes folks, one can manually download/install it too}
Great news! Will this version fix the opacity/atmospheric issue, or is it fixed in DS 5?
As far as I am aware that is an Iray issue, rather than Daz Studio-specific, but if you check the chnage log or the highlights threads you can see if a given issue has been addressed.
Just install, and note that the General release doesn't use the same directory settings as the beta so if you customised your paths you will need to do the same in the general release.
The DAZ Productions help page basically says that, but what you have done is going to work just fine so long as you copy the content and the "config" files to the same places on the new system. In fact not all the config files need copyiing - it's the DIM config, the CMS DB and config and at least "Studio4/ContentDirectoryManager.dsx", but it's safe to copy the whole config directory then install DAZ Studio on top of it. The CMS database may be architecture (endianness) dependent; it may not be possible to copy from Windows to MacOS or vice versa.
The help page seems concerned that users not move the content around. In some sense copying everything to the same path on a new machine doesn't move anything, but it is necessary to preserve the CMS database (which, on Windows, defaults to %AppData%/DAZ 3D/cms and I suspect is in a .config directory in the user $HOME on the Mac).
This will lose the metadata; the CMS database will be empty. Doing "Reimport Metadata..." will restore all the DAZ metadata (I just tested that) but not quite all the user-generated data (see below).
My understanding from what Richard said is that this only works if you have previously done "Content Library/Content DB Maintenance.../Export User Data" on the original machine to get any data you added out of the CMS on that machine; so you have to do this before you copy your library over.
You have to do your library yourself. If you do Export User Data... then the file goes into that library, so copying just that directory tree, re-installing all the DAZ products, then doing "Re-Import Metadata" should (also) restore the system state; you can just choose to import the exported user data and products individually.
The "Re-Import Metadata" step rebuilds the CMS. It says what it is going to do:
So it has found all the products (somehow) and has my previously saved metadata (apparently), as well as something I didn't know I had (I don't have the faintest idea where the AncientMineShaft stuff comes from!) Before trying it in anger I suggest checking out what happens; it seems to fail to preserve the contents of SmartContent/Saved Files, replacing it with stuff corresponding to DAZ3D packages. It's easy to test:
At this point "Smart Content" is empty. Now do "Re-Import Metadata" and see if the results are ok. Since you now have two completely separate CMS databases you can just flip between the two using the F2/CMS Settings/Cluster Directory setting. When finished swap back to your original Cluster Directory setting.
All three of the ways suggested seem to work:
It is also, in truth, easy to move the CMS directories around; just edit the path in "Content Directory Manager". This does have the problem that the old path is still in the Manifest Files DIM writes, but the symbolic link trick I described works round that (I tried it) as, I'm pretty sure, does bulk-editting all the manifests.
@dawnblade - Just DLed 4.15.0.30 and, unfortunately, the bug is still there:
In this image, the smoke for the candle was created with planes that use cutout opacity maps. You can see how the volumetrics are not present in the areas where the maps are black.
- Greg
whats in the new update ? I don;t see anything around the site explaining why I need to download and install it
Big Sur (and, I assume, Monterey) support; it's absolutely essential if you want to upgrade from Catalina. Other than that there are a small number of bug fixes and minor UI changes since 4.15.0.2 some of which may interest you; I'd always have Daz crash when I accidentally used the "Universal" tool instead of Anibones (or whatever it is called) with the pose tree locked, it looks like there is a fix in there for the crash. Look at the "highlights" thread from 4.15.0.9, or the changelog for the beta.
Thank you @algovincian for testing it. Hopefully it will get fixed soon. It could be that Nvidia hasn't done their part yet.
Thanks. I'm on PC and it crashes often. Probably worth the install to see if it improves.
Always remember to stash the original zip archives of the product (12000 or 13176) before downloading a new version; then you can go backwards.
I see two most possible reasons for this.
(1) Z-Brush is M1 native and the dylib is x86_64, libloading will most probably fail
(2) Z-Brush is not built allowing linkage to 3rd party libraries not signed by themselves or Apple, but someone else.
But just my best guesses.
Possibly. But I think this is not a Zbrush issue. This was the plugin from Daz which is simply being called by Zbrush. Same dylib reference issue we had with Daz Studio itself before it was updated.
Have you checked that the plugin has not been updated?
Hey DAZ, maybe someone can pass this on to higher up: It's nice that you're celebrating the new release with some generous coupons, but would be even nicer still if Europeans and other people in different time zones could participate, too! A person needs to sleep some time, you know ...
Yeah... We are 6 to 10 hours ahead of DAZland here.
I full agree to that. I miss many sales in Europe (Germany).
It was a remarkably short celebration - Blink and you miss it.
@jbowler: Thank you very much for taking the time to respond to all of my aprehensions (questions). I actually don't understand some small parts of all of that, but I think I do get most of it. It does relieve me of my worst fears. It certainly took some time for you to write all of that, and I am grateful.
Well, it still contains some glitches, but no reason to stop the celebration THAT fast...
Anything I need to know about this latest 4.15 version, as a PC user? GenX still working, I assume?
I would have preferred the beta version. Can be installed next to other versions ....
PC version is crashing a lot, at least for me. Mac version seems to be slightly more stable. All noticeable bugs (e.g. opacity on atmospehric lighting, transmapped hair, anything with an opacity map) are still there.