Search Issue Tracker
Duplicate
Votes
2
Found in [Package]
3.2.2
Issue ID
PPB-5
Regression
No
[PostProcessing] Kernel 'KEyeHistogramClear' errors are spammed when Platform is set to Android in the Build Settings
How to reproduce:
1. Open the user's attached project
2. Open the "Task_1_City" Scene
3. Hover with a mouse in the Scene view
4. Observe the Console log
Expected result: No abnormal behaviour is detected
Actual result: "Kernel 'KEyeHistogramClear'"-related errors spammed in the Console log
Reproducible with: 3.2.2 (2021.3.2f1, 2022.1.0f1, 2022.2.0a12)
Couldn't test with: 3.2.0 (2019.4.38f1), 3.2.2 (2020.3.34f1) (downgrading errors)
Thrown errors:
Kernel 'KEyeHistogramClear' not found
ArgumentException: Kernel 'KEyeHistogramClear' not found.
-
Resolution Note:
Effects which require compute shaders are disabled when this is not supported on the target platform. An warning message has been added to the editor to indicate this.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/PPB-6
Comments (2)
-
lmlab
Sep 01, 2023 16:23
2022.3.2f1
Getting spammed by "Kernel 'KEyeHistogramClear' not found" in WebGL. -
problemecium
Jun 22, 2023 21:20
Confirmed NOT resolved as of 2023.1.0b20. My project was fine, then I switched its platform to WebGL and now this error message is spammed in the Console from the moment I start the Editor.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #-6