Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
1
Found in
2019.3.0a9
2019.3.7f1
2020.1
2020.2
Issue ID
1232889
Regression
Yes
Video stuttering when large screen target resolution is set and Vsync is disabled
How to reproduce:
1. Open the project from the attached file "1232889.zip"(link in edit)
2. Open the MinimalRepro scene and enter Play Mode
3. In the Game View make sure that the resolution is set to 8192x8192 and Vsync is disabled
4. Inspect the Game View
Expected behavior: Video is played smoothly
Actual behavior: Video is stuttering
Reproducible with: 2019.3.0a9, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Not reproducible with: 2017.4.39f1, 2018.4.21f1, 2019.3.0a8
Notes:
- Reproducible with DX11, DX12, OpenGL Graphics API
- "Large screen target resolution" would be referring to approximetily 8192x8192
- If the suttering is not reproducing try to wait a bit(~20sec) or re-enter playmode a few times
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
Resolution Note (fix version 2020.2):
Under heavier graphics load, the render thread can become late relative to the game loop. Take this extra delay into account before releasing video texture to avoid them being recycled for decoding too early (leading to visual back-and-forth artifacts).
Fixed in 2020.2.0a9
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b8
Resolution Note (fix version 2019.3):
Fixed in 2019.3.12f1