- Jan 20, 2022
- 439
- 1,431
Like I said, I don't know anything about Daz3d.I can’t even imagine how this is possible. I recently watched a training video about Daz, there was a Warhammer style battle. There were 3 times more people in this scene than in the book club. Everything opened normally without significant delays, while the author of the video had 1x3090 and Ocean had 2x3090. I think this is Ocean's problem with the PC, maybe the SSD started to die.
As far as I know, in 3D rendering, it's not the number of objects that matters, but how detailed the texture is used.
Explanations from seniors and Ocean Dev Log.
Sometime ago it was explained why the A6000 was needed, I honestly can't find it at the moment.
SG's workstation, so from memory, is a threadripper 3970x, a 3090, a 4090 and 128 gb of ram.
WIAB's pc was a ryzen 9 3700x with the A6000 and the 3090 which was SG's (it used to be a 2080).
I don't know DAZ but...
Scene load time is an issue, Ocean talked about it in the latest Dev Log.
But what Ocean mostly complains about is VRAM constraints, which is a hardware constraint mostly rather than a DAZ limitation. The more stuff you have in a scene (model complexity, number of models, number of lights etc.) the more VRAM you need to be able to load it in DAZ. It just fails to load if it runs out of VRAM.
That's why he talks about getting A6000 cards, more VRAM. The problem is A6000s render a lot slower than 4090s etc. Which is why no other AVN dev I know of are using A6000 cards, they're using 4090s etc. because they render faster.
When people talk about Ocean doing better optimisation, what they mean is reducing the complexity of the scenes so they're easier to load & render faster. But that requires compromises, reduce the complexity of environments, reduce the number of characters, use background chars instead of full models etc.
Ocean isn't a fan of making those sort of compromises. That's why he's reworking scenes he felt were too empty originally for example. And spending a bomb on A6000 cards for the VRAM despite them rendering slower.
Not at all, we're gentlemen after all. Scouts Honour!
DAZ is one of the most poorly optimized software ever.
When DAZ makes an image what it does is basically rendering the same image over and over again, it then combines them to make the final picture. Every single render is called iteration. You can notice right away if the final picture was done with a low iteration count because it has a distinct sandy feel.
When you're rendering with multiple GPUs DAZ make every GPU render a different iteration. That means that each GPU must be able to load that picture on its own. So if a render requires 17GB to load, both GPUs need to have that amount.
Last edited: