Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.4.0b8
6000.5.0a6
Issue ID
UUM-134168
Regression
No
[GTK] Performing Undo after a Node was created as part of a Wire connection action results in an invisible Wire
Steps to reproduce:
- Open the attached project
- Open the Test.texmkr graph asset
- Left-Click and Hold on the Wire connected to the OutTexture port of one of the UniformNode
- Drag the wire to disconnect it from the node
- Release the wire and select Texture 2D Constant from the Node Library pop-up
- Observe that the Wire was connected to the newly created constant Node
- Undo the action
- Observe the OutTexture port
Actual results: OutTexture port shows it is connected with a Wire, despite no Wire being present on screen. Creating a box selection window around the area where the Wire should be results in a Wire being picked up by the Inspector - showcasing that the connection exists, but isn't rendered
Expected results: After the Undo action is performed, the connecting Wire is restored to a state prior to Step 3
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
Add comment