Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
Issue ID
1269484
Regression
No
Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
ShaderGraph and custom shader creation solutions utilizing ShaderUtil.CreateShaderAsset() and ShaderUtil.UpdateShaderAsset() API, can't register shader include dependencies or handle asset relative paths correctly due to missing AssetImportContext. New API overloads with possibility to pass in AssetImportContext need to be added in order fix this.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment