Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.42f1
2021.3.14f1
2022.1.0a6
Issue ID
UUM-19868
Regression
No
Some actions after right-clicking on the ScriptableObject are unavailable when creating the SO a second time with AssetDatabase.CreateAsset()
Reproduction steps:
# Open the user’s attached project “CreateSO.zip”
# Create a new ScriptableObject by right-clicking and selecting “Create SO Buggy” inside the Assets folder in the Project window
# Right-click on the “BuggySO” ScriptableObject located in the Assets folder of the Project window
# Observe the available options
Expected result: All of the options that are supposed to be selectable are selectable
Actual result: Open, Delete, Rename and Reimport options are greyed out and the Icon of the ScriptableObject is missing
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.0a6
Not reproducible with: 2022.1.0a7, 2022.1.23f1, 2022.2.0b16, 2023.1.0a20
Reproducible on: Windows 10 (21H2)
Note: The issue goes away after entering any folder in the Project window and going back
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
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
- [Android] Crash on ProcessDynamicBatchGeometryJob with OpenGL or on DrawSharedGeometryJobs with Vulkan
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.