Hi, I’m trying to learn the BPT but there are some things you do not understand
- why worsens the appearance of rendering increasing the samples ?
I’ll add the link
- is there a direct illumination problem?
- besides using all samples with a value of 1, how do I fix that problem?
- BTP is still not ready project or are already mature as the PT?
can I use it in production?
- Do you know of any good tutorials? I have found very little on the net
I’m not able to reproduce the problem with the attached file. Are you using CPU or GPU?
The light path thing on the sun lamp is rather odd, but I think it should be ok? I would consider disabling MIS with the sky texture, or at least lowering the sample count to 1-2.
Again, I can’t reproduce the issue and I’ve never seen it in my own scenes.
I hardly ever use regular PT for anything. BPT is much more efficient on most scenes once you learn how to use it. FYI, Arnold’s only render mode is essentially BPT, there is no regular PT mode like Cycles has. I have never seen this widely complained about, and I wouldn’t use it if they added it. I recommend using the “square samples” option with branched path for simplicity’s sake.
There’s an older tutorial from Blender Cookie that is pretty thorough: https://cgcookie.com/archive/cycles-non-progressive-integrator/
Speaking of Arnold renderer, while this guide is written for it, the concepts pretty much apply the same to Cycles, as BPT is loosely based on Arnold’s integrator: https://support.solidangle.com/display/ARP/Removing+Noise
BTW, I wouldn’t use 14 for the AA sample level unless you have a specific reason to do so. (ie, depth of field noise, GPU timing out, etc). Try starting with AA=4, and adjust the subsample levels from there. If you have a lot of sample objects, or motion blur, or DOF, you might need to raise AA samples to something like 6-8, or maybe higher. Also, if you are using GPU, excessive subsample levels can cause the some OS to kill the driver/app for taking too long to respond, so lowering them and increasing AA to compensate can workaround that.
I am using GPU (GTX 580-3gb). Using the CPU the problem goes away!
Perhaps this will be a bug? I hope there is someone who tries some other gpu maybe newer than my!
what is a node copied from somewhere but I do not remember where
Using the CPU the problem goes away!
I know these tutorials but I have not been at all useful
thanks J_the_Ninja for all the other tips.
I will take even those
Hi, this is a bug.
I make report > https://developer.blender.org/T47461
I hope it will fixed for Blender 2.77
ohhh tnx very much man!!!
Yep, that was indeed a bug in the light falloff node in combination with a sunlamp. It should be fixed in the next nightly builds (and 2.77).
Thanks for mentioning and providing the file!
In case anyone cares, the fix is here: https://developer.blender.org/rBa8fe3a1ceef31ca39a455fee25bc1e361e1048ff