Daz Multiple DAZ studio CMS.

[caLTD]

Hello,

For test purposes, I want to use seperate daz installation. Seperate every thing.
Is there any work around for this ?

 

[osanaiko]

You can install and run the Daz Beta in parallel with standard Daz. It can potentially use a separate content DB if you configure it to use different folders.

If you can get your hands on an older beta installer package, you could even have the "same" version as your primary install.

 

[caLTD]

You can install and run the Daz Beta in parallel with standard Daz. It can potentially use a separate content DB if you configure it to use different folders.

If you can get your hands on an older beta installer package, you could even have the "same" version as your primary install.

Thanks I have those. I need second daz setup with own content.

It's like a daz installation that only contains assets for the project I'm currently working on.

 

[simarimas]

I just installed a newer and older version of DAZ. if you rename the original installed folder, by just adding the version number (DAZStudio4 and make it DAZStudio4.23) Then when you install another Daz Studio, it should create a new folder named DAZStudio4. Then make a short cut for each application. At that point, you should be able to create new paths for assets, etc.

 

[osanaiko]

If you want to make a separate set of content but with the same daz installation, the way to do that is to use the "Content Directory Manager" add and remove separated content folders.

Then you can switch between them as needed by reversing the config.

I've got several, which I enable/disable to speed up figure and scene loading when working on project content, vs browsing the whole collection.

 

[caLTD]

If you want to make a separate set of content but with the same daz installation, the way to do that is to use the "Content Directory Manager" add and remove separated content folders.

Then you can switch between them as needed by reversing the config.

I've got several, which I enable/disable to speed up figure and scene loading when working on project content, vs browsing the whole collection.

View attachment 5312328

Thank you.
I've messed with these settings before and didn't understand a thing.

Now it's settled in my mind; I'll have to reinstall Daz.

Thanks again, I appreciate it.

 

[Turning Tricks]

I've been slowly moving the thousands of assets I have, over onto a RAID setup I made. When I build a new render box in a few months, I'll be wiping DAZ completely and then reinstalling with properly mapped out directory structure.

I've been battling meta-data issues for months now, due to some wonkiness in my install and changed drives.

 

[caLTD]

I've been slowly moving the thousands of assets I have, over onto a RAID setup I made. When I build a new render box in a few months, I'll be wiping DAZ completely and then reinstalling with properly mapped out directory structure.

I've been battling meta-data issues for months now, due to some wonkiness in my install and changed drives.

I had one dedicated Gen4 M2. It can handle 4000 of assets without major problems. However Gen 9 assets are problematic.
They are slow to load, when I use them daz very slow to close and worst of them I had jitters in view port.

When I try pose a G9 character view port (flament mode) has FPS problems, it became too slow, so I cannot alter pose with mouse it jitters.

And I'm not sure it was because of large amount of G9 assets (because When I make clean g9 setup with few G9 charaters there is no problem) or because of the one of G9 asset with bad quality.

 

[Turning Tricks]

I had one dedicated Gen4 M2. It can handle 4000 of assets without major problems. However Gen 9 assets are problematic.
They are slow to load, when I use them daz very slow to close and worst of them I had jitters in view port.

When I try pose a G9 character view port (flament mode) has FPS problems, it became too slow, so I cannot alter pose with mouse it jitters.

And I'm not sure it was because of large amount of G9 assets (because When I make clean g9 setup with few G9 charaters there is no problem) or because of the one of G9 asset with bad quality.

That's odd, because I find most of my scenes with G9's are quicker loading than my older scenes with a mix of G8 and G8.1. In fact, in the last series of renders I recently did, my DUF files were only 4-5MB each, while some of my older G8 scenes are like 40MB and up (but TBH, a lot of those have some morphs I could have trimmed)

 

[caLTD]

That's odd, because I find most of my scenes with G9's are quicker loading than my older scenes with a mix of G8 and G8.1. In fact, in the last series of renders I recently did, my DUF files were only 4-5MB each, while some of my older G8 scenes are like 40MB and up (but TBH, a lot of those have some morphs I could have trimmed)

Interesting, perhaps I had a rogue assets which create problems.

 

[Turning Tricks]

Fit Control is one clothing morph that can quickly bloat a scene extremely large. Something like 30-40MB more when you apply it. I had that a lot until another dev pointed out to me that I can remove any unused parts of Fit Control with one of the scripts it comes with. That shaves the DUF sizes down quite a bit.

 

[caLTD]

Fit Control is one clothing morph that can quickly bloat a scene extremely large. Something like 30-40MB more when you apply it. I had that a lot until another dev pointed out to me that I can remove any unused parts of Fit Control with one of the scripts it comes with. That shaves the DUF sizes down quite a bit.

