Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.2.0b1
Issue ID
925546
Regression
No
[OpenGL][AntiAliasing] Video doesn't play, scene renders some random place in editor and spams error
How to reproduce:
1. Open the attached project
2. Open and Play Render Texture scene
3. Click on next video (>|) button twice
4. Click on play (>) button
Result: Notice that it glitches and spams this error
Assertion failed: Assertion failed on expression: 'srcAttach < m_CurrentFramebuffer.colorCount && "We should always resolve only current RT"'
NOTE: Issue occurs only on OpenGL and when texture (video_1_mat in this project) uses Anti Aliasing
Reproducible: 5.6.2f1 , 2017.1.0f2, 2017.2.0b1
Videos (reproducible):
Groot_H264_AAC_1280x720.mp4, 1280x720,H264 avc, Baseline@L3.1, 30, 2137 kb/s,AAC/LC,2,192 kb/s,44.1kHz
Groot_VP8_Vorbis_1280x720.webm,1280x720,VP8,30,1941 kb/s,Vorbis,2,112 kb/s,44.1kHz
Fixed: 2017.2.2p4 <- maybe in earlier version
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment