Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X
Votes
0
Found in
6000.3.11f1
Issue ID
UUM-136710
Regression
No
Can not delete a GTK Context Node when it is duplicated with one or more Blocks
How to reproduce:
1. Extract and open the attached “IN-136013.zip“ project
2. Double-click the “Assets/Data/Items/Weapons/PhoenixFeather/PhoenixFeather_Behavior_Active.ibg“ asset
3. Right-click in the opened “PhoenixFeather_Behavior_Active“ window
4. Select “Add Node“
5. Add the “LevelingContextNode“
6. In the “LevelingContextNode“ click “Add a Block“
7. Add the LevelMilestone Block
8. Right-click the “LevelingContextNode“
9. Click on “Duplicate”
10. Right-click the duplicated “LevelingContextNode“
11. Click on “Delete“
12. Observe the Console and the “PhoenixFeather_Behavior_Active“ window
Actual result: It is not possible to delete the Context Node, and a “NullReferenceException: Object reference not set to an instance of an object“ error message appears
Expected result: The Context Node gets deleted, and no error messages appear
Reproducible with: 0.1.0-exp.1, 0.4.0-exp.2 (6000.3.11f1)
Could not test with: Could not get the asset to load in different Editor versions
Reproducible on: Windows 11
Could not reproduce on: No other environment tested
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 taking the time to report this issue!
This is a bug in the experimental package. Graph toolkit has become a module in 6.4, and since then, this bug has been fixed. We no longer support the package version.
Resolution Note (6000.3.X):
Thank you for taking the time to report this issue!
This is a bug in the experimental package. Graph toolkit has become a module in 6.4, and since then, this bug has been fixed. We no longer support the package version.