Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.4.0b8
6000.5.0a6
6000.6.0a1
Issue ID
UUM-133857
Regression
No
[GTK] Performing Redo Create Node action can lead to Ghost Variable Node being created
Steps to reproduce:
- Open the attached project
- Open the RedoTest.texmkr graph asset
- Create a MeanColorNode
- Click and Drag the InTexture_1 Port
- Select the "Create Variable (of port type)" option
- Create a second MeanColorNode
- Connect the created texture variable to the second MeanColorNode
- Undo actions from steps 3 to 7
- Redo all of the actions
- Observe the nodes created by the Redo operation
Actual results: Variable Node is recreated as a ghost node that is not rendered on screen, but can be selected and retains previously connected wires
Expected results: Nodes created by the Redo operation are identical to the ones prior to the Undo action. No errors or warnings are thrown.
Reproducible with versions: 6000.4.0b8, 6000.5.0a6
Can’t test with versions: 6000.0.67f1, 6000.3.7f1 (Graph Toolkit not available as a built-in module)
Tested on (OS): Windows 11, macOS 26.2
Notes:
- The issue occurs when Redo performs "Create Variable (of port type)" -> "Create Node" actions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Assemblies” and “Areas” tabs disappears after switching to Scene tab and back in the Assemblies filter window
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
Add comment