Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2020.2.0a15
2020.2.7f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1340531
Regression
Yes
[Shader System] The error location is incorrectly printed when using #line directives
How to reproduce:
1. Open the user's attached project
2. In the Project window, select BadShader
3. In the Inspector window, select Compile and show code
4. Observe the error
Expected result: the error occurs in the "source_file" (because of the 3rd line directive)
Actual result: the error occurs in the "this_should_not_show_up_in_the_error_message_because_of_the_next_line_directive"
Reproducible with: 2020.2.0a15, 2020.3.11f1, 2021.1.11f1, 2020.2.0a20
Not reproducible with: 2018.4.35f1, 2019.4.28f1, 2020.1.17f1, 2020.2.0a14
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a3
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b5
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.17f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.16f1