Search Issue Tracker
Fixed in 6.6.0
Votes
0
Found in [Package]
4.9.0
Issue ID
1126569
Regression
No
SubAsset texture input in ShaderGraph not working
It seems that ShaderGraph does not properly handle the case where assets (textures) used as input are stored as SubAssets in the project, when serializating the shader.
Steps to reproduce:
- open included project
- open "New Shader Graph" with ShaderGraph editor
- Assign the two textures contained as SubAssets in "New TextureContainer" to the Sample Texture nodes in the graph
- Save the ShaderGraph asset
- Select "New Material"
Expected result:
The material inspector showing the two texture properties, both with the correct, different texture applied.
Actual result:
The material shows that the first SubAsset texture gets assigned to both texture properties in the shader. It seems that ShaderGraph does not handle the case where the asset is a SubAsset properly during serialization, and can only use the first SubAsset in the container.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The hover selection/highlight of items in the Insert button dropdown and the Documentation button dropdown are hard to see when hovered using the Light Editor theme
- NullReferenceExceptions appear when clicking to rename and then deleting the only GameObject in a scene
- Crash on "core::base_hash_set" when using nested [SerializeReference] fields in List<T> structures
- A ghost Game Window and multiple errors appear in the Editor when a Render Texture used by a Camera's "Target Texture" property is deleted
- Color Picker feels less smooth when dragging a Variables Color property in UI Builder Inspector
Add comment