Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.15
Issue ID
ADDR-3493
Regression
No
Audio Mixer volume doesn't change when trying to change volume with a Slider component in a Player Scene that is loaded with Addressables
Reproduction steps:
1. Open the attached “PROJECTFILE” project
2. Build And Run the project (File > Build And Run)
3. In the Player, press the Q keyboard key and move the “UISlider” Slider component
4. Listen to the audio
Expected result: Volume changes to the moved slider accordingly
Actual result: Volume does not change
Reproducible with: 1.19.19, 1.20.5, 1.21.15 (2021.3.29f1, 2022.3.7f1, 2023.1.9f1, 2023.2.0b5)
Reproducible on: macOS 13.4.1 (M1 Max), Windows 10
Not reproducible on: No other environment tested
Note: The Audio Mixer volume changes when using Snapshots. No reproduction if the scene is loaded without Addressables.
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
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.