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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Add comment