Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.4.16f1
2020.3
2021.1
2021.2
2021.2.0a11
Issue ID
1325521
Regression
Yes
Shader compilation errors are not shown when Editor is restarted
How to reproduce:
1. Open the user's attached "shader_errors" project
2. Reimport the "NewUnlitShader" (in the Project window right-click on the "NewUnlitShader"->Reimport)
3. Close and reopen the project
4. In the Project window select the "NewUnlitShader" Asset
5. Inspect the Inspector (Window->General->Inspector)
Expected results: Errors of the Shader are shown in the Inspector
Actual results: No errors of the Shader are shown in the Inspector
Reproducible with: 2019.4.16f1, 2019.4.23f1, 2020.3.1.1f1, 2021.1.1f1, 2021.2.0a11
Not reproducible with: 2018.4.33f1, 2019.4.15f1
Notes:
- Reimporting the Shader makes the errors appear again
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
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a14
Resolution Note (fix version 2021.1):
Fixed in 2021.1.4f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.6f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.25f1