Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0b5
Issue ID
916386
Regression
No
Changing files included in compute shader doesn't compile before compute shader is changed
Steps to reproduce:
1. Open the attached project (ComputeIncludeCompilationExample.zip)
2. Open ComputeGlobals.compute and uncomment the 4th line and save the file
3. Go back to Unity, you will see no compilation errors
4. Open ComputeShader.compute insert an extra space somewhere and save the file
5. Go back to Unity, you will see a compilation error
Expected result: Unity should throw the error after you have changed the files included in a compute shader
Actual result: Unity does not throw the error
Note:
The compile error will also list a line inside the compute shader instead of the included file making it hard to track down where an error is occurring if multiple include files are used
Reproduced with: 5.4.5p2, 5.5.4f1, 5.6.1p2, 2017.1.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment