4.2.0 broken on Intel Mac Pro, AMD D500 GPU. Cycles > GPU Compute #120046

New Issue

Caco Oportot · 2024-03-29T05:13:01+01:00

Caco Oportot commented

2024-03-29 05:13:01 +01:00

System Information
Operating system: macOS Monterey 12.7.4 (21H1123)
Graphics card: AMD FirePro D500 3 GB

Mac Pro (Late 2013)
2,7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
AMD FirePro D500 3 GB

Blender Version
Broken: 4.2.0, e6808cd558, main, 03-29-2024
Worked: 4.2.0, 02a488d0fe, main, 03-24-2024

Broken Since: 4.2.0, ee38a7b723, main, 03-27-2024

**Fix #119906: Cycles compilation on device that don't use the light tree ** might be related and might have introduced this new issue

Short description of error
Blender fails to render (and viewport render) on Cycles when GPU Compute enabled.

Everything goes black on viewport. Look:

Render also fails:

Exact steps for others to reproduce the error
Launch Blender on default cube scene
Go to Render Properties and select Cycles and GPU Compute
Change Viewport Shading to Rendered... viewport goes all black.

If you try to Render the scene, it also fails to render.

**System Information** Operating system: macOS Monterey 12.7.4 (21H1123) Graphics card: AMD FirePro D500 3 GB Mac Pro (Late 2013) 2,7 GHz 12-Core Intel Xeon E5 64 GB 1866 MHz DDR3 AMD FirePro D500 3 GB **Blender Version** Broken: 4.2.0, e6808cd558f0, main, 03-29-2024 Worked: 4.2.0, 02a488d0fe2e, main, 03-24-2024 Broken Since: 4.2.0, ee38a7b723f8, main, 03-27-2024 **Fix #119906: Cycles compilation on device that don't use the light tree ** might be related and might have introduced this new issue **Short description of error** Blender fails to render (and viewport render) on Cycles when GPU Compute enabled. Everything goes black on viewport. Look: <video src="/attachments/489a26f4-4fdd-4e42-8ba6-362daa038c07" title="Render GPU Compute Screen Recording 2024-03-28 at 21.32.02.mov" controls></video> Render also fails: ![Screen Shot 2024-03-28 at 21.29.21.png](/attachments/85739b91-944a-474f-a67c-6d20c0ac388a) **Exact steps for others to reproduce the error** Launch Blender on default cube scene Go to Render Properties and select Cycles and GPU Compute Change Viewport Shading to Rendered... viewport goes all black. If you try to Render the scene, it also fails to render.

Render GPU Compute Screen Recording 2024-03-28 at 21.32.02.mov

6.2 MiB

Screen Shot 2024-03-28 at 21.29.21.png

2.4 MiB

Caco Oportot added the

labels 2024-03-29 05:13:02 +01:00

Caco Oportot changed title from ~~4.2.0 broken on Intel Mac, AMD GPU. Render/Viewport Cycles > GPU Compute, Mac Pro, Monterey 12.7.4~~ to 4.2.0 broken on Intel Mac, AMD GPU. Cycles > GPU Compute, Mac Pro, Monterey 12.7.4

2024-03-29 05:13:53 +01:00

Caco Oportot changed title from ~~4.2.0 broken on Intel Mac, AMD GPU. Cycles > GPU Compute, Mac Pro, Monterey 12.7.4~~ to 4.2.0 broken on Intel Mac, AMD GPU. Cycles > GPU Compute

2024-03-29 05:26:07 +01:00

Alaska commented

2024-03-29 06:17:05 +01:00

**Fix XXXXX: Cycles compilation on device that don't use the light tree ** might be related and might have introduced this new issue

This is unlikely, what's more likely is the changes that came before it, 082b68fcb9, fdc2962beb, introduced some sort of issue, but you couldn't test it until the fix from the commit you mentioned a4f1a52a5c.

Either way, using the system and Blender build found at the bottom of the comment, I ran these tests:

