Search Issue Tracker
Fixed in 2018.3.X
Votes
8
Found in
2017.2.0p3
Issue ID
984235
Regression
Yes
[WebGL] [VideoPlayer] When a movie is played the second and subsequent times, the screen doesn't render
To reproduce:
1) Open attached project
2) Build and run on WebGL
3) Play the movie - notice it runs normally in each loop
4) Stop it and restart
When a movie is played the second and subsequent times, the screen is black (but the sound plays).
Reproduced in 2017.1.2p1, 2017.1.2p2, 2017.1.3f1, 2017.2.0p3, 2018.1.0b1
Not reproduced in 2017.1.2f1.
Browsers reproduced in - Firefox 57.0.2 (64-bit), Chrome Version 63.0.3239.108 (Official Build) (64-bit)
Comments (60)
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
kwcae
Jul 19, 2018 22:10
Same or at least similar issue in 2018.2.0b2 but only under Edge 40
r8-Bit-Ape
Jun 12, 2018 22:15
Also seeing this in 2017.3.1p4. Has anybody got a work around?
FireHawkX
May 03, 2018 17:52
I tested both
Unity 2018.1.0f2 (64-bit)
and
Unity 2018.2.0b2 (64-bit)
and got the same bug... although the "1st play" didnt work either in those 2 version, it simply showed the first frame, subsequent play had only audio and no visuals at all...
FireHawkX
May 01, 2018 00:29
I updated my whole project to Unity 2017.4.1f1 (64-bit) last week and got this bug... this really needs to be fixed as my whole game depends on the video player working properly! Please? :)
Note that the bug was not present in Unity 5.6.3p2 (64-bit) but I'd like to avoid rolling back then project to an earlier version...
realworld666
Mar 19, 2018 10:06
We're seeing this issue on Unity 2017.3f2 and 2017.3.1p3