Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
0
Found in
2020.2.0a13
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1318689
Regression
Yes
Errors shown in the Console window point to the incorrect line number in shader code
How to reproduce:
1. Open the attached project "ShaderLineNumberErrorExample.zip"
2. Open the "SampleScene" scene
3. Reimport "ErrorShader" ("Shaders" folder)
Expected result: Console window reports error on line 47
Actual result: Console window reports error on line 45
Reproducible with - 2020.2.0a13, 2020.3.0f1, 2021.1.0b7, 2021.2.0a8
Not reproducible with - 2018.4.30f1, 2019.4.22f1, 2020.2.0a12
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a11
Resolution Note (fix version 2021.1):
Fixed in 2021.1.2f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.5f1