Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
901973
Regression
Yes
Screen tearing and jittering issues in the game view
Steps to reproduce:
1. Open attached project ("StutterTest")
2. Open "main" scene
3. Play the scene
4. Observe the screen tearing
Expected result: there should be no screen tearing and jittering when the cube is moved
Actual result: the cube is jittering when moving and screen tearing is highly noticeable
Reproduced in: 2017.1.0b3, 2017.1.0b1, 5.6.0p4, 5.6.0a6, 5.6.0a5, 5.6.0a3
Not reproduced in: 5.6.0a2, 5.6.0a1, 5.5.3f1, 5.5.0f3, 5.4.5p1
Regression since: 5.6.0a3
Reproduced using macOS Sierra 10.12.3
Fixed in: 2017.1.0b8
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
flashframe
May 20, 2017 17:55
I'm seeing this bug in 5.6.1f1. IT says "Fixed in future release", which release will that be? I can't see it listed in the latest patch released 2 days ago either. Thanks