Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b7
Issue ID
920303
Regression
Yes
Shader using UsePass does not recompile when referenced shader is changed
How to reproduce:
1. Import users attached assets (Source shader, UsePass shader and a material)
2. Notice that Console produces two errors regarding Shader syntax. One for "ExampleSourceShader", another for "ExampleUsePass" shader that references to "ExampleSourceShader"
3. Fix the Source shader syntax error (uncomment 11th line of "ExampleSourceShader")
Expected result: Both errors are gone, since Source shader syntax error is fixed
Actual result: "ExampleUsePass" is still shown as having a syntax error in Shader, although its refrenced shader was fixed
Notes:
1. Reimporting "ExampleUsePass" shader fixes the issue
2. Only reproduces if "ExampleUsePass" shader is used by material
Regression introduced in - 2017.1.0a3
Reproducible - 2017.2.0a3, 2017.1.0b9, 2017.1.0a3
Not reproducible - 2017.1.0a2, 5.6.1p3, 5.5.4f1
Fixed in 2017.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment