Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.2.X, 2018.4.X, 2019.1.X
Votes
0
Found in
2018.1.0b7
Issue ID
1002833
Regression
Yes
[Shaders] Surface shaders don't track #include dependencies properly
To reproduce:
1) Create new project
2) Create Surface Shader
3) Create "Test.cginc" file
4) Open Surface Shader
5) Add '#include "Test.cginc"' to it
6) Open Test.cginc
7) Write some gibberish to make an error
8) Save and return to editor
9) Notice the error in the surface shader
10) Go back to Test.cginc
11) Delete all and save
12) Go back to Unity
Expected: The error disappears
Actual: The error stays
Reproduced in 2018.1.0a3, 2018.1.0a5, 2018.1.0a7, 2018.1.0b1, 2018.1.0b7
Not reproduced in 2018.1.0a2, 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment