Search Issue Tracker
Fixed in 2019.1.X
Votes
7
Found in
2018.2.0a7
Issue ID
1024877
Regression
No
Video player doesn't show anything on Scriptable Render Pipeline
To reproduce:
1. Open the project, attached by the user (Bug_VPlayer_HD.zip)
2. Open the "SampleScene"
3. Enter Play mode
4. Observe that video is not showing up on the plane, but the sound from the video is playing
Expected: video player works as it should on any SRP mode
Reproduced in 2018.1.0f1, 2018.2.0a7, 2018.2.0a8
Could not test in 2017.3 and earlier due to many errors in the console
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
- [Enlighten] Worker thread related message is printed in the log regardless of realtime GI being enabled or not
- [Hub][Linux] Hub .AppImage does not allow to upgrade the Hub from 2.4.5 to 3.0.0-beta.2
- [Profiler] Current frame button initially hides profile frame marker
- [Linux][Hub] Unity Hub 2.4.5 does not open "Add modules" window when clicking "Install with Unity Hub" in Build Settings
- Broken link in HDRP manual
warpedpipe
Jun 21, 2019 16:47
Still an issue in 2019.3.0a6. If you change the material property to _BaseColorMap then it will play the video.
GalaTyler
Jun 19, 2019 20:36
If you're still having problems with this (as I was on LWRP) then make sure that the "Material Property" on the Video Player component is set to "_BaseMap". By default it renders into "_MainTex", which isn't used on LWRP materials.
codespark-james
Jan 24, 2019 01:00
We are seeing the same thing on 2018.3.1f1.
codespark-james
Jan 24, 2019 00:59
We are seeing the same thing on 2018.3.1f1.
codespark-james
Jan 24, 2019 00:58
We are seeing the same thing on 2018.3.1f1.
RoutineAyhan
Sep 14, 2018 11:52
The videoplayer does work when rendering to a rendertexture.
It does not work with rendering to camera near & far planes. As for the other options, i did not try them yet.
RoutineAyhan
Sep 14, 2018 11:28
Exists in 2018.2.7f1..
Dipity
Aug 08, 2018 14:23
Problem still exists in 2018.2.2f1.