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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment