- Dec 5, 2019
- 12
- 159
My Shifter Ranger in D&D
Last edited:
- Aug 12, 2019
- 83
- 205
- Dec 28, 2020
- 125
- 4,387
- Apr 21, 2018
- 280
- 4,669
- Aug 12, 2019
- 83
- 205
Test render with blood. (3840x2160)
LQ mp4 with hair en cloth problems.
View attachment LQknifeA.mp4
Last edited:
- Nov 6, 2019
- 124
- 3,814
- May 25, 2020
- 22
- 170
- Jan 16, 2018
- 531
- 11,651
- Feb 7, 2018
- 250
- 2,073
This one seems worth it. Going to let it go for awhile.
Question: when you have a proper rig with a good GPU, do you get "better" iterations?
I'm 3000+ iterations all HDRI and still getting noise. Other people are talking about doing 200 iterations with lights and no noise. Curious if your getting more bang for your buck when it comes to iteration "quality" with a GPU.
- Jan 31, 2019
- 3,971
- 14,953
- Apr 25, 2020
- 1,090
- 8,062
As far as i know iterations quality (100 will be the same in every rig) are rig independent, but you'll reach more iterations faster, so technically you can get more iterations to get rid of the noise with the same time the weaker rig can, of course that will depend if your noise is just because you are rendering with low iterations or some other problem.
Rendering with a higher resolution and downscalling might help with a stronger rig too.
Edit: For anyone interested and dont know yet, the most important thing to GPU render after everything is loaded in the memory is Cuda Cores, the more the faster. (2k cuda cores gpu will render 2 times faster than a 1k cuda cores gpu)
Last edited:
- Jul 22, 2019
- 535
- 4,097
It's not just about the hardware. The more mesh polygons and maps you have in your scene, the more iterations are needed.
I render with a RTX 2070 8GB (also used for displaying), a simple character with hair (Iray, SubD level 2) and a HDRI environment will aprox. take 15 Minutes for Full HD. A scene like this one (Character with many HD morphs, hair, vellus & body hair, GP anatomy, all SubD level 4, all maps full resolution, environment objects, rendering size 3000 x 4000px) will take more than a day (27 hours in this case, no joke
). Edit: And it was about 48000, in words forty-eight thousand, iterations.
Last edited:
I mean, in theory you could have some dual CPU setup with 2 high end quadros and a ton of CPU ram that could do even the most complex renders in under a day. But most people don't have 50 grand in discretionary income sitting around...
- Nov 25, 2018
- 571
- 3,873
- Jan 31, 2019
- 3,971
- 14,953
- Sep 16, 2020
- 597
- 2,659
Last night's queue finished, playing with cloth shaders.
Margot
Margot
- Jul 20, 2018
- 724
- 1,185
Usually when you get into this long a render I'd say it is using the CPU to render the scene, not the GPU. It's too late now but when you start a render you should check if the last line before the actual renders start says CPU native code generated (or something along those lines.
If you are rendering this scene on CPU and renders other scenes normal on the GPU it usually means that that your scene is too complex and doesn't fit into the VRAM of the GPU.
Other things that increase render times and or atrifacts:
- low lighting (make sure the scene is well lit use postwork to decrease the lighting for low light scenes.)
- multi coloured lights. (don't use more than 3 colours)
- larger renders (e.g. Full HD vs 4k)
- Feb 7, 2018
- 250
- 2,073
#potatosquad over here. I'm CPU only rendering as a Mac user. One day might get a RTX laptop, but we'll see how the finances fall in the next year or so.
And I agree with the over exposing and bringing down in post. I haven't had great luck with it since with CPU previews in IRay it doesn't get far enough and when I see the hot spots they're way too gone to bring down later and by then I just give up on the render and move on. Happened in this one
Kate: "The rain got us pretty good, huh? Come her handsome and keep me warm."
