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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Add comment