Search Issue Tracker
Fixed
Fixed in 2021.3.34f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a14, 7000.0.0a1
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52266
Regression
Yes
[WebGL]VideoPlayer Rendering stops when setting FilterMode of a texture downloaded with UnityWebRequestTexture.GetTexture()
How to reproduce:
1. Open the attached Project "webgl-video-atlas" and load Scene "SampleScene"
2. Build and Run the Project on WebGL
3. In the Player, Click the "Stream Video" Button
4. Observe the Player
Expected result: Textures appear to the right of the VideoPlayer and the VideoPlayer continues showing the video
Actual result: Textures appear and the VideoPlayer becomes black
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0a19, 2023.2.0b12, 2023.3.0a8
Not reproducible with: 2023.2.0a18
Reproduced on:
* Google Chrome 116.0.5845.187
* Safari 16.6 (18615.3.12.11.2)
* Mozilla Firefox 118.0.1
Did not reproduce on:
* MacOS Editor
* MacOS Player
Notes:
* The Audio of the Video continues playing and the frame counter keeps going up even with the VideoPlayer showing a black screen
* Firefox throws the following Warning into its Console:
"WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 0 is incomplete: Bad mipmap dimension or format."
* The issue might not reproduce immediately on Firefox and might take a few tries
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2023.3.0a14):
The WebGL backend for the VideoPlayer was manipulating the graphics state directly from javascript without keeping the internal state cache (containing bindings) up to date. Now the internal state cache is correctly invalidated after the backend has updated the current frame from javascript.