Search Issue Tracker
Duplicate
Votes
0
Found in
2021.1.8f1
2021.2.0a16
Issue ID
1337570
Regression
Yes
Certain workflows with exposed send level in audio mixer causes an assertion
How to reproduce:
1. Create a new Unity project
2. Create an AudioMixer asset and open it in AudioMixer window
3. Add 2 new child groups of the Master group
4. Add a 'Send' effect to group A and a 'Receive' effect to group B
5. Select group A and set its 'Receive' target to group B
6. Right-click the 'Send Level' label and expose this parameter
Then one of the following:
7a. Delete the send effect on group A
7b. Delete the receive effect on group B
7c. Delete group B
Expected result: no errors are thrown, Exposed Parameters drop-down works
Actual result: an assertion failed error is thrown, Exposed Parameters drop-down no longer works and throws a NullReferenceException
Note: There could be other workflows involving exposed send levels that also lead to this assertion.
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
This is a duplicate of issue #1285638