Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
Issue ID
1196301
Regression
No
[Shader] changing lightloop.hlsl and going back to editor does not update ALL shaders which depend on it
Steps to reproduce:
1. download project and open scene
2. In project, find LightLoop.hlsl in Packages/com.unity.render-pipelines.high-definition/Runtime/Lighting/LightLoop
3. open LightLoop.hlsl and rename "ApplyDebug" to "1231231_ApplyDebug"
4. save and go back to editor window
5. observe shaders being refreshed, observe errors in console
6. clear errors
7. open LightLoop.hlsl and rename "1231231_ApplyDebug" to "ApplyDebug"
8. save and go back to editor window
9. observe shaders reimport, no errors
10a. In project, under Packages/com.unity.render-pipelines.high-definition, search "t:Shader"
10b. select all items (CTRL-A) and right click > reimport
11. observe errors persist on some shaders still
12. reimport lightloop.hlsl, reimport all shaders, observe errors are cleared now
Expected: no shader errors printed when reimporting (step 10)
Actual: some shaders are not updated (step 9) and errors are printed (step 10)
Reproduces: 2019.3.0b8 (7eb5456f98b4), 2020.1.0a8 (a932f1074310)
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.2):
This issue does not reproduce in 2020.1.0b8 or 2020.2.0a4