Search Issue Tracker
Won't Fix
Votes
0
Found in
4.5.0a5
Issue ID
587715
Regression
No
AnimationCurve.MoveKey creates new keys when the animation has a position property
To reproduce:
1. Open attached project
2. Open "scene"
3. Open animation window and select the main camera. "Anim" should be the current animation
4. Open Custom > Open
5. In the custom editor window change the Length - instead of moving the keyframes, the script creates new ones. This does not occur for the 2nd clip (FOV), which does not have the position property
Extra bug: the animation window does not fully update after the length has been changed (only the length gets updated). You need to navigate to Curves and then back to the dopesheet - this shouldn't be necessary
Explanation: The problem here is that not EditorCurves were used. (AnimationUtility.GetAllCurves(...) is deprecated)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment