Rolling shutter issue on MacOS since 1.14.3 Pre-Release 2

Can confirm. Although it's impossible to take a screenshot of this graphical glitch for some reason, the video displayed the exact issue I had. I also had this happen higher up on my screen a few days ago as well as having it recently lower on my screen.

I'm not sure sure that's screen tearing. That's usually defined as a frame rate inconsistent with the display, causing partial updates. It's also usually only noticed with horizontal movement, not vertical. This to me looks more like incorrect mipmapping, at least the distance in which it is applied. Out of curiosity, if you reduce/disable mipmapping, does this go away?

How would one "reduce/disable mipmapping". I have never seen this setting before.

To reduce/disable mipmapping, go to "video settings" which is found in "options" and you will find a bar that has 4 levels with the maximum being default. By the way, when I removed mipmapping, the glitch still happened (this was only tested for the MacBook Pro I have acess to).

I have the same problem Macbook Pro 2016. Turning off mip-mapping has no effect.

I have the same issue, but it appears in upper part of the screen instead of lower part.

macOS 10.14.5

MacBook Pro 2012

Can confirm that this is happening to me too. MacBook Pro user.

can confirm MacBook Pro 2017, MacOS Mojave (10.14.5)

Also having this issue, MacBook Pro 2017, macOS 10.15 Catalina (beta 2)

No problems on <=1.14.2

Same thing is happening to me as well. I get both the top of the screen, and right above the health/hunger bar. iMac 2017, macOS High Sierra (10.13.6) user

Same here. MacBook Pro 2013 with Mojave 10.14. Really annoying. Took a video example here: https://www.youtube.com/watch?v=WgnwDktPI3U

Also reported in MC155120. Turning VSync off helped some folks, but not everyone.

I can confirm this issue on 2017 iMac 4K with macOS Catalina developer beta 2. Tears with Vsync on or off.

Minecraft Crash Report -------- Minecraft Crash Report ----// Quite honestly, I wouldn't worry myself about that.
Time: 30/06/19 9:52 AMDescription: Manually triggered debug crash
java.lang.Throwable at cvm.b(SourceFile:530) at cvo.m(SourceFile:1477) at cvo.e(SourceFile:925) at cvo.b(SourceFile:411) at net.minecraft.client.main.Main.main(SourceFile:154)

A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
– Head --Thread: Client threadStacktrace: at cvm.b(SourceFile:530)
– Affected level --Details: All players: 10 total; [dkb['JaydenIrwin'/625841, l='MpServer', x=14.53, y=63.00, z=0.44], dkc['zkcneg2x42'/380, l='MpServer', x=24.50, y=64.00, z=10.50], dkc['ya15j2xpa2'/66, l='MpServer', x=26.50, y=64.00, z=4.50], dkc['2tt87p8e10'/67, l='MpServer', x=25.50, y=64.00, z=7.50], dkc['eod2b3uv5b'/372, l='MpServer', x=9.50, y=63.00, z=-5.50], dkc['crt0ea84ix'/61, l='MpServer', x=22.50, y=63.00, z=-15.50], dkc['9j6w478o9z'/63, l='MpServer', x=24.50, y=64.00, z=-9.50], dkc['8d99s7b893'/64, l='MpServer', x=25.50, y=64.00, z=-6.50], dkc['6b1109plkm'/65, l='MpServer', x=26.50, y=64.00, z=-3.50], dkc['f688w8f66t'/376, l='MpServer', x=34.50, y=64.00, z=-19.50]] Chunk stats: Client Chunk Cache: 5041, 169 Level dimension: minecraft:overworld Level name: MpServer Level seed: 0 Level generator: ID 01 - flat, ver 0. Features enabled: false Level generator options: {} Level spawn location: World: (-1,65,-1), Chunk: (at 15,4,15 in -1,-1; contains blocks -16,0,-16 to -1,255,-1), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1) Level time: 457080736 game time, 981 day time Level storage version: 0x00000 - Unknown? Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false) Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false Server brand: vanilla Server type: Non-integrated multiplayer serverStacktrace: at dhr.a(SourceFile:421) at cvo.b(SourceFile:1923) at cvo.b(SourceFile:426) at net.minecraft.client.main.Main.main(SourceFile:154)
– System Details --Details: Minecraft Version: 1.14.3 Operating System: Mac OS X (x86_64) version 10.15 Java Version: 1.8.0_74, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 858285696 bytes (818 MB) / 1845493760 bytes (1760 MB) up to 2147483648 bytes (2048 MB) JVM Flags: 7 total; -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Launched Version: 1.14.3 LWJGL: 3.2.2 build 10 OpenGL: AMD Radeon Pro 560 OpenGL Engine GL version 2.1 ATI-3.0.47, ATI Technologies Inc. GL Caps: Using GL 1.3 multitexturing.Using GL 1.3 texture combiners.Using framebuffer objects because ARB_framebuffer_object is supported and separate blending is supported.Shaders are available because OpenGL 2.1 is supported.VBOs are available because OpenGL 1.5 is supported.
Using VBOs: Yes Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: vanilla, file/Fluid Current Language: English (US) CPU: 4x Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz

I have the same issue of a rolling shutter that occurs on the bottom directly above the hunger bar across the whole screen vertically, and then across the top randomly. I'm on a 2018 MacBook Pro 2015 on the latest version of MacOS. Issue occurs no matter what resolution of fullscreen and when fullscreen is disabled. Vsync slightly diminishes the issue, but does not resolve it. 1.14.3 is the only version this issue has occurred in for me.

Even happens on my Acer Aspire E1...

(yes it's running macOS)

1.14.4-pre5  Confirmed

This issue still occurs on my 2017 iMac Pro w/Vega 64 running 10.14.5 (18F132) on both the latest release 1.14.3 and 1.14.4-pre5 

...pretty unplayable

I agree with Peter.

At first I thought "Oh man this is annoying"

But after playing more and more it seems to affect more than the rolling shutter. It almost seems like some frames are behind, borderline lagging. 

yep. I can not play the new version of the game, "pretty unplayable". returned to 1.14.2.
Mojang, please fix

" ...pretty unplayable"

Yeah... Lately I don't play Minecraft because of this issue. Waiting for the next release and hoping it will be fixed.

Just tried out 1.14.4 Pre-release 6 and the screen tearing/stutter is still there for me.

macOS Mojave 10.14.5
Mid 2017 27" iMac.

It is also still present on my machine.

macOS Mojave 10.14.5
Early 2015 13" MacBook Air.

This issue is now present in the 1.15 pre-releases, please re-open. I'm not quite sure how to record an image of this happening on my machine, but it certainly is.

@unknown, please create a new report for this.