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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Add comment