Page MenuHome

OpenEXR file with only R channel fails to read
Confirmed, LowPublicKNOWN ISSUE

Description

System Information
Operating system: Linux Mint 19.1
Graphics card: GTX 1080ti / latest drivers

Blender Version
Broken: Current nightlies and own builds of 2.79 and 2.80
Worked: Official 2.79b and older nightlies (can't tell exactly when the problem started to occur, maybe 2 weeks?!)

Short description of error
If I render a simple multilayer EXR without a Z channel and load the resulting image file in e.g. Blender's image editor it looks black with an alpha although during rendering it looked OK.
Rendering with a Z channel gives the correct result.

Exact steps for others to reproduce the error

  • Open this scene:
  • Press CTRL+F12 to render (it's a simple Suzanne with a point light)
  • Load the EXR e.g. into the compositor or Blender image editor -> It turns black
  • Load the image in an external image editor -> all is fine

It looks like Blender can't properly read its own layers any more.

Event Timeline

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.

I'm not sure if it's the same bug, but I've got an exr (a zbrush displacement map) that renders black in eevee, shows up black in the image / UV editors, but renders greyscale in cycles. It shouldn't have a Z pass, so maybe this is a similar bug. I'm attaching an exr and a test .blend (toggle between lookdev and rendered to see it in eevee/cycles)

small addendum: I'm on gnu/linux (fedora 29), using intel cpu and nvidia gpu (i7/1080)

The JokerGargle_Displacement.exr is a different case than the original report. It has a single "R" channel. I'll keep the report open for that case.

Brecht Van Lommel (brecht) renamed this task from Multilayer EXRs without Z channel give weird results to OpenEXR file with only R channel fails to read.Jul 17 2019, 8:58 PM
Brecht Van Lommel (brecht) changed the task status from Resolved to Unknown Status.
Brecht Van Lommel (brecht) lowered the priority of this task from 50 to Low.
Richard Antalik (ISS) changed the subtype of this task from "Report" to "Known Issue".

Still problem with JokerGargle_Displacement.exr

Sean Kennedy (hype) added a comment.EditedApr 19 2020, 12:35 AM

I've also run into this bug using the latest stable build of Blender 2.82a. Working on the workflow for STmap lens distortion/undistortion, the STmap I created in Nuke kept importing into Blender as completely black. When I added in a depth pass (not any real information, just a solid color value in the depth channel) and re-saved the EXR, it worked fine.

Including two EXR images, with and without zdepth channel, and a screenshot of both EXR images in Blender's compositor.

I created the same image in Natron instead of Nuke, and it worked fine. I did NOT include the z depth pass in this EXR. Otherwise, I used all the same image output settings that I used when rendering from Nuke.

Looks like it is naming related. The "..no_depth_pass.." exr shows up as Color.XY instead of Color.RGBA in Natron.

Someone please test Quixel .exr files, same issue seems to me and i cannot use roughness map because of that. Blender 2.83 Win 10 x64

Yup, any grayscale-type map downloaded as EXR from Quixel is unusable in Blender because it stores the data in a single R channel with no GBA channels.

I really hope 2.83.1 fixes that, i often want to preview scene/mesh/texture with PBR before moving target object to Unreal. I use .exr files directly in Blender without Bridge for quick preview but now it is not working because of this bug.

Anyone knows workaround for this? 2.83.1 still do not work. How to get that Z channel thing to work?