GPU rendering with M1 Pro GPU - Works fine.
Undefine all the features AMD GPUs with Metal have undefined (The most important one here is the light tree, but also MNEE, PRINCIPLED_HAIR and PATCH_EVAL) - When rendering with my CPU or my GPU, this worked fine.

This testing points to the black rendering being another AMD GPU on macOS specific bug. @iss Can you test on your AMD GPU mac?

System Information
Operating system: macOS-14.2.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2
Blender version: 4.2.0 Alpha, branch: main, commit date: 2024-03-29 02:29, hash: 3d2593b2296c

> **Fix XXXXX: Cycles compilation on device that don't use the light tree ** might be related and might have introduced this new issue This is unlikely, what's more likely is the changes that came before it, 082b68fcb9905e2e290e433ee67f1646146bbad8, fdc2962bebb47e5d55564fcf30b4586f57f4311a, introduced some sort of issue, but you couldn't test it until the fix from the commit you mentioned a4f1a52a5c11379981fc2009985fa7183957565f. Either way, using the system and Blender build found at the bottom of the comment, I ran these tests: 1. GPU rendering with M1 Pro GPU - Works fine. 2. Undefine all the features AMD GPUs with Metal have undefined (The most important one here is the light tree, but also MNEE, PRINCIPLED_HAIR and PATCH_EVAL) - When rendering with my CPU or my GPU, this worked fine. This testing points to the black rendering being another AMD GPU on macOS specific bug. @iss Can you test on your AMD GPU mac? **System Information** Operating system: macOS-14.2.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Pro 1.2 Blender version: 4.2.0 Alpha, branch: main, commit date: 2024-03-29 02:29, hash: `3d2593b2296c`

Richard Antalik commented

2024-03-30 20:18:27 +01:00

Can't reproduce with fresh alpha build.

Caco Oportot commented

2024-03-30 20:42:31 +01:00

Can't reproduce with fresh alpha build.

Issue still present latest daily alpha build (d7c718dfd4) on my Mac Pro with AMD FirePro D500 on Monterey 12.7.4 (21H1123)
It rendered fine until 4.2.0, 02a488d0fe, main, 03-24-2024

If I lower Performance to 1 thread, the render goes to full black just like the viewport

> Can't reproduce with fresh alpha build. Issue still present latest daily alpha build (d7c718dfd467) on my *Mac Pro with AMD FirePro D500 on Monterey 12.7.4 (21H1123)* It rendered fine until 4.2.0, 02a488d0fe2e, main, 03-24-2024 ![Screen Shot 2024-03-30 at 16.26.30.png](/attachments/ab999c50-7b98-42d6-b85d-57e7da68ed7d) <video src="/attachments/8db58965-37a4-4fa1-8a97-c34ce915a7ad" title="Render Cycles GPU Compute.mov" controls></video> If I lower Performance to 1 thread, the render goes to full black just like the viewport ![Screen Shot 2024-03-30 at 16.40.35.png](/attachments/cfc82ad4-0efa-470b-aa09-7322dd759900)

Screen Shot 2024-03-30 at 16.26.30.png

1.1 MiB

Screen Shot 2024-03-30 at 16.40.35.png

22 KiB

Render Cycles GPU Compute.mov

1.1 MiB

Caco Oportot commented

2024-03-30 20:55:53 +01:00

On '02a488d0fe2e' alpha daily build from 03-24-2024 it rendered an previewed on viewport just fine:

On '02a488d0fe2e' alpha daily build from 03-24-2024 it rendered an previewed on viewport just fine: ![02a488d0fe2e Screen Shot 2024-03-30 at 16.48.46.png](/attachments/cf113f87-a2c5-4226-a9f6-72bd9e518a33) <video src="/attachments/8c5e502a-a114-4547-aae1-231a1efb013f" title="02a488d0fe2e Render.mov" controls></video>

02a488d0fe2e Screen Shot 2024-03-30 at 16.48.46.png

1.1 MiB

