eevee pixel artifacts, holdout mixed with lightpathnode, reinforced with bloom and Dof #81092
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash:
Broken in 2.90 and 2.91
Worked: 2.83.5 2.83.6
Short description of error
Eevee produced pixelartifacts when using a holdout-shader for composting. Reinforced by bloom and Dof.
The rendered Image differs with different camera-settings for f-Stop.
Exact steps for others to reproduce the error
see file: render f12, there is a bright spot in the rendered image. change f-stop to 2.1, the bright spot dissapears.
Using 'is camera-ray' or' is shadow-ray' in the nodetree both produced the pixelartifacts.
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm.
It is related to Boom, Depth of Field (from the camera) and Transparence.
If you disable any of these, the problem goes away.
Should be fixed by new Depth of Field when merged (D10238).
This issue was referenced by
when i applyed the rotation of one object of the plane, the bright spot went away...
In #81092#1138744, @brothermechanic wrote:
not fixed in 2.93-master
(in 2.92 all is perfect)
Looks like issue was fixed in latest git!
Thank you, blender developers!
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?