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
- Flickering orbs appear when using RenderTargetHandle
- UsePass for ShaderLabShader is ignored and GameObjects are not rendered when SRPBatcher is enabled
- Animated model translated down when interrupting a transition
- UI Toolkit text splits when changing PanelSettings scale
- Error "NullReferenceException" is thrown when selecting folders from the folder panel or closing the folder panel with EditorUtility.OpenFolderPanel() in use
Add comment