Search Issue Tracker
Not Reproducible
Votes
2
Found in [Package]
7.1.6
Issue ID
1301965
Regression
No
[Big Sur][Metal] Warnings are thrown endlessly when creating a new HDRP project after shader compilation
Reproduction steps:
1. Create a new HDRP project
2. Observe the console
Expected result: Console is clean
Actual result: Console is being flooded with warnings
Warning: Metal: Fragment shader missing buffer binding at index 5 (g_vLightListGlobal / HDRP/Lit)
Reproducible with: 7.1.6, 7.3.1, 7.5.2, 10.2.2, 11.0 (2019.4.19f1, 2020.2.3f1, 2021.1.0b4, 2021.2.0a3)
Not reproducible with: 4.2.0-preview, 4.10.0-preview, 6.5.2-preview, 7.0.0, 7.1.5 (2018.4.30f1)
Comments (2)
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
YOSHIDA-Shinya
Jul 26, 2021 10:18
I see the exact same warnings when I activate GameView without enabling scene lighting.
Not randomly here. The warnings show up every time I launch the editor with the setting above and stop just after scene lighting is enabled.
MacBook Pro 16-inch, 2019
macOS Big Sur 11.4
Unity 2020.3.13f1
Wyldfire42
Feb 22, 2021 22:59
I see this regularly, but randomly. Most recently on Unity 2020.2.5f1, HDRP 10.3.1. Though it's happened intermittently on several earlier versions too.
Things like editing an Avatar config seem to provoke it, but not always. Once it's started happening though it tends to continue flooding the log until I quit/restart the editor.
But I've gone more than a week without seeing it at all too on the same build.
Once it happens I get visual artifacts, like the model being rendered as a black void.