Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X, 2019.1.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.1f1
2019.2.0a1
2019.3.0a1
Issue ID
1152137
Regression
No
Animation Curve on the Audio Source is copied with an offset when using GetCustomCurve and SetCustomCurve Methods
How to reproduce:
1. Open the "SampleScene" Scene in the attached "audio-curves.zip" Project
2. Enter Play Mode
3. Inspect Animation Curve on the "Original" GameObject
4. Compare it to the Animation Curve on the "New Game Object" GameObject
Expected Behavior: The Animation Curves are identical as they are copied
Actual Behavior: The Animation Curve on the "New Game Object" is Offset on the X Axis
Reproducible with: 2017.4.26f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0b1, 2019.3.0a2
Note: Copying the whole Component using EditorUtility.CopySerialized gives the expected behavior
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 (fix version 2019.2):
Fixed in: 2019.3.0a7
Backported to: 2019.2.0b7, 2019.1.9f1