Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133962
Regression
No
Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
How to reproduce:
1. Create a new Unity project
2. In the Project window, right-click -> Create -> Shader Graph -> URP -> Unlit Shader Graph
3. Go to Edit -> Preferences -> Shader Graph -> Enable Deprecated Nodes
4. In the Graph Toolkit, Blackboard -> + and observe the dropdown
5. Add any Property
6. Click the "+" button again and observe the dropdown
Expected results: The legacy options (e.g. "Color (Legacy v0)") are available both times
Actual results: The legacy options (e.g. "Color (Legacy v0)") are available only when opening the dropdown for the second time
Reproducible with: 6000.0.67f1, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thanks for reporting this issue.
We suspect this won't impact users in any practical way. We are currently investigating a more holistic solution for handling deprecation, obsolescence, and versioning of nodes.
We do not intend to address this issue directly, but instead as part of a more comprehensive review.
Thanks.
Resolution Note (6000.5.X):
Thanks for reporting this issue.
We suspect this won't impact users in any practical way. We are currently investigating a more holistic solution for handling deprecation, obsolescence, and versioning of nodes.
We do not intend to address this issue directly, but instead as part of a more comprehensive review.
Thanks.