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
- [URP] SubmitRenderRequest with NativeRenderPass + Upscaling doesn't work
- “ArgumentOutOfRangeException” error appears when inserting a double character if using “SetValueWithoutNotify” on UI Toolkit’s TextField
- Particle System emission delays between particle generations when playing the simulation
- EditorUtility.DisplayDialog is not shown when Input.GetMouseButtonDown is called a second time
- Animator Enum Properties get set to 0 instead of the value specified in the Scene when the Property is animated by a State that is not playing
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