This week, I had one of those costly experiences.
While playing with daz for the secondary asset directory I planned to use for G9, I messed up the existing asset system.

About a month and a half of my work was wasted; perhaps I could have fixed it if I'd tried. However, instead of tackling it one by one, I chose to start over.

This time, however, I made my first attempt with only G9 assets. My first short game was made entirely with G9 assets, and for some reason, it was causing problems in the viewport. So, I slowly tested the existing G9s while loading them.

My conclusion was that G9 assets with problematic morphs cause jitter in the viewport. I tracked the logs and deleted the problematic ones completely. Now, my G9 characters are as flexible as G8.1, and their skin details are much more realistic.

I'll be re-doing everything I've done so far (about 300 shots).

Loading G9s still takes longer (perhaps due to 4k, 8k skin textures), and some tasks run slower on G9s. Unfortunately, the current daz3d studio can't utilize multiple cores, so it's very slow even for very small tasks.

Rendering times are similar, and I didn't notice any noticeable difference.

 

[osanaiko]

My conclusion was that G9 assets with problematic morphs cause jitter in the viewport. I tracked the logs and deleted the problematic ones completely.

This is very interesting. Can you please share which morphs caused the problems?

 

[caLTD]

This is very interesting. Can you please share which morphs caused the problems?

Too many.

install baretail for windows locate daz log. open daz create new g9 character.

Even this scenario possible.

A cloth has some common body fitment as morph slider and you do not have that particular body morph. When you try to create pose in view port with using mouse, tons of error thrown in log. If those errors starting pile up. Viewport fps affected.

 

[caLTD]

2025-10-20 13:04:36.718 [INFO] :: Preparing modifiers...
2025-10-20 13:04:36.754 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(6788): Parent for modifier not found: Jamal_body_cbs_BodyZ55L. (parent: )
2025-10-20 13:04:36.755 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(2389): Modifier not prepared: Jamal_body_cbs_BodyZ55L!
2025-10-20 13:04:36.781 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(6731): Modifier definition not found.
2025-10-20 13:04:36.781 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(2389): Modifier not prepared: Poisition-0xa4fb47a!
2025-10-20 13:04:36.781 [INFO] :: Creating modifiers...
2025-10-20 13:04:37.030 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(2406): Modifier not created: Jamal_body_cbs_BodyZ55L!
2025-10-20 13:04:37.763 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(2406): Modifier not created: Poisition-0xa4fb47a!
2025-10-20 13:04:37.779 [INFO] :: Creating property aliases...
2025-10-20 13:04:37.806 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(10184): Alias property reference not found: Genesis9:/data/DAZ%203D/Genesis%209/Base/Morphs/P3Design/P3D%20Natural%20Expressions%202/P3D100NE2_facs_bs_FunnyDiscomfort_UpperFace_UpperFace.dsf#P3D100NE2_facs_bs_FunnyDiscomfort_UpperFace_UpperFace-0xa75006b?value
2025-10-20 13:04:37.806 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(2421): Property alias not created!
2025-10-20 13:04:37.835 [INFO] :: Resolving 440098 formulas...
2025-10-20 13:04:37.835 [INFO] :: Finding formula properties...
2025-10-20 13:04:37.842 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(646): Formula target property not found:
    File: /data/Daz 3D/Genesis 9/Base/Morphs/Daz 3D/Pixie 9/Pixie9_facs_cbs_EyeBlinkR.dsf
    URI: head:/data/Daz%203D/Genesis%209/Base/Morphs/Daz%203D/FACS/alias_head_facs_bs_EyeBlinkRight.dsf#facs_bs_EyeBlinkRight?value
2025-10-20 13:04:37.843 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(646): Formula target property not found:
    File: /data/Daz 3D/Genesis 9/Base/Morphs/Daz 3D/Pixie 9/Pixie9_facs_cbs_EyeBlinkL.dsf
    URI: head:/data/Daz%203D/Genesis%209/Base/Morphs/Daz%203D/FACS/alias_head_facs_bs_EyeBlinkLeft.dsf#facs_bs_EyeBlinkLeft?value
2025-10-20 13:04:37.898 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(595): Formula output property not found:
    File: /data/DAZ 3D/Genesis 9/Base/Morphs/Zev0/Shape Shift/SS_body_bs_Thigh Length.dsf
    URI: Genesis9:/data/DAZ%203D/Genesis%209/Base/Morphs/Zev0/Bend%20Control/RCompress%20Inner.dsf#RCompress%20Inner?value
