Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
2
Found in
2019.1.0a13
2020.1.9f1
2021.1
Issue ID
1285638
Regression
Yes
[Audio Mixer] Unable to expose other "Send Level" parameters when one is already exposed
How to reproduce:
1. Open users attached project
2. In Audio Mixer, change "Canard1" send level to "Unexposed"
3. Change "Canard2" send level to "Exposed"
4. Try to change "Canard1" send level to exposed again
Expected result: "Canard1" send level changes to "Exposed"
Actual result: "Canard1" send level is not possible to change to "Exposed", only to "Unexposed"
Reproducible with: 2019.1.0a13, 2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5
Not reproducible with: 2018.4.29f1, 2019.1.0a12
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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a10
Moved send data from group (i.e. "singleton") controller to effect controller. This also allows multiple sends on a group.
Resolution Note (fix version 2021.2):
Fixed in 2021.2.1f1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.26f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.21f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.32f1