Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
5.6.2p1
Issue ID
932277
Regression
No
[Video Player] VideoPlayer.loopPointReached is being called 2 times when specific h264/VR Video Clip plays out
How to reproduce:
1. Open the attached "loopPointIssue" project and "Repro" scene
2. Inspect "player" GameObject, it has a Video Player Component with a "Repro" Video Clip attached. Observe that its Loop setting is unchecked
3. Open the Console window and enter playmode
Expected result - Video plays out, VideoPlayer.loopPointReached is being called only 1 time
Actual result - Video plays out, VideoPlayer.loopPointReached is being called 2 times
Reproducible with - 2017.3.0a7, 2017.2.0b10, 2017.1.0p5, 5.6.1p4
Reproducible on:
Windows 10 Pro, AMD FX(tm)-8350 (8 core) 4.00 GHz, AMD Radeon (TM) R7 360
Reproducible only on first play:
macOS Sierra, Intel Core i7 2.3Ghz, NVIDIA GeForce GT 750M 2048 Mb
Windows 10 Pro 64-bit, Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz 3.40GHz, NVIDIA GeForce GTX 760
Does not reproduce at all:
Windows 10, Intel Core i7--4820K @ 3.7 GHz, Nvidia GeForce GTX 780
Note: Issue does not seem to reproduce if Loop setting is enabled
Fixed in - 2017.3.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment