Cycles Apple Metal device feedback

The latest Blender 3.1 and 3.2 builds now have initial support for AMD graphics cards. However this requires macOS 12.3, which is still in beta.

Obviously there is risk involved in installing a beta operating system, so I wouldn’t necessarily recommend everyone to go and do that. But if there’s anyone that has it installed, it would be good to hear how it works.

11 Likes

…as soon as D14081 lands!

1 Like

Ah, I was wondering which “OS update” Jason was referring to. I kinda hoped it was the 12.2.1 update that showed up today.

The Blender system settings panel now shows a ‘Metal’ header and ‘MetalRT’ checkbox, but it doesn’t recognise my AMD 580X video card yet.

Going to sit on my hands a bit more then :slight_smile:

I forgot about this, the latest builds have this now also.

1 Like

I tested couple of benchmark files with a few different settings for those interested.

System
macOS Monterey 12.2
MacBook Pro 14"
M1 Pro with 8-core CPU, 14-core GPU
RAM: 32 GB

Blender Version
Blender 3.2.0-alpha arm64 (467c16eab1ec)
Daily Build: Feb 11

Tests

bmw27 (Low Power)

Metal + CPU :           5:21.45 (321.45 sec)
Metal + GPU :           1:35.36 (95.36 sec)
Metal + MetalRT + CPU : 5:18.84 (318.84 sec)
Metal + MetalRT + GPU : 1:34.04 (94.04 sec)

bmw27 (Low Power Disabled)

Metal + MetalRT + CPU : 4:25.85 (265.85 sec)
Metal + MetalRT + GPU : 1:30.25 (90.25 sec)

classroom (Low Power)

Metal + MetalRT + CPU : 11:52.79 (712.79 sec)
Metal + MetalRT + GPU :  3:36.54 (216.54 sec)

classroom (Low Power Disabled)

Metal + MetalRT + CPU : 9:52.78  (592.78 sec)
Metal + MetalRT + GPU : 3:24.30  (204.30 sec)

*I can add screenshots of the results if anyone is interested to see the results

Checking the MetalRT in preferences seem to show a few seconds improvement on the first test. I therefore decided to test the others with the option enabled.

I did not encounter any crashes during these tests with this build. I also spend a couple of hours building Earth from Blue Marble data and using Eevee and Cycles. Eevee render took less than a second, while Cycles took close to six seconds. Viewport was also very usable on both Cycles and Eevee.

Very impressed with how well this works and having switched to a Mac for work, glad to be able to get back to using Blender.

3 Likes

I’m getting this error after loading render kernels
(Radeon Pro 555, MacOS 12.3 beta)

2 Likes

Whenever I try to go into rendered view with Radeon 5500 XT (external), I am stuck at Loading render kernels and MLT Compiler service is using 95% of CPU and 12 GB of RAM (I only have 8 GB :thinking:) If I try and go back into solid view/another viewport shading, it freezes and I have to force quit blender.
Using Blender 3.2 (Feb 12), macOS 12.3, AMD Radeon RX 5500-XT (External), Late-2019 MacBook Air

Edit: After letting my computer sit for a while, I ended up getting the same error as @KudeKube

While Metal cannot beat Optix yet I think we should find it really impressive the M1 Max compares well with the AMD 6900 XT from what little information I have been able to find so far. At least for the BMW benchmark the 6900 XT seems to be about 2.43x slower than Optix which seems to put it on par with what others have seen with the M1 Max. Other benchmarks may be different of course.

2 Likes

Same result here as other AMD users:

iMac 19,1 with 580X , Mac Os 12.3 beta 2.

Both latest 3.1 beta and 3.2 alpha do have a Metal pane selector in Cycles Render devices but gives error after compiling kernels:

Failed to create compute pipeline state “integrator_init_from_camera”,error: Compiler econterer an internal error

D14018 Is already closed, wouldn’t that mean that the kernel issue should be solved?

1 Like

I was just about to ask the same as @SkylineX as it looks to be the problem from what I know. Was it late for todays build so it would be in the next build?

I opened the D14018 page yesterday, but didn’t check if it was open or closed. I just updated my Mac to 12.3 this morning and couldn’t test out the GPU rendering on Feb 11 build. Perhaps when the Feb 13 build is out we should test it again. If not, all we can do is wait…

Edit: I checked the log and it appears as if it was closed on Feb 11 @11:53 PM which would make it late for today’s build.

Hi everyone. Apologies if this is the improper forum.
I’m running Blender 3.1 Beta on an 16" M1 Max 24-core, Mac OS 12.1, and I’m getting the message:
“No compatible GPUs found for Cycles. Requires Apple Silicon and macOS 12.0 or newer.”
Does anyone know what’s going on?

That is weird. Try installing a different build of Blender? Daily builds here. If there are any updates to macOS, do those.

2 Likes

Thanks for the reply!
Hmm… Yeah, I just installed the newest build today from there. But it looks like I have an update available for OS 12.2.1, so I’ll try that and report back!

2 Likes

Update!
That strange message is fixed after updating to 12.2.1 and everything seems to look normal!
Looks like the compatibility warning should perhaps be increased to macOS 12.2 or later.

1 Like

Yay! Now we just wait for tomorrow’s build for GPU support on AMD cards.

Just rebuilt, the compiler error is still there. :frowning:

Yeah I had to try it myself and still the same error.

1 Like

Just tested it, didnt work :sob: