Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in [Package]
Issue ID
1218554
Regression
No
[Shadergraph] Changing Alpha Clip Threshold from 0 does not update graph until graph is changed
Reproduces on master (bcdb37f295) and Universal RP 7.1.7
Repro steps:
1. Use Universal RP or HDRP as your pipeline
2. Create a PBR graph
3. Set the Alpha Clip Threshold to 0
4. Drag out an edge from Alpha to create a Gradient Noise node
5. Change the Alpha Clip Threshold to 0.5
Expected result: the preview updates with the new change
Actual result: the shader has no alpha clipping in the preview. Saving the shadergraph and making a material will have no alpha clipping. The only way to get the change to alpha clipping to update is to change the graph structure by connecting or disconnecting an edge.
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
There will be changes to resolve this issue in 20.2.