Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
4
Found in
2019.3.0a8
2019.3.0f1
2020.1
Issue ID
1215034
Regression
Yes
[Shaders] Change in included hlsl file does not always trigger recompilation
How to reproduce:
1. Open attached project "ShaderErrorAfterCommenting.zip" and scene "SampleScene"
2. In Project window, open "SampleNormal.hlsl" with Visual Studio
3. In Visual Studio, comment line 3 (int index = 0;) save changes
4. In Editor, click on "LitSimple" file
5. Observe the Inspector window or Console window (an error is thrown, if not, repeat steps 3 - 5, commenting/uncommenting the line)
Expected result: "Shader error in 'Lit/Shadow Casting': undeclared identifier 'index' at Assets/SampleNormal.hlsl(5) (on d3d11)" is thrown everytime
Actual result: sometimes no errors are thrown
Reproducible with: 2019.3.0a8, 2019.3.0f6, 2020.1.0a21
Not reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.20f1, 2019.3.0a7
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Verified in: 2020.2.0a5
Resolution Note (fix version 2020.1):
Fixed in:
2020.1.0b4.3439
Resolution Note (fix version 2019.3):
Verified in: 2019.3.8f1