Vlado-
I thought about putting this in the problems section but I'm not sure what all is going on behind the scenes. I'm not sure its so much a problem as it is a limitation of the current implementation. I ran this setup with both the Progressive Path Tracer and the BDPathTracer. In both cases I set the total samples to the max 65k and was surprised to see that the BDPathTracer Ran out/finished in a touch over 8min, but with still a lot of variance. I stopped the Progressive Path Tracer at roughly the same point, even though it was suggesting it would continue on for several hours to hit the max samples.
Id love to know whats going on under the hood that the BDPathTracer ran out of sample so quickly, or is there another heuristic that is determining when to have the render stop. I guess this also begs the question what in the future might you do to not have the render stop until the image reaches some variance threshold?
Here is the Pathtracing version.
Here is the BDPathTracing version
Thanks!
-Michael
I thought about putting this in the problems section but I'm not sure what all is going on behind the scenes. I'm not sure its so much a problem as it is a limitation of the current implementation. I ran this setup with both the Progressive Path Tracer and the BDPathTracer. In both cases I set the total samples to the max 65k and was surprised to see that the BDPathTracer Ran out/finished in a touch over 8min, but with still a lot of variance. I stopped the Progressive Path Tracer at roughly the same point, even though it was suggesting it would continue on for several hours to hit the max samples.
Id love to know whats going on under the hood that the BDPathTracer ran out of sample so quickly, or is there another heuristic that is determining when to have the render stop. I guess this also begs the question what in the future might you do to not have the render stop until the image reaches some variance threshold?
Here is the Pathtracing version.
Here is the BDPathTracing version
Thanks!
-Michael
Comment