Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.1f1
Issue ID
1069362
Regression
No
[XR][UWP] Opening the TouchScreenKeyboard causes spatial sounds to stop taking Spatial Blend into account
Steps to reproduce:
1. Download 1069362_repro.zip
2. Change platform to UWP
3. Build "SampleScene" with XR enabled and app type set to XAML
4. Open VS solution and build to HoloLens
5. When the app launches on HoloLens test if spatial sound is working (audio source is on the right side)
6. Perform tap motion to open the keyboard
7. Enter and submit any text to return to the application.
8. Notice how the sound effect no longer sounds like it is coming from a fixed point in 3D space.
Expected results: Spatial sound works after re-entering app on HoloLens
Actual results: After re-entering app Spatial sound stop working. From left and right speakers sound volume is the same.
Reproducible on: .NET and IL2CPP backends
Reproduced with: 2018.3.0a10, 2018.2.5f1, 2018.1.9f1, 2017.4.9f1
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
- “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
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2018.3.X):
We are no longer fixing issues in 2018.3. If your issues still occurs in Unity 2018.4 or Unity 2019.3 and greater, please re-submit your bug for consideration.