Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.47f1
2021.3.23f1
2022.2.16f1
2023.1.0b13
2023.2.0a11
Issue ID
UUM-33433
Regression
No
[HDRP] Shader warnings are thrown in the Console window when switching to WebGL or Android Platforms in Build Settings
How to reproduce:
1. Create a new project using 3D Sample Scene (HDRP) Template
2. Go to File > Build Settings and switch to Android or WebGL Platform
3. Observe the Console window
Expected results: No warnings are thrown in the Console window
Actual results: Shader warnings are spammed in the Console window
Reproducible with: 10.10.1 (2020.3.47f1), 12.1.11 (2021.3.23f1), 14.0.7(2022.2.16f1), 15.0.5 (2023.1.0b13), 16.0.1 (2023.2.0a11)
Warnings:
{code:java}
Shader warning in 'GenSdfRayMap': HLSLcc: The resource 'rayMap' uses an unsupported type/format for read/write access at kernel GenerateRayMapLocal (on gles3){code}
{code:java}
Shader warning in 'GenSdfRayMap': HLSLcc: The resource 'rayMap' uses an unsupported type/format for read/write access at kernel RayMapScanX (on gles3){code}
{code:java}
Shader warning in 'GenSdfRayMap': Buffer count exceeding default GL_MAX_SHADER_STORAGE_BUFFER_BINDINGS. Shader might not work on all hw. Consider combining separate buffers into one containing struct elements. at kernel ClearTexturesAndBuffers (on gles3){code}
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Intercepted Events text is hardly visible in Inspector window for UI elements when Editor theme is set to Light
- [Hierarchy V2] Add new Query Block window contains a typo in the Hierarchy Search Area block
- Scene is not rendered in Player when ran with -force-d3d12 argument and GPU Resident Drawer enabled
- “Failed to load” window appears when a package’s docked window is opened and the package is uninstalled
- Properties window is not closed when the GameObject is deleted and the Properties window is not focused
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.