Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
5.3.3p2
Issue ID
775269
Regression
No
Compute shaders get included to every Assembly-CSharp-* project that has at least one single script in it
Compute shaders get included to every Assembly-CSharp-* project that has at least one single script in it.
If there are no scripts in the project, ".compute" files don't end up in any VS project - double clicking it merely opens it up in Visual Studio. If there are no editor or firstpass C# scripts in the project, it ends up in the only project that exists. If there are editor or firstpass C# scripts, the ".compute" shader file ends up in all the project, which causes issues when double clicking it in the solution explorer (picture attached).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment