Search Issue Tracker
Fixed in 8.0.0
Votes
0
Found in [Package]
7.0.1
Issue ID
1186225
Regression
Yes
[ShaderGraph] Cannot redo undone actions when certain nodes are added to a graph
After adding certain nodes to a shader graph, you cannot redo any actions you make afterwards unless it is a 'Change GraphView Selection' action.
Appears to occur with nodes that have a preview square, such as 'Invert Colours', 'Channel Mixer', 'Sample Texture 2D' etc.
Is not affected by nodes that have no preview square in the node, such as logic (i.e. 'Is NaN', 'Is Infinite') or property values.
1. Create a new project.
2. Install Shader Graph package through package manager. (Window -> Package Manager)
3. Create a new shader graph. (i.e. Assets -> Create -> Shader -> Unlit Graph)
4. Open the shader graph.
5. Create a new node in the graph. (i.e. Right Click -> Create Node -> search for 'Channel Mixer')
6. Move this new node to a different position in the graph.
7. Undo change. (Edit -> Undo Move Elements)
8. Redo the change.
Expected Outcome: The undone change is redone.
Actual Outcome: Nothing happens. The 'Redo' option in the Edit menu is greyed out.
Reproducible in Package Version 7.0.1, 7.1.1
No issue in package 5.2.3 or 6.9.1
Notes:
- You can still undo all actions without any noted issue.
- You can redo any 'Change GraphView Selection' action after editing a node.
- GIF attached to case showing this issue occuring while editing values on a blackboard property.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment