When WITH_OPENIMAGEDENOISE is OFF, cycles render does not output anything #115200

New Issue

Anthony Roberts · 2023-11-20T18:25:42+01:00

Anthony Roberts commented

2023-11-20 18:25:42 +01:00

System Information
Operating system: Windows 10/11
Graphics card: NVIDIA Quadro P600 / Qualcomm Adreno 690

Blender Version
Broken: Current master, I checked out a commit from before 4.0's release and it's been present since then at least
Worked: 3.x

Short description of error
When blender is built from source with WITH_OPENIMAGEDENOISE set of OFF, and cycles is used as the renderer, no output is given.

I suspect because an error is reported due to OIDN not finding a device (comes up in a big red box at the bottom).

Works fine in EEVEE (legacy) and WB.

Screenshot taken from machine with Quadro P600.

Exact steps for others to reproduce the error

Build a stock version of blender release with WITH_OPENIMAGEDENOISE set to OFF.
Open blender, and switch renderer to cycles (this issue happens even with default cube)
Click the render button
Observe no output

**System Information** Operating system: Windows 10/11 Graphics card: NVIDIA Quadro P600 / Qualcomm Adreno 690 **Blender Version** Broken: Current master, I checked out a commit from before 4.0's release and it's been present since then at least Worked: 3.x **Short description of error** When blender is built from source with `WITH_OPENIMAGEDENOISE` set of `OFF`, and cycles is used as the renderer, no output is given. I suspect because an error is reported due to OIDN not finding a device (comes up in a big red box at the bottom). Works fine in EEVEE (legacy) and WB. Screenshot taken from machine with Quadro P600. ![CyclesFailureOIDN.png](/attachments/b16c8046-88b0-491d-8875-a9d55f985e09) **Exact steps for others to reproduce the error** 1. Build a stock version of blender release with `WITH_OPENIMAGEDENOISE` set to `OFF`. 2. Open blender, and switch renderer to cycles (this issue happens even with default cube) 3. Click the render button 4. Observe no output

CyclesFailureOIDN.png

1.1 MiB

Anthony Roberts added the

labels 2023-11-20 18:25:43 +01:00

Thomas Dinges commented

2023-11-20 22:34:34 +01:00

Does it work if you disable "Denoise" in the render settings?

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-11-21 07:35:23 +01:00

Anthony Roberts commented

2023-11-21 10:00:26 +01:00

No

Anthony Roberts commented

2023-11-21 10:33:50 +01:00

Actually - yes, I was looking at the checkbox under "Viewport", oops....

I guess maybe this could be changed to a suggestion to disable denoising if there are no available options, or provide a clearer error, indicating denoising needs to be disabled?

Actually - yes, I was looking at the checkbox under "Viewport", oops.... I guess maybe this could be changed to a suggestion to disable denoising if there are no available options, or provide a clearer error, indicating denoising needs to be disabled?

Brecht Van Lommel commented

2023-11-21 13:37:50 +01:00

Can you explain why this is a problem? Was this encountered randomly while testing a build without this option, or are Windows Arm builds not expected to support OpenImageDenoise in the near future?

Generally it's not good to silently fail when a feature that is meant to be enabled is not. For example if you have a render farm and some machines silently render images without denoising, that should be a hard failure.

Can you explain why this is a problem? Was this encountered randomly while testing a build without this option, or are Windows Arm builds not expected to support OpenImageDenoise in the near future? Generally it's not good to silently fail when a feature that is meant to be enabled is not. For example if you have a render farm and some machines silently render images without denoising, that should be a hard failure.

Anthony Roberts commented

2023-11-21 13:46:17 +01:00

WoA builds right now do not have OIDN - I spoke to Xavier, and while it is on the roadmap, AFAICT there is no date on it so far.

I made a PR with no response: https://github.com/OpenImageDenoise/oidn/pull/183

I agree failing silently is not a good idea, however failing to render something with no indication (other than a box at the bottom of the non-modal window which disappears when you move the modal window) is also not what I would expect.

WoA builds right now do not have OIDN - I spoke to Xavier, and while it is on the roadmap, AFAICT there is no date on it so far. I made a PR with no response: https://github.com/OpenImageDenoise/oidn/pull/183 I agree failing silently is not a good idea, however failing to render something with no indication (other than a box at the bottom of the non-modal window which disappears when you move the modal window) is also not what I would expect.

Brecht Van Lommel referenced this issue from a commit

2023-11-21 19:11:59 +01:00

Cycles: clearer message when denoising in build without OpenImageDenoise

Brecht Van Lommel closed this issue

2023-11-21 19:12:00 +01:00

Blender Bot added

Status

Resolved

and removed

Status

Needs Information from User

labels 2023-11-21 19:12:03 +01:00