2025-10-20 13:04:37.972 [WARNING] :: \src\sdksource\fileinput\dzassetdaz.cpp(595): Formula output property not found:
    File: /data/Daz 3D/Genesis 9/Base/Morphs/Censored/Subtle Expressions Olympia 9 Edition/facs_ctrl_SEOE Awkward.dsf
    URI: Genesis9:/data/Daz%203D/Genesis%209/Base/Morphs/Censored/Subtle%20Expression%20Olympia%209%20Edition/facs_ctrl_SEOE%20Amused.dsf#facs_ctrl_SEOE%20Amused-0xa0b8d3f?value

 

[Turning Tricks]

This week, I had one of those costly experiences.
While playing with daz for the secondary asset directory I planned to use for G9, I messed up the existing asset system.

About a month and a half of my work was wasted; perhaps I could have fixed it if I'd tried. However, instead of tackling it one by one, I chose to start over.

This time, however, I made my first attempt with only G9 assets. My first short game was made entirely with G9 assets, and for some reason, it was causing problems in the viewport. So, I slowly tested the existing G9s while loading them.

My conclusion was that G9 assets with problematic morphs cause jitter in the viewport. I tracked the logs and deleted the problematic ones completely. Now, my G9 characters are as flexible as G8.1, and their skin details are much more realistic.

I'll be re-doing everything I've done so far (about 300 shots).

Loading G9s still takes longer (perhaps due to 4k, 8k skin textures), and some tasks run slower on G9s. Unfortunately, the current daz3d studio can't utilize multiple cores, so it's very slow even for very small tasks.

Rendering times are similar, and I didn't notice any noticeable difference.

Ya, that single core restriction is interesting, because my DAZ runs pretty decent, even with my old low-level 10th gen i3. But it has decent single core speed, while people with later generations of CPU, with 8 or 10+ cores, get the same or even worse viewport performance, because they have lower single core speeds. When I build my new render box later this year, I think I will be choosing a CPU I can (1) afford and (2) has better single core speeds in it's price-point and not put as much emphasis on multiple cores. The other general guideline DAZ developers use is having system RAM = 2X the VRAM of your GPU. That's what I have now (16GB GPU and 32GB system RAM) I'll be upgrading that to a newer MB with DDR5 memory and getting 4X the RAM (probably still be using a 16GB 5060 Ti but with 64GB of RAM).

I fixed a lot of my meta-data issues currently, but I still have this problem where if I install an asset with DIM, DAZ seems to have problems with the meta-data. So I just get placeholder icons when looking for it. I'm sure it's something to do with my directories being messed up somehow, but I honestly don't have time to deep-dive it right now. I'll wait until I build my new PC and then wipe and reinstall DAZ on both machines properly. For right now, what I do is take the DAZ IM files and and just manually extract them directly into my content directory and they show up fine in both SMART view and the Content Tab.

 

[caLTD]

Ya, that single core restriction is interesting, because my DAZ runs pretty decent, even with my old low-level 10th gen i3. But it has decent single core speed, while people with later generations of CPU, with 8 or 10+ cores, get the same or even worse viewport performance, because they have lower single core speeds. When I build my new render box later this year, I think I will be choosing a CPU I can (1) afford and (2) has better single core speeds in it's price-point and not put as much emphasis on multiple cores. The other general guideline DAZ developers use is having system RAM = 2X the VRAM of your GPU. That's what I have now (16GB GPU and 32GB system RAM) I'll be upgrading that to a newer MB with DDR5 memory and getting 4X the RAM (probably still be using a 16GB 5060 Ti but with 64GB of RAM).

I fixed a lot of my meta-data issues currently, but I still have this problem where if I install an asset with DIM, DAZ seems to have problems with the meta-data. So I just get placeholder icons when looking for it. I'm sure it's something to do with my directories being messed up somehow, but I honestly don't have time to deep-dive it right now. I'll wait until I build my new PC and then wipe and reinstall DAZ on both machines properly. For right now, what I do is take the DAZ IM files and and just manually extract them directly into my content directory and they show up fine in both SMART view and the Content Tab.

Yes, daz3d is very old and very affected with single core performance.

From my one-year experience with DAZ, I understand that for every update to the viewport, DAZ checks all the morphs valid for that Genesis version one by one. If there's an error, it has a very high CPU cost, and after a certain point, it affects viewport performance. Because, I believe, everything other than VRAY is rendered by the CPU.

However, this week I encountered a very silly situation. I use a recursive node to create keys in animations. After moving to G9 characters can require a wait of minutes. So I created a script.

The same process takes seconds with a script. I believe there was also problem with DAZ UI to Daz Backend.

And about new render pc.



This scene was rendered by RTX 3090 ( I buy second hand) with Ryzen 7900 (12 core) and 64 gb ram. All characters are G8.1 and I try to find good skins. After some time I will recreate same scene with G9 Characters I wonder will it fit.

So, when you buy a new rig, try with bigger vram.