Search Issue Tracker
Fixed
Fixed in 6000.6.0a7
In Progress in 6000.3.X, 6000.5.X
Won't Fix in 6000.4.X
Votes
0
Found in
6000.3.13f1
6000.4.2f1
6000.5.0b3
6000.6.0a3
Issue ID
UUM-141418
Regression
No
[Web] VideoPlayer.frameReady event fires only once in a video when the Player Graphics API is set to WebGPU
How to reproduce:
1. Open the attached “IN-140834“ project
2. Build and Run the Player
3. Focus the Player tab in the browser
4. Observe the “frameReady count” value at the top left corner of the Player
Actual result: The frameReady count value is equal to 1 and does not increase
Expected result: The frameReady count value constantly increases
Reproducible with: 6000.3.0a1 (4592b02ab560), 6000.3.14f1, 6000.4.5f1, 6000.5.0b6, 6000.6.0a4
Not reproducible with: 2023.1.0a1, 6000.0.74f1, 6000.2.0b2 (2bdac9ac0d74)
Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environments tested
Notes:
- Issue reproduces on Firefox, Edge, Chrome browsers
- Issue does not reproduce when the Graphics API is set to WebGL 2
- Issue does not reproduce on the Windows Platform with Graphics API Direct3D12
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note:
Fixed in 6000.6.0a7
Resolution Note (fix version 6000.6.0a7):
Fixed in 6000.6.0a7
Resolution Note (6000.4.X):
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.