Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.43f1
2021.3.16f1
2022.2.2f1
2023.1.0a23
Issue ID
UUM-27544
Regression
No
Graph Node stays selected when the Unselection entry in the Undo History pane is clicked
Reproduction steps:
1. Open the attached project “UndoProject”
2. Open “Assets/Scenes/OutdoorScene.unity” scene
3. Open “Assets/PlanetGraph.asset” to open the Planet Graph Editor
4. In the Planet Graph Editor right click on the mouse and select “Add Node/Perlin Noise”
5. Select the node (“Perlin Noise”) created
6. Click on the background (In Planet Graph Editor) to unselect the Perlin Noise
7. Open “Edit>Undo History” and Redo the Selection Change
Expected result: The Node is unselected
Actual result: The Node remains selected
Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a23, 2023.2.0a3
Reproducible on: Intel macOS 13.0.1
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 bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue, the number of users affected by it and it’s current experimental state. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.1.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue, the number of users affected by it and it’s current experimental state. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.