Cycles oneAPI: Incorrect rendering of "Window" texture coordinate. #118713

New Issue

Alaska · 2024-02-25T08:15:55+01:00

Alaska commented

2024-02-25 08:15:55 +01:00

System Information
Operating system: Linux-6.6.0-14-generic-x86_64-with-glibc2.39 64 Bits, WAYLAND UI
Graphics card: Mesa Intel(R) Arc(tm) A750 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 24.0.1-1ubuntu1

Blender Version
Broken version: 3.6.9
Broken version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-24 23:01, hash: 0f266ca3c99c
Broken version: 4.2.0 Alpha, branch: main, commit date: 2024-02-24 23:03, hash: 0a2544f2e8c8
Worked: 3.6.0 to 3.6.8, 4.0.2

Short description of error
When using a certain material in Cycles in oneAPI, rendering artifacts occur. The material is this (Anything making use of the Window texture coordinate option):

And in complex scenes, it creates results like this:

3.6.0 (Working)	3.6.9 (Broken)	4.1 (Broken)	4.2 (Broken)

Note: The glowing hand in the 3.6.0 result is caused by something else, and appears on all/most backends. I have already created a bug report for this.

Exact steps for others to reproduce the error
Option 1:

Download the Spring scene from the Blender foundation demo list: https://www.blender.org/download/demo-files/
Render it with oneAPI and compare it to other backends (E.G. CPU).

Option 2:

Create a scene that uses material that makes use of the Window texture coordinate option. Simple oneAPI issue scene.blend
Render it with oneAPI and compare it to other backends (E.G. CPU).

Extra notes:

I could not reproduce this issue on CPU or Metal GPU rendering. I haven't tested HIP or CUDA, but they likely do not have this issue.
I believe this issue may be Linux specific. But I have not tested Windows yet to confirm or deny this.

**System Information** Operating system: Linux-6.6.0-14-generic-x86_64-with-glibc2.39 64 Bits, WAYLAND UI Graphics card: Mesa Intel(R) Arc(tm) A750 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 24.0.1-1ubuntu1 **Blender Version** Broken version: 3.6.9 Broken version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-24 23:01, hash: `0f266ca3c99c` Broken version: 4.2.0 Alpha, branch: main, commit date: 2024-02-24 23:03, hash: `0a2544f2e8c8` Worked: 3.6.0 to 3.6.8, 4.0.2 **Short description of error** When using a certain material in Cycles in oneAPI, rendering artifacts occur. The material is this (Anything making use of the `Window` texture coordinate option): ![oneAPI culprit material.png](/attachments/3c3b2df8-78e2-4d16-b464-9fbef3560e7a) And in complex scenes, it creates results like this: |3.6.0 (Working)|3.6.9 (Broken)|4.1 (Broken)|4.2 (Broken)| |-|-|-|-| |![cycles_spring_3.6.0_ONEAPI_0.png](/attachments/cd3b0e05-83e1-41dd-894f-6afd8fb23d6d)|![cycles_spring_3.6.9_ONEAPI_0.png](/attachments/ad73d9c0-eb59-4d27-b815-c4a49a40c071)|![cycles_spring_4.1 - 0f266ca3c99c_ONEAPI_0.png](/attachments/a09162ac-f410-4b12-a5c1-de0c4aed9ec1)|![cycles_spring_4.2 - 0a2544f2e8c8_ONEAPI_0.png](/attachments/c0e2881a-8c71-42db-91d8-5d80bf88505a)| Note: The glowing hand in the 3.6.0 result is caused by something else, and appears on all/most backends. I have already created a bug report for this. **Exact steps for others to reproduce the error** Option 1: 1. Download the Spring scene from the Blender foundation demo list: https://www.blender.org/download/demo-files/ 2. Render it with oneAPI and compare it to other backends (E.G. CPU). Option 2: 1. Create a scene that uses material that makes use of the `Window` texture coordinate option. [Simple oneAPI issue scene.blend](/attachments/35faac9a-ab56-403f-8bfd-7cad39e41d37) 2. Render it with oneAPI and compare it to other backends (E.G. CPU). Extra notes: - I could not reproduce this issue on CPU or Metal GPU rendering. I haven't tested HIP or CUDA, but they likely do not have this issue. - I believe this issue may be Linux specific. But I have not tested Windows yet to confirm or deny this.

oneAPI culprit material.png

94 KiB

cycles_spring_4.1 - 0f266ca3c99c_ONEAPI_0.png

3.0 MiB

cycles_spring_3.6.9_ONEAPI_0.png

3.7 MiB

cycles_spring_4.2 - 0a2544f2e8c8_ONEAPI_0.png

4.5 MiB

cycles_spring_3.6.0_ONEAPI_0.png

2.8 MiB

Simple oneAPI issue scene.blend

888 KiB

Alaska added the

labels 2024-02-25 08:15:55 +01:00

Alaska commented

2024-02-25 08:17:09 +01:00

The most likely culprit to me is: f7ca183ff6

If this is the case, then the issue is most likely with the Intel compiler, not Cycles. Although I haven't tested to verify if this is the cause.

CC @xavierh just in case.

The most likely culprit to me is: https://projects.blender.org/blender/blender/commit/f7ca183ff6a0f5a4bbd574ffb66935a2f3cea6c0 If this is the case, then the issue is most likely with the Intel compiler, not Cycles. Although I haven't tested to verify if this is the cause. CC @xavierh just in case.

👍 1

Xavier Hallade commented

2024-02-26 18:20:43 +01:00

Thanks for this report @Alaska
I confirm the compiler update is the culprit and a newer version fixes it already.
I'll open a PR tomorrow to get it updated.

edit: I also confirm the issue is absent on Windows.

Thanks for this report @Alaska I confirm the compiler update is the culprit and a newer version fixes it already. I'll open a PR tomorrow to get it updated. edit: I also confirm the issue is absent on Windows.

👍 1

Xavier Hallade referenced a pull request that will close this issue

2024-02-27 20:09:53 +01:00

Build: Upgrade Intel Graphics Compiler to 1.0.15468 on Linux #118814

Xavier Hallade added

and removed

labels 2024-02-27 20:11:03 +01:00

Alaska referenced this issue