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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
This is a duplicate of issue #1285638