Daz 4.8 Iray renderes still noisy and dots abound, screenshot provided with render details...

Hello,, here is a render i just did over night, i think it might have taken 4 hours or somethig, not sure, i was sleeping. The imae looks pretty good, but it doesnt seem to be as complete and unnoisy as it should be. Can anyone look at my progressive rendering setting an tell me what I should tweak to get a more complete render? I am using a laptop with intel hd graphics, 8gb of ram so yeah its a tiny computer but iray does work! Thanks!


Screenshot_(32)_copy.jpg
1077 x 634 - 645K
Comments
If you didn't change the default setting for the IRay render engine the rendering will stop at which ever of the following comes first, 2 hrs or 5000 iterations or 95% convergence. If you don't have a fast processor and/or Nvidia graphics card 2 hrs may not be long enough for convergence to reach an acceptable percentage level.
Would 5000 iterations be enough to "finish" a 2560x1800 size image if I set the time to like 10 hours?
I was wondering about the convergence percentage, do I want to push tthat over to 100% in order to get an image with less dots? What about rendering quality? do I want to raise that any higher than 1?
How is your scene lit? is it open or enclosed? What are your tone mapping settings? If there isn't enough light, or if the light can't reach the area you are rendering, then the render will take longer to converge. If the scene is dimly lit and you don't adjust the tone mapping to compensate then the render will take longer to converge. A simple looking portrait render shouldn't take that long, I don't think your issue is the time/quality settings but the lighting or the tone mapping.
Looks an awful lot like a picture taken on a phone from about 6 or 7 years ago.
That screams to me lighting/tone mapping as opposed to not enough time. I've found that overall, not enough time to converge issues have a different look to them. Like the noise tends to be concentrated in certain areas, or there are a lot bright fireflies or other things along those lines...it looks a lot like the what it does after the first few iterations...but a bit more refined.
Not enough light/wrong exposure (tone mapping)...a more uniform noise/cheap camera photo look.
And that isn't just an Iray observation...it is similar in any PBR render I've seen/done.
Thanks for the observations! Tone mapping it seems like a lot to take in, anyone have a good tutorial for a new user? Don't worry I'll Google it too lol
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/interface/panes/render_settings/engine/nvidia_iray/tone_mapping/start
Just want to add that it is possible to adjust your tone mapping settings DURING render so you can see the effect without canceling/restarting.
On your render progress window, if you look on the left edge, there's a tiny handle you can click to pop up the render settings. You can adjust the progressive/filtering/tone mapping from here.
With that said, I still haven't found a magical tone mapping setting that works for all light sets and skin tones. Definitely something that needs adjusting per render unless you like the default look. ( who does?! )
Can we get a screEn shot of this handle?
Could you post a screen shot of Tone Mapping, Environment and the camera (if you have one setup) settings.
There are a couple in this thread:
http://www.daz3d.com/forums/discussion/comment/837965/#Comment_837965
Thank you. Found it.
Have a a render going, on 15 hours. I'm so happy with image, I'm willing to just let it go until it's finished. Then I tried adjusting ISO while rendering and it basically restarted the render?! Maybe I misunderstand the concept?
15 hours, ouch!
The restart issue is a recent development, some things have begun to trigger a restart, I'm not sure which.