Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133792
Regression
No
Renaming Node class name turn existing node into “Missing Node” instead of updating the name
Steps to reproduce:
1. Create new Unity project
2. Import provided script “AdvancedGraph.cs”
3. In the Project window, right-click -> Create -> Graph Toolkit Samples -> Advanced Test Graph -> Open the Graph
4. Press space in Canvas and create “TestNode” Node
5. Open “AdvancedGraph.cs” script
6. Change class name “TestNode” to “TestNodeNode”
7. Wait for the script to compile
8. Observe Node in Graph Canvas
\\
Actual results: Node name changes to “Missing Node” instead of updating Node name to “TestNodeNode” in Canvas after script changes
Expected results: Node name should update/change accordingly after script changes
\\
Reproducible with versions: 6000.4.0b7, 6000.5.0a6
\\
Tested on (OS): Ubuntu 24.04, macOS Silicon Tahoe 26.2 (M1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.