Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
1
Found in
2020.3.35f1
2021.3.3f1
2022.1.3f1
2022.2.0a13
Issue ID
UUM-663
Regression
No
Editor crashes when selecting a referenced ScriptableObject asset containing AnimationCurves from the scene
Reproduction steps:
1. Open linked Project
2. Open Assets\\Scenes\\bug Scene
3. Select PROBLEM_OBJECT in the Hierarchy
4. Expand Game Mode in the Inspector
5. Select the Object in the Modifier field
Expected result: The Object is selected
Actual result: The Editor crashes
Reproducible with: 2019.4.24f1, 2020.3.5f1, 2021.1.5f1, 2021.2.0a15
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.
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.
Resolution Note (2022.2.X):
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.