- Jul 26, 2023
- 1,373
- 2,256
- Nov 11, 2017
- 645
- 1,815
is that like standard DAZ rendering? that seems way too slow on progress and heavy on a PC
- Apr 28, 2023
- 41
- 141
While I'm not an expert, I have a pretty good understanding of how DAZ works now after doing it for almost two years, but someone with more experience/knowledge might correct me on what I'm about to say.
For Chapter 2 I would say that the average time has been closer to 40 minutes. But obviously render times vary considerably based on what is being rendered and how many iterations are required to produce the final image. The current scene I'm working on is indoors, at night, mostly focused on character faces and has glass windows in the background. In my experience, the glass requires more iterations to render to completion, a closer shot of a character's face typically renders slower than a further out shot (not sure exactly why on this bit), and the environment (light settings and actual building prop) can also impact render times, to varying degrees. But for me and my setup, 90 minutes for a scene like this seems pretty normal.
As an example of this scene I'm working on, I'm attaching three images. I've not done any post work or anything to them, they're just the raw renders, all from the same part of the scene, the same conversation. One renders in 40-50, one in 1 hour 20 and one in exactly 2 hours. The lighting and camera angles are pretty much the same, I'm hiding unnecessary assets to save memory etc. but the renders time still vary, presumably because of the hair and makeup on certain character iterating slower.
You don't have permission to view the spoiler content.
Log in or register now.
You don't have permission to view the spoiler content.
Log in or register now.
You don't have permission to view the spoiler content.
Log in or register now.
An bright, sunny outdoor scene, for instance, I can render in 10 minutes (assuming it's just 1 or 2 characters with little to no extra lighting). But I've found that a lot of indoor scenes can really run up the render times. The longest I've had for this chapter was just over 4 and a half hours, if memory serves. That's because of a very specific asset for a character that, for whatever reason, means that the render iterates very slowly.
I don't know if this is normal. As far as I can tell, I render using pretty standard settings, but if someone can point out something I've been doing something wrong this whole time then I'd take any advice.
For what it's worth my PC has been completely fine the whole 2 years I've had it. Nothing's ever broken or needed replacing, and it runs as well as it ever has. GPU temps all normal etc., too. So I don't think the excessive render times have been negatively impacting it.
- Nov 11, 2017
- 645
- 1,815
thanks for the insight with what takes longer to render. but even 40 minutes for one image is insane to me
- that sounds so inefficient for one image when the intention is to create scenes which i'm sure DAZ programmers had in mind. idk if it's a bottleneck issue with one of your drivers but it's not an overworked component as you pointed out for what it's worth the renders are crisp and high res. however, i hate to break it to u but there's a community of us who just ask for compressions of the VN so we dont even necessarily require such high resolution. but that's up to u and if u want to further investigate other developers' process
- Apr 28, 2023
- 41
- 141
I'm not sure what the original intention of DAZ was, but I'd be surprised if they thought people would be trying to make 1000s of renders a year on it. My assumption was always that it was a 3D art software for one-off images, so it's not especially optimized for quick renders. Not sure on that, though.thanks for the insight with what takes longer to render. but even 40 minutes for one image is insane to me
for what it's worth the renders are crisp and high res. however, i hate to break it to u but there's a community of us who just ask for compressions of the VN so we dont even necessarily require such high resolution. but that's up to u and if u want to further investigate other developers' process
And to be fair, as I say sometimes scenes can take 5-10 minutes if they're really basic. But once you start adding in details and environments, it just adds to the information that needs to be processed and calculated.
As for render quality, I'm pretty much already working at the minimum. I only render at 1920x1080. Many other devs, as far as I can tell, render at larger sizes (4K or 1440) and then downscale to 1080. This does result in better image quality, but like you say not everyone cares for that, and people often play compressed versions anyway. My issue with that is that while 4K images look a lot better, they literally take 4x the amount of time to render. That's a sacrifice devs with multiple rendering machines with very high-end cards can afford, but for me and I assume a lot of other devs with only one computer it's not worth the time. But it's good to know that native 1080 renders are still a good enough quality.
- May 1, 2017
- 343
- 192
- Apr 28, 2023
- 41
- 141
Back in May I thought I could have it out by the end of June. That's still a possibility, but unlikely at this point. I've still got what I'd guess to be a couple weeks of rendering to do still. I don't want to keep guessing a date and pushing it back, but atm I'd say early-to-mid-July. Hopefully I won't push that back too.
- Jul 26, 2023
- 1,373
- 2,256
Keep at it mate. No pressure. At least you're keeping us in the loop about where things stand. I appreciate it muchly. And very much looking forward to chapter 2.