Daz Characters max for a scene with subdivision

coffeeaddicted

Well-Known Member
Apr 13, 2021
1,841
1,508
So, i have an older computer now.
It does have an AMD Ryzen 5 3600, a RTX3600 with 12GB, Ram with 32GB.
DAZ(4.23.0.1) runs fine but the newer version made it more laggy in my opinion.

Now, i wanted to render a scene in a clothing store.

I removed most of this things from the scene so that i only have walls and some crap where the cashier is.
Then i used a 3point lightning system.
3 characters.
Sydney 8 HD (sub 1,4) and two male genesis 8 (none HD) that have sub 2.

Every time DAZ doesn't render. It seems that i only can render two characters at the same time.
But i know i rendered before this DAZ version with 3 characters.
I lowered the sub division from Sydney to 1,2 but that made a real difference.

So what sub should i use or should zero the HD of Sydney? She stands a little father away. So not much details are seen in that scene.

What do you do if you have a similar PC like mine to render 3 characters at the same time?
 

Midzay

Member
Game Developer
Oct 20, 2021
215
625
Is it just that scene that's the problem?
How much RAM and how much video memory is used? Are the rendering settings still on the GPU? Did you update the video card driver?
 

Turning Tricks

Rendering Fantasies
Game Developer
Apr 9, 2022
1,444
2,729
SubD really should only effect how long a render takes, not the amount of VRAM needed. It sounds like you are maxing your VRAM out and don't have CPU fallback enabled. Your log file should list an out of memory error if the render shut down because of that. Or you can just run task manager and look at your GPU performance tab to see how much VRAM is being used.

With 12GB, you could easily run out in a full scene with 3 Gen characters and the environment. Try hiding the environment and rendering again to see if it works. That shop asset you linked has 55 - 4K textures being used. That's a lot of overhead. You might want to try the scene optimizer script to reduce those textures.

Worst case, you have to do the render in stages. Like Background separate from the characters, then add them afterwards. I had to do that a LOT when I was using an old 1050 Ti card with 4GB.
 

anne O'nymous

I'm not grumpy, I'm just coded that way.
Modder
Donor
Respected User
Jun 10, 2017
11,237
16,948
DAZ(4.23.0.1) runs fine but the newer version made it more laggy in my opinion.
Yeah, it have ten time more problems with the memory usage than before.


I lowered the sub division from Sydney to 1,2 but that made a real difference.
Here too Daz Studio always had issues, partly due to its really bad management of the memory.

You need to understand that for each level of subdivision you multiply the number of polygons by four. Therefore, with Genesis 8, that have 17,000 polygons, three levels of sub divisions make you pass over the million polygons. And this is just for the figure itself, but there's also the clothes and the hair. What is doubled since you've two characters in the scene, and of course should also be counted what you kept of the room.

So, of course, it give something smoother, but it also easily saturate the memory, as well as the CPU/GPU.


So what sub should i use or should zero the HD of Sydney?
2 when the character is in the foreground and the focus of the scene, 1 when the character is at mid distance or not the focus of the scene, 0 when it's far. 3 is to reserve for close-up, and I mean real close-up.
When there's many characters, render the scene by cluster that you'll put together with Photoshop/Gimp/whatever. It cause issues with the shadows, but generally it's faster than trying to render the scene in one go.
 
  • Yay, update!
Reactions: coffeeaddicted

coffeeaddicted

Well-Known Member
Apr 13, 2021
1,841
1,508
Yeah, it have ten time more problems with the memory usage than before.




Here too Daz Studio always had issues, partly due to its really bad management of the memory.

You need to understand that for each level of subdivision you multiply the number of polygons by four. Therefore, with Genesis 8, that have 17,000 polygons, three levels of sub divisions make you pass over the million polygons. And this is just for the figure itself, but there's also the clothes and the hair. What is doubled since you've two characters in the scene, and of course should also be counted what you kept of the room.

So, of course, it give something smoother, but it also easily saturate the memory, as well as the CPU/GPU.




2 when the character is in the foreground and the focus of the scene, 1 when the character is at mid distance or not the focus of the scene, 0 when it's far. 3 is to reserve for close-up, and I mean real close-up.
When there's many characters, render the scene by cluster that you'll put together with Photoshop/Gimp/whatever. It cause issues with the shadows, but generally it's faster than trying to render the scene in one go.
Yes, this is the problem.
DAZ is a mess. But perhaps they work with NVidia to sell more GPU's. WHo knows.

In any case, i went with the original intended subdivisions which is 1/4.
Probably overkill. So i went for 1/3. Still overkill.
I will try 1/2, since its not a close up. Though i like to see the wrinkles. Other than that, no purpose for a $100 Dollar figure.

I kind of want to avoid to do the cluster. But in the end, if you want to add some NPC's, this may be the only way.
Thanks, Anne. Always a pleasure to read you.

p.s. i forgot to mention, that it still happens that after some time, DAZ decides to crash with an error. I don't care about the error but just the fact, that DAZ is doing some stuff with memory and crashes upon the memory is already funny. I am sure there more people that have stories like that.
I am not sure which version i had before but i think it was more smooth, no crashes or if, rarely.
So i am not sure how this was released and the worst part is, you have to take it since you can't select the version when you install DAZ.
Unless there is a way to not have to download it before installing. I did try to overwrite it with an older version but that caused more problems. I am sure if forgot to delete some newer version libraries.
 
Last edited: