MetalRT: Rendering being unresponsive with AO node #109899
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#109899
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
System Information
Operating system: Ventura 13.4.1
Graphics card: Apple M1 Max 32 Core
Blender Version
Broken: Blender 3.6 LTS
Worked: Blender 3.5.1
Short description of error
After downloading the newest Version of Blender it seems that using the Ambient Occlusion Node need leads to Blender being unresponsive. Sample count stays on 0 and neither Viewport nor F12 Render is starting as expected. Trying to quit, Blender crashes completely.
Exact steps for others to reproduce the error
Thank you for the report, could you please confirm if this is happening in Cycles or EEVEE?
Hi @sz , Could you try switch the graphics backend to
OpenGL
in the user preference and see if that makes any difference?Hi, it's happening in Cycles. I don't use EEVEE that much, so I can't tell if EEVEE has the same problem. Switching to OpenGL evokes the same error. I also tried to give Blender more time for the process, but after half an hour still stuck on 0 - Rendering doesn't start.
Geometry is just black. Screenshot attached.
Thanks, will point this in the direction of @Michael-Jones.
Hey @sz . I wasn't able to reproduce this on the latest Blender 3.6.1 RC on a M1 Max 32 Core running on Sonoma / 14 beta (test .blend scene attached):
On first render it can take a minute or so to build the render kernels, particularly if "AO" or "Bevel" nodes are used in a scene. Assuming it's not a case of waiting a bit longer and you're able to update to a macOS 14 beta build, then that would be a useful datapoint.
Hi @Michael-Jones, unfortunately I'm not able to try macOS 14 Beta at the moment. I tried 3.6.1 RC on macOS 13, but the problem still exists. For now I will stick to 3.5.1, but would love to switch to 3.6.1- if it’s working as expected.
Just found out that if I switch from GPU to CPU in Scene, Device - it work's, but missing the GPU Speed of course. So the problem seems to be related to GPU somehow. Also tried on a Mac Studio M1 with Factory Settings in Blender and Problem was exactly the same.
Anyone any ideas how to fix this?
I'm encountering the same issues. CPU works but it crashes when AO + GPU + Viewport is used. However, if I render the image it kind of works. The AO output is weird but it doesn't crash.
Apple M1 Pro 16GB, Ventura 13.4
In 3.6.3 RC if Metal RT is disabled und Render Device ist set to only GPU not CPU+GPU it works. AO renders in Viewport and actual Rendering. Result is as expected (same as it was in 3.5.1). Maybe this helps.
Similar bug has been observed on Windows + NVIDIA too: #102162
It seems MetalRT is still experimental so render time might be greater in some cases: https://projects.blender.org/blender/blender/src/branch/main/intern/cycles/blender/addon/properties.py#L1476
@Michael-Jones , can you confirm with this preference enabled?
Blender 3.6 on Macbook Pro M1to MetalRT: Rendering being unresponsive with AO node