Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.35f1
2022.3.20f1
2023.2.11f1
2023.3.0b8
6000.0.0b11
Issue ID
UUM-64805
Regression
No
Audio Reverb Zone Component is not applied when Effects are reordered in the Mixer
Reproduction steps:
1. Open the attached “AudioReverZoneBug.zip” project
2. Enter the Play mode and listen to the audio
3. Exit the Play mode
4. Open the “Mixer” asset from the Project Window
5. Click on the “Parent” Group Controller
6. Reorder the “Send” Effect so that it is placed above the “Attenuation” Effect
7. Enter the Play mode and listen to the audio
Expected result: The Reverb Effect is still heard after reordering the Effects
Actual result: Reordering the Effects disables the Reverb Effect
Reproducible with: 2021.3.35f1, 2022.1.0a2
Not reproducible with: 2022.3.20f1, 2023.2.9f1, 2023.3.0b7
Fixed in: 2022.1.0a3
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Moving the “Send” Effect back to the bottom doesn't fix the issue, the Effect needs to be removed and added back
-
man572142
Apr 01, 2024 03:13
I want to share more things that I found recently around this issue.
1. It seems not only to occur after reordering the effect but many other changes to the AudioMixer as well, such as adding a new effect in any AudioMixerGroup and adding a new child AudioMixerGroup.
2. The "Remove effect and add back" workaround does not work after we relaunch the editor, even if we save the AudioMixer.
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
- “Readme” Asset is unreadable in the Inspector window when switching Editor Theme to Light
- “NullReferenceException” error thrown when switching Editor Theme to Light if “Unity Version Control” tab is enabled
- A Warning is displayed in the Inspector when a Mesh with any Material is added as a Terrain Detail
- [Android][Vulkan] Memory leak when playing and stopping a video using the Video Player on some devices
- Caret moves by a character when typing "." and any number into 'Grid and Snap' toolbar's input field
Resolution Note:
There are no fixes planned for this Bug