Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2020.1
2020.1.0a14
Issue ID
1202437
Regression
No
AudioSource curve's last Keyframe position is set to maxDistance and the entire curve is streched when set through script
Steps to reproduce:
1. Open the attached project (case-1202437_LowPassFilterCurves.zip)
2. Select "Audio Source" in the Hierarchy
3. Scroll down in the Inspector and take note of the "Reverb Zone Mix" and "Low-Pass" curves
4. Enter Play Mode
5. Observe the change in the curves
6. Use Spacebar to move the last keyframe of each curve in negative X and negative Y direction
Expected result: Both of the curves overlap at Distance = 375 and continue to do so as the last keyframe is moved by repeatedly pressing Spacebar
Actual result: Low-Pass filter's curve's last Keyframe's time parameter is completely ignored and set to 1.0, which causes the entire curve to scale accordingly
Reproduced in: 2017.4.35f1, 2018.4.14f1, 2019.2.16f1 (Low-Pass only), 2019.3.0f2 (Low-Pass only), 2020.1.0a16 (Low-Pass only)
Note: In Unity 2017.4.35f1, 2018.4.14f1, the same behavior is observed for all built-in AudioSource distance function curves (Volume, Spatial Blend, etc.) along with the Low-Pass curve.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in 2019.3.6f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.31f1