Search Issue Tracker
Won't Fix
Votes
3
Found in
2021.3.29f1
2022.3.7f1
2023.1.9f1
2023.2.0b4
Issue ID
UUM-46128
Regression
Yes
Spatial audio (3D Sound Settings) from a Video Player does not change direction from where the sound is played when in WebGL Player
Reproduction steps:
1. Open the “SpatialBlendStripped” project
2. Open the “Sample” scene
3. Ensure the selected platform in Build Settings is WebGL
4. Build And Run
5. The audio source relative to the camera
Expected result: The audio source is spatialized relatively to the camera
Actual result: The audio source is affected by distance but not by direction
Reproduced in: 2021.2.3f1, 2021.3.29f1, 2022.3.7f1, 2023.1.9f1, 2023.2.0b4
Reproduced on: macOS 13.4.1 (Intel), Windows 11
Not reproduced on: No other environment tested
Notes:
1. Not reproduced in Play Mode and StandalonOSX
2. Related forum thread: https://forum.unity.com/threads/webgl-spatial-audio-for-videoplayer.947112/
3. Similar fixed bug: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-1165
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
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
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.