Geez I am so glad I found this thread!! Excellent research TheKD!! And great followup quesitons Padone!
I only discovered and started using Daz3d at the beginning of this month (Nov 2017) and had an AMD card and learned about iRay which prompted me to buy a 1080, no ti, and then discovered various nuances like vram not freeing up until after closing and also it hitting a hard limit on the ram avail etc and then found posts about scene optimizer and also NGS 2 and thought that upgrading to a 1080ti would solve my woe's, which I just got in today. After installing and trying to render a scene again it maxed out card memory at 8192!!:/ I found some articles about this issue and TCC hacks for previous cards to make them operate more like quadro/tesla/titan as a non video game type of card that would not drive a display etc (dangerous dark road!) and finally found this article...Thanks for all the posts!
Ah this old one .. Those were my first tests with DS/iray to find out what they were capable of. At this time I mainly use DS as a content generator for Blender, because DS is too much limited for my needs. And they didn't fix the log yet, apparently because it's a iray bug. So they say.
And you will always need the scene optimizer even with a Titan. This is because most DAZ content is not optimized at all to run on the gpu. Another good resource is the ghost light kit to help indoor convergence. And a final denoiser in GIMP will save you a lot of rendering time too.
Ah this old one .. Those were my first tests with DS/iray to find out what they were capable of. At this time I mainly use DS as a content generator for Blender, because DS is too much limited for my needs. And they didn't fix the log yet, apparently because it's a iray bug. So they say.
And you will always need the scene optimizer even with a Titan. This is because most DAZ content is not optimized at all to run on the gpu. Another good resource is the ghost light kit to help indoor convergence. And a final denoiser in GIMP will save you a lot of rendering time too.
Awesome! Thanks so much for the info and the links!
I have not tried Blender yet. I have looked at other things like octane render but I am not sure about how the materials and shaders work in other programs once exported. I have managed to get my gpu to utilize up to 10500 MB in iRay though and my renders are not as fast as I would like in scenes with props/building etc but I am going to keep researching and looking.
I think when DAZ Studio 1st starts an iRay render all the textures in the surfaces are seperate as it must make the individual iRay iteration calculations & adjustments to those surfaces and apply them to the final render but you'll notice as the render runs longer memory use decauses as iRay finishes having written the result of all the calculations to the rendered image it's use of each texture / map and unloads those texture maps and uses instead the calculated value of the rendered image for further iRay iterations. That's just guessing though, I certainly never had a hand in designing or programming nVidia's iRay engine.
Comments
Geez I am so glad I found this thread!! Excellent research TheKD!! And great followup quesitons Padone!
I only discovered and started using Daz3d at the beginning of this month (Nov 2017) and had an AMD card and learned about iRay which prompted me to buy a 1080, no ti, and then discovered various nuances like vram not freeing up until after closing and also it hitting a hard limit on the ram avail etc and then found posts about scene optimizer and also NGS 2 and thought that upgrading to a 1080ti would solve my woe's, which I just got in today. After installing and trying to render a scene again it maxed out card memory at 8192!!:/ I found some articles about this issue and TCC hacks for previous cards to make them operate more like quadro/tesla/titan as a non video game type of card that would not drive a display etc (dangerous dark road!) and finally found this article...Thanks for all the posts!
Ah this old one .. Those were my first tests with DS/iray to find out what they were capable of. At this time I mainly use DS as a content generator for Blender, because DS is too much limited for my needs. And they didn't fix the log yet, apparently because it's a iray bug. So they say.
And you will always need the scene optimizer even with a Titan. This is because most DAZ content is not optimized at all to run on the gpu. Another good resource is the ghost light kit to help indoor convergence. And a final denoiser in GIMP will save you a lot of rendering time too.
Do not rely on brute force gpu, it doesn't work.
https://www.daz3d.com/scene-optimizer
https://www.daz3d.com/iray-ghost-light-kit-2
Awesome! Thanks so much for the info and the links!
I have not tried Blender yet. I have looked at other things like octane render but I am not sure about how the materials and shaders work in other programs once exported. I have managed to get my gpu to utilize up to 10500 MB in iRay though and my renders are not as fast as I would like in scenes with props/building etc but I am going to keep researching and looking.
Thanks so much!
I think when DAZ Studio 1st starts an iRay render all the textures in the surfaces are seperate as it must make the individual iRay iteration calculations & adjustments to those surfaces and apply them to the final render but you'll notice as the render runs longer memory use decauses as iRay finishes having written the result of all the calculations to the rendered image it's use of each texture / map and unloads those texture maps and uses instead the calculated value of the rendered image for further iRay iterations. That's just guessing though, I certainly never had a hand in designing or programming nVidia's iRay engine.
I have had times it would run fine with GPU for a few thousand iterations, then suddenly drop to CPU and start the render from square 1 :(