Search Issue Tracker
Active
Votes
11
Found in
2021.3.25f1
2022.2.19f1
2023.1.0b16
Issue ID
UUM-35595
Regression
No
AsyncGPUReadback.RequestIntoNativeArray displays incorrect frame count in WebGL Player when using Chrome or Edge browsers
How to reproduce:
1. Open the “Frame_Count_Bug” project
2. Switch build to “WebGL” (File > Build Settings > “WebGL” > Switch Platform)
3. Build And Run (File > Build And Run)
4. Click on the Button labeled “Render”
5. Observe the label “Frame Count”
Expected result: frame count is around 2-4
Actual result: frame count is around 201-203
Reproduced with: 2021.3.25f1, 2022.2.19f1, 2023.1.0b16
Could not test with: 2020.3.48f1 (Functionality is broken → frame count is constantly displaying “0”), 2023.2.0a14 (Player does not fully load)
Browser reproduced on: Chrome, Edge
Browser not reproduced on: Firefox
Reproduced on: Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Dynamic lights still show up in the Profiler consuming time when "Main Light" and "Additional Lights" are disabled in the UniversalRP-HighQuality asset
- Sprite Asset changes are unsaved after updating sprite atlas
- Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
Add comment