Search Issue Tracker
Fixed in 2.0.3
Votes
0
Found in [Package]
2.0.1
Issue ID
1041673
Regression
No
Possible to choose shader functions / shader graph nodes as a shader for a material
Currently looking for reproduction steps on this one, it happened after a shader graph shader failed to compile.
Basically the list of shaders to choose from becomes annoyingly huge as what shader functions (perhaps specific nodes) are added to this list of shaders that a material can choose from.
2018.2 w/ HDMasterMerge
Kink3d commented 17 days ago
Afaik this is not actually a bug. Its because of the regression tests in the repository. Each one generates a shader and we have one for each individual math node (with all the other nodes coming soon, so its only going to get worse).
The plus side is these wont exist in packages, the downside is this is incredibly annoying. Need a solution.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
Add comment