Ever since I updated to 1.14.3, I have noticed screen tearing only near the bottom of my screen. It happens most when I am sprinting. It's very annoying because if I turn VSync off, the screen tearing stops, but the input lag and occasional drop in frame rate is unbearable for me. With VSync turned on, the screen tearing is unbearable for me (but there is no input lag, nor drops in frame rate).
If we could solve this issue, I would be so happy. What additional information do you need from me?
Please see all the details I have gathered for you (files are attached). I attached the following files:
My Mac computer specs
My Minecraft video settings
A video showing the issue https://photos.app.goo.gl/eytuHpJ2ir45om7o6 (recorded on my phone). It's hard to see the issue on captured video, you must see it in person to experience the full extent.
There's a report on the bug tracker that confirms this as being an issue in 1.14.3 on MacOS, with no known fix provided (it appears to be a bug within LWJGL itself):
However, in a related report somebody mentioned that the location of the tear appears to be fixed relative to the screen, not the game window, so by moving the window you can can move it out of it (unless you play on fullscreen).
The issue occurs on both my internal iMac display, as well as my external thunderbolt display.
From the sounds of it, it's strictly a 1.14.3 issue, and I am not the only one who experiences the issue. I suppose I just have to wait for the next update to see a fix.
@TheMasterCaver thanks for providing the bug report. I will comment on it notifying them that this happens to me too.
Is there anything else I can do to help bring more awareness to this issue so that I am more likely to see a fix in a near future version? Lol
Ever since I updated to 1.14.3, I have noticed screen tearing only near the bottom of my screen. It happens most when I am sprinting. It's very annoying because if I turn VSync off, the screen tearing stops, but the input lag and occasional drop in frame rate is unbearable for me. With VSync turned on, the screen tearing is unbearable for me (but there is no input lag, nor drops in frame rate).
If we could solve this issue, I would be so happy. What additional information do you need from me?
Please see all the details I have gathered for you (files are attached). I attached the following files:
Per this Forum section's rules, I can bump a thread every 12 hours. Hoping for help! *fingers crossed*
I have same issue with Minecraft 1.14.3 on macOS Mojave.
However, in my environment, it is not the issue for 1.14.2. It seem to be the bug caused by 1.14.3.
So, I think what we can do is only waiting the update.
Interesting. I don't have this issue in 1.14.3 on my MacBook Pro.
1.14.3 further updated LWJGL, so that might be the issue.
Does it happen on both in internal and external display?
@gaojie Are you on an iMac or a MacBook?
I'll try to provide what help I can with this information.
(she/they)
Get my 1.10.2 modpack :D, Quae Machinis (Machines and Things)
Have a nice day!
There's a report on the bug tracker that confirms this as being an issue in 1.14.3 on MacOS, with no known fix provided (it appears to be a bug within LWJGL itself):
MC-154271 Rolling shutter issue on MacOS since 1.14.3 Pre-Release 2
However, in a related report somebody mentioned that the location of the tear appears to be fixed relative to the screen, not the game window, so by moving the window you can can move it out of it (unless you play on fullscreen).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
The issue occurs on both my internal iMac display, as well as my external thunderbolt display.
From the sounds of it, it's strictly a 1.14.3 issue, and I am not the only one who experiences the issue. I suppose I just have to wait for the next update to see a fix.
@TheMasterCaver thanks for providing the bug report. I will comment on it notifying them that this happens to me too.
Is there anything else I can do to help bring more awareness to this issue so that I am more likely to see a fix in a near future version? Lol
Thank you all so much for your feedback !!!