Blender 3.1 CPU/GPU rendering denoise is broken on M1 Mac / Monterey #96656

Open
opened 2022-03-20 19:10:23 +01:00 by Jeff Diamond · 12 comments

System Information
Operating system: MacOS Monterey (M1 Max)
Graphics card: Integrated GPU

Blender Version 3.1.0 release for M1 Macs
Broken: (example: 2.80, edbf15d3c0, master, 2018-11-28, as found on the splash screen)
Worked: (newest version of Blender that worked as expected) 2.93.3

Short description of error
On all my projects, when rendering via the CPU or GPU, the render works as expected, but on completion the entire screen blacks out to a solid color and the render is LOST! I suspected it must be a post render step, and I have confirmed that it is the DENOISER that is broken in this version of blender. When I go into the scene and remove the denoiser, the render completes, and I can save the image!

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
You need a project that uses denoising as a final compositing step. Attached is a simple matt object set to denoise at the end. Render it, and at the end you get a gray screen. Go into compositing and remove the denoise node, and you get the render.TestRenderWithDenoise.blend

**System Information** Operating system: MacOS Monterey (M1 Max) Graphics card: Integrated GPU **Blender Version** 3.1.0 release for M1 Macs Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) Worked: (newest version of Blender that worked as expected) 2.93.3 **Short description of error** On all my projects, when rendering via the CPU or GPU, the render works as expected, but on completion the entire screen blacks out to a solid color and the render is LOST! I suspected it must be a post render step, and I have confirmed that it is the DENOISER that is broken in this version of blender. When I go into the scene and remove the denoiser, the render completes, and I can save the image! **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible). You need a project that uses denoising as a final compositing step. Attached is a simple matt object set to denoise at the end. Render it, and at the end you get a gray screen. Go into compositing and remove the denoise node, and you get the render.[TestRenderWithDenoise.blend](https://archive.blender.org/developer/F12937041/TestRenderWithDenoise.blend)
Author

Added subscriber: @Jeff-Diamond

Added subscriber: @Jeff-Diamond

Added subscriber: @Memento

Added subscriber: @Memento

Added subscriber: @Nurb2Kea

Added subscriber: @Nurb2Kea

Plroblem is here...in the users blend file...
Screen Shot 2022-03-20 at 7.15.44 pm.jpg

Plroblem is here...in the users blend file... ![Screen Shot 2022-03-20 at 7.15.44 pm.jpg](https://archive.blender.org/developer/F12937112/Screen_Shot_2022-03-20_at_7.15.44_pm.jpg)
Author

One second - let me check if that is really the issue or if I just screwed up the sample because I keep hooking up / unhooking denoising to test... It would be strange indeed if that was in my original projects yet I never had an issue...

One second - let me check if that is really the issue or if I just screwed up the sample because I keep hooking up / unhooking denoising to test... It would be strange indeed if that was in my original projects yet I never had an issue...
Author

OK, I just confirmed that in the original projects I copied over, the image was indeed hooked up to the denoise node...
Stand by for more info.

OK, I just confirmed that in the original projects I copied over, the image was indeed hooked up to the denoise node... Stand by for more info.
Author

OK, this looks like a weird MIGRATION issue - it looks like very blender project I bring from 2.93/Intel to 3.1.0/M1Max has that one connection above to the denoiser broken! I'm not sure why this would happen, but at least it's an easy fix.

OK, this looks like a weird MIGRATION issue - it looks like very blender project I bring from 2.93/Intel to 3.1.0/M1Max has that one connection above to the denoiser broken! I'm not sure why this would happen, but at least it's an easy fix.
Author

Quick update - it looks like I'm having additional migration issues with loading my 2.93 blend files in 3.1 besides that one broken link to the denoise node involving animation, but I need to take some time and characterize it. But it's safe to say this is now a migration issue and not specifically a denoise issue, unless there's something intentional going on - by that I mean, maybe the reason that single link is breaking is because Blender has an issue with the old denoiser node?

Quick update - it looks like I'm having additional migration issues with loading my 2.93 blend files in 3.1 besides that one broken link to the denoise node involving animation, but I need to take some time and characterize it. But it's safe to say this is now a migration issue and not specifically a denoise issue, unless there's something intentional going on - by that I mean, maybe the reason that single link is breaking is because Blender has an issue with the old denoiser node?

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

Seems that noisy image pass is not available unless you enable denoising in cycles properties. Not quite sure if this was intentional and it was decided that nodes won't be re-routed automatically , but I don't see this mentioned in release notes or anywhere else, so will confirm.

As for other issues, please make new report for each new problem.

Seems that noisy image pass is not available unless you enable denoising in cycles properties. Not quite sure if this was intentional and it was decided that nodes won't be re-routed automatically , but I don't see this mentioned in release notes or anywhere else, so will confirm. As for other issues, please make new report for each new problem.
Contributor

Added subscriber: @Raimund58

Added subscriber: @Raimund58
Philipp Oeser removed the
Interest
Render & Cycles
label 2023-02-09 14:03:13 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#96656
No description provided.