Cycles renders shows black during rendering huge resolutions #93350

New Issue

Jeroen Bakker · 2021-11-24T10:16:43+01:00

Jeroen Bakker commented

2021-11-24 10:16:43 +01:00

System Information
Operating system: Linux-5.13.0-7620-generic-x86_64-with-glibc2.33 64 Bits
Graphics card: Radeon RX Vega (VEGA10, DRM 3.41.0, 5.13.0-7620-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.2.2

Blender Version
Broken:

version: 3.0.0 Beta, branch: master, commit date: 2021-11-24 09:05, hash: 785503a7e4
version 3.1.0 Alpha

Worked:

version: 2.93.6 official release.

Short description of error
When rendering an image with a resolution of 20000x10000 makes the intermediate result fully back. The transparency checkerboard also doesn't show in this case. After rendering the image is correct.

Exact steps for others to reproduce the error

Start Blender
Set render engine to cycles
Set render resolution to 20000x10000
Disable denoising (has nothing to do with the error, except that it would be very time consuming.)
Press F12

I was able to render with 16000x8000

Screenshot during rendering

system-info.txt

**System Information** Operating system: Linux-5.13.0-7620-generic-x86_64-with-glibc2.33 64 Bits Graphics card: Radeon RX Vega (VEGA10, DRM 3.41.0, 5.13.0-7620-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.2.2 **Blender Version** Broken: * version: 3.0.0 Beta, branch: master, commit date: 2021-11-24 09:05, hash: `785503a7e4` * version 3.1.0 Alpha Worked: * version: 2.93.6 official release. **Short description of error** When rendering an image with a resolution of 20000x10000 makes the intermediate result fully back. The transparency checkerboard also doesn't show in this case. After rendering the image is correct. **Exact steps for others to reproduce the error** * Start Blender * Set render engine to cycles * Set render resolution to 20000x10000 * Disable denoising (has nothing to do with the error, except that it would be very time consuming.) * Press F12 I was able to render with 16000x8000 Screenshot during rendering ![Screenshot from 2021-11-24 10-10-20.png](https://archive.blender.org/developer/F11969698/Screenshot_from_2021-11-24_10-10-20.png) [system-info.txt](https://archive.blender.org/developer/F11969725/system-info.txt)

Jeroen Bakker commented

2021-11-24 10:16:43 +01:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker changed title from ~~Cycles renders black when rendering huge resolutions~~ to Cycles renders shows black during rendering huge resolutions

2021-11-24 10:19:58 +01:00

Garek commented

2021-11-24 12:04:24 +01:00

Added subscriber: @Garek

Garek commented

2021-11-24 12:04:24 +01:00

Can confirm. Black shows as long as either X or Y resolution are greater than 16384 (which is 2^14).
When I switch to Eevee I get an error about texture size limit, might be related?

Can confirm. Black shows as long as either X or Y resolution are greater than 16384 (which is 2^14). When I switch to Eevee I get an error about texture size limit, might be related? ![изображение_2021-11-24_160342.png](https://archive.blender.org/developer/F11979081/изображение_2021-11-24_160342.png)

Sergey Sharybin self-assigned this 2021-11-24 14:31:57 +01:00

Sergey Sharybin commented

2021-11-24 14:39:06 +01:00

This issue indeed roots into the same limitation as @Garek pointed out: OpenGL has a limit on the texture size and in Cycles for 3.0 we are allocating one single texture for the final result. Technically it is a regression compared to 2.93, but not sure whether there is a way around it.

Guess the proper solution is to allocate multiple texture in the BlenderDisplayDriver when the render result does not fit into limitations of the OpenGL.

Marking as high priority to allow classify whether it is something we aim to be resolved before 3.0.

This issue indeed roots into the same limitation as @Garek pointed out: OpenGL has a limit on the texture size and in Cycles for 3.0 we are allocating one single texture for the final result. Technically it is a regression compared to 2.93, but not sure whether there is a way around it. Guess the proper solution is to allocate multiple texture in the `BlenderDisplayDriver` when the render result does not fit into limitations of the OpenGL. Marking as high priority to allow classify whether it is something we aim to be resolved before 3.0.

Jeroen Bakker commented

2021-11-24 14:44:10 +01:00

Best to keep the texture to 8Kx8K. The reported max resolution of the gl driver doesn't mean that allocation of smaller textures always work.

Dalai Felinto commented

2021-11-24 15:59:27 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Brecht Van Lommel commented

2021-11-24 16:00:12 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2021-11-24 16:00:12 +01:00

Maybe we could allocate one texture per tile, and limit the max tile size to 8k?

Sergey Sharybin commented

2021-11-24 16:00:54 +01:00

Good to know.

And to clarify: this but is something what is very nice to be fixed soon, but we do not consider this a stopper for 3.0.

Good to know. And to clarify: this but is something what is very nice to be fixed soon, but we do not consider this a stopper for 3.0.

Sergey Sharybin commented

2021-11-24 16:07:02 +01:00

@brecht, That is definitely a possibility, and it does sound like it is simplest/cleanest approach. I'd need to think a bit about what exactly that'd mean for the display driver and graphics interop API.

Raimund Klink commented

2021-11-24 16:55:26 +01:00

Added subscriber: @Raimund58

Raimund Klink commented

2021-11-30 01:57:53 +01:00

Just to create a link:
D13385: Fix #93350: Cycles renders shows black during rendering huge resolutions

Just to create a link: [D13385: Fix #93350: Cycles renders shows black during rendering huge resolutions](https://archive.blender.org/developer/D13385)

Vladimir commented

2021-11-30 05:09:13 +01:00

Added subscriber: @Wovchick