Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.16f1
Issue ID
UUM-22533
Regression
No
[LEGO Microgame] AudioSampleProvider buffer overflow Warnings thrown when starting Elevator Tutorial
How to reproduce:
1. Create "LEGO Microgame" project
2. Load Tutorials
3. Start the "Activate the elevator" Tutorial
4. Observe Console
Reproducible with: 4.0.0 (2021.3.16f1)
Not reproducible with: 2.4.2 (2020.3.36f1)
Could not test with: 2022.2.2f1, 2023.1.0a25 (LEGO Microgame not available)
Warnings:
AudioSampleProvider buffer overflow. 1024 sample frames discarded.
AudioSampleProvider buffer overflow. 2048 sample frames discarded.
AudioSampleProvider buffer overflow. 128 sample frames discarded.
Tested on: Windows 11
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
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2021.3.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.