MetalRT: Rendering being unresponsive with AO node #109899
Operating system: Ventura 13.4.1
Graphics card: Apple M1 Max 32 Core
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
- Add new material
- Add Ambient Occlusion Node
- Select cycles and GPU
- Enable MetalRT
- Start Viewport Rendering.
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.
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.
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
In 3.6.3 RC if Metal RT is disabled und Render Device ist set to only GPU not CPU+GPU it works
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?
No due date set.
No dependencies set.
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?