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
- Project Browser Icons use the wrong Theme and Users are not shown any indication that process will be deferred when switching Editor Theme in Play Mode
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
- UIElements memory allocations grow when interacting with IMGUI custom Editor window
- AI Navigation Preferences are not indexed for Search and cannot be found when searching for them in the Preferences Search field
Add comment