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
- Number "0" is not visible in Unity Documentation page button tooltips
- Selected Korean input text in UIToolkit TextField is not fully replaced when refocusing and entering new input
- [UITK Controls] Non text InputField can't be reset by API
- Control Scheme name field has no character limit, causing “Add Control Scheme” window to expand if name is too long
- Prefab variants do not keep the values of linear drag and angular drag while upgrading the project from Unity 6000.0
Add comment