OSL OptiX Error in viewer or renderer when using Blender 3.5 Beta with OSL #105382

New Issue

Murad · 2023-03-02T19:44:47+01:00

Murad commented

2023-03-02 19:44:47 +01:00

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49

Blender Version
Broken: version: 3.5.0 Beta, branch: blender-v3.5-release, commit date: 2023-03-01 10:15, hash: ff89dfd6d283

Short description of error

"OSL group data size (2296) is greater than the maximum supported with OPTIX (2048)"

Exact steps for others to reproduce the error

Run a scene with OptiX.
Check OSL checkbox.

**System Information** Operating system: Windows-10-10.0.19042-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49 **Blender Version** Broken: version: 3.5.0 Beta, branch: blender-v3.5-release, commit date: 2023-03-01 10:15, hash: `ff89dfd6d283` **Short description of error** "OSL group data size (2296) is greater than the maximum supported with OPTIX (2048)" **Exact steps for others to reproduce the error** Run a scene with OptiX. Check OSL checkbox.

Murad added the

labels 2023-03-02 19:44:48 +01:00

Richard Antalik commented

2023-03-02 19:58:13 +01:00

I can not reproduce this issue. My steps were really just: Check OSL checkbox and render.

Murad commented

2023-03-02 20:01:26 +01:00

What does this error mean and is there any way to increase that OptiX pool?

Evan Wilson commented

2023-03-02 22:26:23 +01:00

Looks like the group data size was exposed in the OSL developer branch a month ago.

9ae5b69fd8

Looks like the group data size was exposed in the OSL developer branch a month ago. https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/commit/9ae5b69fd8738a276d45209fda28f763221c5bcc

Pratik Borhade commented

2023-04-14 06:34:50 +02:00

Hi, thanks for the report. Looks like array size in your case is more than 2048.
This error is shown intentionally, see: https://archive.blender.org/developer/D15902

Fixed funky behavior in some scenes due to the OSL group data array being too small, causing data to be written into the adjacent closure pool (and added an error message for cases where it is still to small, so that it's obvious; but this does require an OSL modification to be able to retrieve the necessary size of that array, see groupdata_size patch in osl.diff)

        if (groupdata_size > 2048) { /* See 'group_data' array in kernel/osl/osl.h */
          set_error(
              string_printf("Requested OSL group data size (%d) is greater than the maximum "
                            "supported with OptiX (2048)",
                            groupdata_size));
          return false;
        }

Not sure what groupdata_size attribute does. @pmoursnv 's knowledge will help in understanding this :)

Hi, thanks for the report. Looks like array size in your case is more than 2048. This error is shown intentionally, see: https://archive.blender.org/developer/D15902 ``` Fixed funky behavior in some scenes due to the OSL group data array being too small, causing data to be written into the adjacent closure pool (and added an error message for cases where it is still to small, so that it's obvious; but this does require an OSL modification to be able to retrieve the necessary size of that array, see groupdata_size patch in osl.diff) ``` ``` if (groupdata_size > 2048) { /* See 'group_data' array in kernel/osl/osl.h */ set_error( string_printf("Requested OSL group data size (%d) is greater than the maximum " "supported with OptiX (2048)", groupdata_size)); return false; } ``` Not sure what `groupdata_size` attribute does. @pmoursnv 's knowledge will help in understanding this :)

Pratik Borhade added

Module

Render & Cycles

Status

Needs Info from Developers

and removed

Status

Needs Triage

labels 2023-04-14 06:35:09 +02:00

Patrick Mours commented

2023-04-14 13:46:27 +02:00

Your material graph is too complicated. The memory for group data is currently hardcoded in Cycles to 2048 bytes and going beyond that is not supported, hence the error. Eventually this could be improved by dynamically allocating more memory upfront as needed, but at the moment this is intended behavior.