02a488d0fe2e Render.mov

1.1 MiB

Caco Oportot changed title from ~~4.2.0 broken on Intel Mac, AMD GPU. Cycles > GPU Compute~~ to 4.2.0 broken on Intel Mac Pro, AMD D500 GPU. Cycles > GPU Compute

2024-03-30 22:36:02 +01:00

Alaska commented

2024-03-31 03:28:20 +02:00

@Caco-Oportot Issues with Cycles Metal GPU rendering on AMD GPUs on macOS have been quite common recently. It seems to be that Apple has been providing very little support to fixing bugs with the Metal drivers and/or compilers for these AMD GPUs.

The only way for the Cycles developers to fix these issues is to re-arrange code, and disable code until it starts working again. But to do this the Cycles developers need access to hardware that can reproduce the issue. Sadly it doesn't seem like we have access to that hardware. So it may take a while for this issue to be fixed, if it is to be fixed at all. (Note: The Cycles developers were thinking about removing MacOS AMD GPU support from Cycles in 4.2 due to all the issues it keeps having)

Sorry for the inconvenience this causes.

@Caco-Oportot Issues with Cycles Metal GPU rendering on AMD GPUs on macOS have been quite common recently. It seems to be that Apple has been providing very little support to fixing bugs with the Metal drivers and/or compilers for these AMD GPUs. The only way for the Cycles developers to fix these issues is to re-arrange code, and disable code until it starts working again. But to do this the Cycles developers need access to hardware that can reproduce the issue. Sadly it doesn't seem like we have access to that hardware. So it may take a while for this issue to be fixed, if it is to be fixed at all. (Note: The Cycles developers were thinking about removing MacOS AMD GPU support from Cycles in 4.2 due to all the issues it keeps having) Sorry for the inconvenience this causes.

😕 1

Caco Oportot commented

2024-03-31 03:38:37 +02:00

@Caco-Oportot Issues with Cycles Metal GPU rendering on AMD GPUs on macOS have been quite common recently. It seems to be that Apple has been providing very little support to fixing bugs with the Metal drivers and/or compilers for these AMD GPUs.

The only way for the Cycles developers to fix these issues is to re-arrange code, and disable code until it starts working again. But to do this the Cycles developers need access to hardware that can reproduce the issue. Sadly it doesn't seem like we have access to that hardware. So it may take a while for this issue to be fixed, if it is to be fixed at all. (Note: The Cycles developers were thinking about removing MacOS AMD GPU support from Cycles in 4.2 due to all the issues it keeps having)

Sorry for the inconvenience this causes.

@Alaska thank you for you honest reply. I thought there were more "Trashcan" (Mac Pro) users still, but it seems it´s not the case. Anyway, 4.1 would be good enough but it is also recently broken for this AMD system, not the same issue but metal related for sure. Please take a look: #119934

> @Caco-Oportot Issues with Cycles Metal GPU rendering on AMD GPUs on macOS have been quite common recently. It seems to be that Apple has been providing very little support to fixing bugs with the Metal drivers and/or compilers for these AMD GPUs. > > The only way for the Cycles developers to fix these issues is to re-arrange code, and disable code until it starts working again. But to do this the Cycles developers need access to hardware that can reproduce the issue. Sadly it doesn't seem like we have access to that hardware. So it may take a while for this issue to be fixed, if it is to be fixed at all. (Note: The Cycles developers were thinking about removing MacOS AMD GPU support from Cycles in 4.2 due to all the issues it keeps having) > > Sorry for the inconvenience this causes. @Alaska thank you for you honest reply. I thought there were more "Trashcan" (Mac Pro) users still, but it seems it´s not the case. Anyway, 4.1 would be good enough but it is also recently broken for this AMD system, not the same issue but metal related for sure. Please take a look: #119934

Alaska referenced this issue

2024-04-05 14:05:02 +02:00

Cycles render doesn't work on Intel Mac #120126

MCurto referenced this issue

