Search Issue Tracker
Fixed
Votes
0
Found in
2022.3.13f1
2023.3.0a13
Issue ID
UUM-55392
Regression
Yes
Properties can't be added to the Shader Graph after trying to convert a node to a Property
How to reproduce:
1. Create a new URP Template project
2. Right-click in the Project window → Create → Shader Graph → Choose any Shader Graph Template
3. Open the Shader Graph and create the “Texture 2D Asset” node
4. Right-click on the node → Convert to → Property
5. Add the Property by clicking the plus button on the left side of the Shader Graph window
Expected result: There are no errors after trying to convert the node to Property and the Properties can be added
Actual result: There are three errors in the Console after trying to convert the node and Properties can’t be added after that
Reproducible with: 2022.3.12f1, 2022.3.13f1, 2023.3.0a13
Not reproducible with: 2021.3.32f1, 2022.3.11f1, 2023.1.19f1, 2023.2.0b17
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Notes:
-After that, the Shader Graph remains broken even after the Unity restart
-This bug sometimes carries to the other Shader Graphs without converting the node there but usually newly created Shader Graphs work fine
-If you don’t try to convert the node, the Properties can be added without problems
-Reproducible with all the nodes that can be converted to Properties
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
Fixed by another internal issue: UUM-55342: Cannot convert value node to Property