3D-Daz Daz3d Art - Show Us Your DazSkill

5.00 star(s) 13 Votes

Willibrordus

Well-Known Member
Feb 17, 2020
1,117
6,513
Then I'd need to try that denoiser. I wish I could do renders like that. Also, I'd suggest you dabble in product rendering. This setup and the quality would bring you lots of income I think. Long as you keep posting those beautiful images here.
Denoiser will not do your renders any justice I think. Denoiser kills texture and detail. You're better off using a denoiser afterwards on the finished render but only if you really have to. I rarely have to use denoiser. I light my scene a bit brighter than I have to in order to get all the detail I want and then darken it in photoshop to get the desired look.

You can also oversample and then reduce size to counter noise.

This is my latest render, no noise from the render itself, I only needed to adjust some levels and retouch a few artefacts. Villa Toscana Sara closeup M_02.JPG
 
  • Like
Reactions: Leeduva

atheran

Member
Feb 3, 2020
355
2,759
Denoiser will not do your renders any justice I think. Denoiser kills texture and detail. You're better off using a denoiser afterwards on the finished render but only if you really have to. I rarely have to use denoiser. I light my scene a bit brighter than I have to in order to get all the detail I want and then darken it in photoshop to get the desired look.

You can also oversample and then reduce size to counter noise.
Of course at the finished render. Isn't that how nvidia denoiser works? I wouldn't touch the DAZ one, that's for sure. I did that mistake once. As for oversampling..I'm a proud member of the #potatosquad with a laptop carrying a 6700HQ and a 970m. Oversampling kills the render times for me. If I render an image at FHD in 4h, at 4k it takes about 3h to start returning percentages to me. Even if I left it to 50% and then stopped the render to reduce the size, it'd still take about 6-7h.

EDIT: Because I forgot the part of the comment about lighting it brighter than needed. That might reduce render times, and it's a good idea for the normal renders. But since I started using volumetric lighting, if I make the lights brighter, the whole image is blown out. I haven't found a way yet to get rim lighting working without making the render look like it's placed in a heavy snowstorm or the middle of a thick fog.
 

Willibrordus

Well-Known Member
Feb 17, 2020
1,117
6,513
Of course at the finished render. Isn't that how nvidia denoiser works? I wouldn't touch the DAZ one, that's for sure. I did that mistake once. As for oversampling..I'm a proud member of the #potatosquad with a laptop carrying a 6700HQ and a 970m. Oversampling kills the render times for me. If I render an image at FHD in 4h, at 4k it takes about 3h to start returning percentages to me. Even if I left it to 50% and then stopped the render to reduce the size, it'd still take about 6-7h.

EDIT: Because I forgot the part of the comment about lighting it brighter than needed. That might reduce render times, and it's a good idea for the normal renders. But since I started using volumetric lighting, if I make the lights brighter, the whole image is blown out. I haven't found a way yet to get rim lighting working without making the render look like it's placed in a heavy snowstorm or the middle of a thick fog.
Hey, I'm the guy who started the #Potatosquad hastag here several months back. I know a thing or two about long rendertimes. on my old pc I had average rendertimes between 14 and 18hrs.
I have one supersize picture I had render for 127hrs in 20hr sessions with some cooldown in sleepmode in between it made my PC unusable for a whole week.
Even my screensaver (a rotating word on a black background) barely got 3 frames per minute.
I now have a new pc better suited for graphical workloads but I feel you dude.

Edit: The name Potatosquad came from FixMatik but I launched it as a tag for low end or no GPU users. This is the post that started this movement.
 
Last edited:

atheran

Member
Feb 3, 2020
355
2,759
One thing you could do which should save a bit of time, proportionally to how long your renders are, is to turn off the convergence percentage calculation. I'm not sure how often it happens but it could be for every single sample that DAZ runs the algorithm to calculate the convergence percentage. If you want to try this you can set your Progressive Rendering settings to the following:

And, if you're not planning to use a denoiser, set Max Samples to some very large number and then just stop whenever you think it looks good.

Another thing which should improve render time on second-generation Maxwell GPUs is to turn on Optimise for Compute Performance in NVIDIA Control Panel for DAZ:

The recent renders I posted used 800 samples and were denoised afterwards. The total rendering time for my most recent one was 5 minutes 42.58 seconds on a GTX 970.
Wait, that last one was 800 samples on a 970 in about 6 minutes? I'll try those tomorrow. Right now I'm at 4h 30mins at about 5k samples. I don't have that option checked on my nvidia panel. I don't need 10 minutes renders. If I drop it to 30-60 minutes each I'd be really happy. Then again I'm pretty sure that volumetrics add a lot of time and computation to it. But I'll post tomorrow about how it worked out with your settings.


And here's the render at 5.2k samples. No denoiser.

Let's call it..Inspection day?
Siobhan_inspection_day.png

Don't ask me why the head is so big, I didn't change the model from the previous renders. Probably the camera angle or something.
Also..That dude inspecting her..As base of 8.1 as it can be. Which is why he looks like he came out of Life is Strange or something. I need to get the HD pack for 8.1 males.
 
Last edited:
5.00 star(s) 13 Votes