2024-04-05 23:30:26 +02:00

Cycles render doesn't work on Intel Mac #120126

Alaska added

and removed

labels 2024-04-07 02:26:20 +02:00

Alaska commented

2024-04-07 02:36:14 +02:00

I am tentatively confirming this report.

While investigating #120126 we found out that some newer AMD GPUs on macOS (E.G. RX 580) also have this issue. However, even newer GPUs (E.G. Vega or RNDA1 did not has this issue).

There is still some investigation that needs to be done. For example when the RX 580 and Vega users ran this test, their Metal Language version was force set to 2.4. In a normal version of Blender 4.2, the Metal Language version for these users would be 3.1, which may or may not fix this issue. However I am waiting for !120299 to be merged into Blender before asking them to do further testing.

Just a note for @Caco-Oportot , in a normal versioin of Blender, the Metal Language version is determined by your macOS version. So macOS 12 uses 2.4, macOS 13 uses 3.0, and macOS 14 uses 3.1. If we find out that increasing the Metal Language version resolves this issue, then you may need to update your macOS version, assuming your mac still gets update.

I am tentatively confirming this report. While investigating #120126 we found out that some newer AMD GPUs on macOS (E.G. RX 580) also have this issue. However, even newer GPUs (E.G. Vega or RNDA1 did not has this issue). There is still some investigation that needs to be done. For example when the RX 580 and Vega users ran this test, their Metal Language version was force set to 2.4. In a normal version of Blender 4.2, the Metal Language version for these users would be 3.1, which may or may not fix this issue. However I am waiting for !120299 to be merged into Blender before asking them to do further testing. Just a note for @Caco-Oportot , in a normal versioin of Blender, the Metal Language version is determined by your macOS version. So macOS 12 uses 2.4, macOS 13 uses 3.0, and macOS 14 uses 3.1. If we find out that increasing the Metal Language version resolves this issue, then you may need to update your macOS version, assuming your mac still gets update.

Caco Oportot commented

2024-04-07 02:49:47 +02:00

Thank you @Alaska for taking the time to investigate further. Unfortunately my Mac Pro (Trashcan) does not get to run any macOS newer than 12.

I hope you find any workaround on the code that keeps us running 4.2.

Even 4.1 would be fine but also broken recently #119934

Thank you @Alaska for taking the time to investigate further. Unfortunately my Mac Pro (Trashcan) does not get to run any macOS newer than 12. I hope you find any workaround on the code that keeps us running 4.2. Even 4.1 would be fine but also broken recently #119934

Caco Oportot referenced this issue

2024-04-07 03:15:45 +02:00

Cycles render doesn't work on Intel Mac #120126

Caco Oportot commented

2024-04-09 22:39:36 +02:00

@Sergey I can report Cycles GPU Compute it still broken on 4.2.0 patch build #120299 PR120299 on my system:

System Information
Operating system: macOS Monterey 12.7.4 (21H1123)
Graphics card: AMD FirePro D500 3 GB

Mac Pro (Late 2013)
2,7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
AMD FirePro D500 3 GB

@Sergey I can report Cycles GPU Compute it still broken on 4.2.0 patch build #120299 [PR120299](https://builder.blender.org/download/patch/PR120299) on my system: System Information Operating system: macOS Monterey 12.7.4 (21H1123) Graphics card: AMD FirePro D500 3 GB Mac Pro (Late 2013) 2,7 GHz 12-Core Intel Xeon E5 64 GB 1866 MHz DDR3 AMD FirePro D500 3 GB

Alaska referenced this issue

2024-04-09 23:36:37 +02:00

Cycles render doesn't work on Intel Mac #120126

Alaska commented

2024-04-09 23:43:33 +02:00

@Caco-Oportot I should of been more clear. !120299 fixes a crashing issue on some AMD GPU Macs with macOS 14+. Since you are not on macOS 14, this does not benefit you. On a side note, since you weren't on macOS 14, you didn't have the crashing issue in the first place!

