1
$\begingroup$

I've rendered an animation to an EXR image sequence and am now compositing it.

The glare node outputs a black square where the Nishta sky texture sun is. This does not happen when having the composite directly in the render. So I beleive I have done something wrong with the exporting options in the output or the glare node is f*ckd in 4.1, 4.0 and 3.6. I have not tested other versions.

The artifact in blender 3.6:

Rendering output. To be clear this the output for the 3d render itself and not the composite:

Even when the mix has been turn all the way to -1.0 it is still outputting a black square so it isn't an issue with glare it self:

Heres two frames showing how the black square changes from frame to frame depending on location:

First frame: Second frame:

The few frames after this remained as is shown in the second image until it disapered when the sun was out of frame.

Here is how it behaves with other glare types and the full node setup. I have tried turning off the nodes before the glare:

Improve this question
$\endgroup$
2
  • 1
    $\begingroup$ It feels more like a faulty EXR than something else. Maybe share your blend file with packed texture with blend-exchange.com. $\endgroup$
    – Lutzi
    Commented Jul 1 at 2:01
  • $\begingroup$ Here's the blend file with a frame connected. (blend-exchange.com/b/Koz240pK) $\endgroup$
    – thomThalas
    Commented Jul 1 at 7:25

1 Answer 1

Reset to default
0
$\begingroup$

I figured it out. The DWAA (lossy) compression caused it.

Changing the compression from DWAA (lossy) to zip (lossless) fixed the problem.

Either lossy compression gets weird at higher float values or DWAA is a bad compression choice for higher values.

Improve this answer
$\endgroup$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .