Search Issue Tracker
Fixed
Fixed in 6000.3.11f1, 6000.4.0b11, 6000.5.0a8, 6000.6.0a1
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134112
Regression
No
Shader Graph Swizzle node data updates incorrectly after undo action
Steps to reproduce:
- Open a new shader graph
- Setup a simple graph (world position -> swizzle node -> output node 'color')
- Set swizzle node input mask to 'xyz'. Can visibly see the mask input change to vec3
- Set swizzle node input mask to 'xy'. Can visibly see the mask input change to vec2
- Undo (crtl/cmd+z). Can see everything move back from vec2 to vec3
- Click on the input mask field
- Click off input mask field.
Actual results: Input mask stays the same but notice the actual visual output changes, and appears to become a float perhaps?
Expected results: The mask and visual output remain consistent as vec2, the result of the undo operation.
Reproducible with versions: 6000.5.0a7, 6000.3.5f1
Tested on (OS): MacOSX Tahoe (MacEditor ARM M1 Max)
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.4.0b11):
Fixed in 6000.4.0b11
Resolution Note (fix version 6000.3.11f1):
Fixed in 6000.3.11f1