It seems that the issue you are experiencing (Cycles renders are black on AMD GPUs on macOS) is more wide spread that I thought with a Cycles developer (Sergey) able to reproduce the issue on a much more modern AMD GPU Mac (RDNA2 based AMD GPU Mac). So there is a increased chance that this issue can be investigated and fixed due to the wide spread impact and the developers having access to hardware to test it.

There is still the possibility that this issue doesn't get fixed and AMD GPU macOS support in Cycles will be removed in 4.2. But the final decision on whether or not to do this hasn't been made and discussion for what to do is planned to happen in the near future.

@Caco-Oportot I should of been more clear. !120299 fixes a crashing issue on some AMD GPU Macs with macOS 14+. Since you are not on macOS 14, this does not benefit you. On a side note, since you weren't on macOS 14, you didn't have the crashing issue in the first place! --- It seems that the issue you are experiencing (Cycles renders are black on AMD GPUs on macOS) is more wide spread that I thought with a Cycles developer (Sergey) able to reproduce the issue on a much more modern AMD GPU Mac (RDNA2 based AMD GPU Mac). So there is a increased chance that this issue can be investigated and fixed due to the wide spread impact and the developers having access to hardware to test it. There is still the possibility that this issue doesn't get fixed and AMD GPU macOS support in Cycles will be removed in 4.2. But the final decision on whether or not to do this hasn't been made and discussion for what to do is planned to happen in the near future.

👍 1

Caco Oportot commented

2024-04-10 00:00:33 +02:00

@Alaska thank you for clarifying. I can test (on my macOS 12 / AMD D500 GPU) any build you point me to if further investigation is done. Thanks!

Alaska added

and removed

labels 2024-04-10 02:52:37 +02:00

MCurto commented

2024-04-10 10:27:21 +02:00

I can confirm the new 4.2 alpha release from today is patched for the crashes.

It does have the blacked out GPU output on:

My iMac on latest Sonoma 14.4.1 +580X
and a 2019 MacPro on Ventura 13.6 +580X
EDIT: same on iMac Sonoma 14.4.1 with 570X

Same version (Intel version) runs fine on M2 Ultra GPU

Have some other GPU models on older Mac OS versions at my work place will try to find some time to test on some of them and report later.

EDIT2:

Tested a few more combos, all have blacked out GPU render and black Render Viewport on today's 4.2 alpha:

iMac Pro 2017 - Ventura 13.5.2 - Radeon Pro Vega 56
MacPro 2013 - Monterey 12.7.3 AMD FirePro D300
iMac Monterey 12.5.1 - AMD Radeon R9 M380

I can confirm the new 4.2 alpha release from today is patched for the crashes. It does have the blacked out GPU output on: My iMac on latest Sonoma 14.4.1 +580X and a 2019 MacPro on Ventura 13.6 +580X EDIT: same on iMac Sonoma 14.4.1 with 570X Same version (Intel version) runs fine on M2 Ultra GPU Have some other GPU models on older Mac OS versions at my work place will try to find some time to test on some of them and report later. EDIT2: Tested a few more combos, all have blacked out GPU render and black Render Viewport on today's 4.2 alpha: iMac Pro 2017 - Ventura 13.5.2 - Radeon Pro Vega 56 MacPro 2013 - Monterey 12.7.3 AMD FirePro D300 iMac Monterey 12.5.1 - AMD Radeon R9 M380

👍 1

~~Alaska referenced this issue 2024-04-10 10:52:00 +02:00~~

Regression: Slow renders on Intel Mac / AMD GPU #120006

Sergey Sharybin referenced a pull request that will close this issue

2024-04-10 15:46:03 +02:00

Fix #120046: Broken render on AMD Metal GPUs #120476

Sergey Sharybin referenced this issue from a commit

2024-04-11 10:51:57 +02:00

Fix #120046: Broken render on AMD Metal GPUs

Sergey Sharybin closed this issue

2024-04-11 10:51:58 +02:00

Blender Bot added