Strange motion blurring that's not visible to screen sharing or recording.

Please explain the difference to MC-127400 . I cannot see it.

Here's some screencaps from the first video clip; it appears there's some sort of pixel ghosting / smearing happening that doesn't happen in any other game.

It's especially noticeable when you're do a small wiggle in one spot as I did in the first bit of the video; it's like the blurring effect has an additive component and the smearing/ghosting gets worse even as you only wiggle 5 degrees consistently. It's also most apparent with hard color changes between light and dark (like the black and bright green on leaves). Clamping fps to 60 or lower helps to some extent, but it's still there.

In regards to the possibility this is due to a personal perception issue or camera shutter speed (or anything along those lines) I recorded the third video in slow-mo; you can see a more precise example of it here:

Thank you for re-opening it; I wish I knew more about low level graphics to better conjecture about possible causes, but I tried to eliminate factors by trying different monitors and asking friends to check this too.

And in regards to MC-127400; his issue appears to be some sort of perspective tearing because he's rendering with very little vertical pixels; which I would think is different from the pixel bleed that's happening here.

I've also recorded a video trying to replicate MC-127400; I'm not sure I'm seeing the perspective distortion myself.

However in this video you can see the back cobble wall is "quaking"❓ as the camera is rotated; like the pixels won't sit still; however this could be attributed to the stretched recording perspective, trying to record at his aspect ratio was difficult and spread across two monitors. However near the end of the video (in the unstretched display) you can see the cobble pixels vibrating as well; the stretched video recording appears to be exaggerating the affect rather than the causing it.

The following videos are not necessarily indicative of MC-135666 (they are for MC-127400); please refer to the videos in the original report for more accurate demonstration of the issue I've reported.

Youtube upload (compression could be an issue): https://www.youtube.com/watch?v=MWoed9BvLsM

Raw (lossless) download: https://drive.google.com/file/d/1TnXlTutaNQw6I7XVOtYrifOZrbXOWgOy/view?usp=sharing

Is your display using interlaced video?

Is this issue new to 1.13, or does it also affect 1.12.2? (Make sure to use a separate game folder when testing 1.12.2; loading 1.13 content in 1.12.2 corrupts it)

No, none of our displays are using interlaced video; my primary monitor: https://www.amazon.com/LG-32GK850G-B-Gaming-Monitor-Refresh/dp/B078TTXLW5 (this issue arises regardless of display or computer).

I use the twitch client to download and launch each minecraft client; each time a fresh 1.13 jar is downloaded and each new game version receives it's own dedicated folder.

I'll follow up shortly with some tests from older versions of minecraft including 1.12.2

All the following clips were recorded using slow-mo to demonstrate the issue.

1.12.2 Fullscreen (the effect is much less noticable): https://drive.google.com/open?id=1vuF_YDhcJ2ouVTaM2CeluMwTMZUJvF9G
1.12.2 Windowed (looks like 1.13): https://drive.google.com/open?id=1S0PY14tzGnkllo8LX4UnzNMxXJcdGdy0
1.13 Fullscreen (seems identical to windowed 1.13): https://drive.google.com/open?id=1nxYs6zOsuDfHzcGIYtt7o3bqk_6HvOh2
1.13 Windowed (For reference, 3rd link in original post showed the same circumstances): https://drive.google.com/open?id=1sKtMiM1jmClvBKi8kiz6O4at8tKn8AjO

Please excuse the audio, I believe my phone's slow-mo mode is adding it.

As you might see from the videos, 1.12.2 fullscreen was the only outlier (even then there was an issue); perhaps the change to add a fullscreen resolution option in 1.13 contributed / touched the code that's causing this. 1.13 fullscreen vs windowed shows no difference.

For reference, I decided to test 1.0:

Fullscreen (lots of screen tearing because of a lack of vsync): https://drive.google.com/open?id=1Nkn4GU0zzpjRNyn0bJqvCCRneE6bmXF4
Windowed (Windows 10 has built-in vsync, correcting the issues from fullscreen): https://drive.google.com/open?id=1cFnhNo6htqIrsCsrC31Sbfg4P5sbbyvS

All the visual artifacts in 1.0 are caused by screen tearing, windowed mode seems to eliminate them. Therefore this issue arose sometime after version 1.0.

For comparison, I went frame by frame from both 1.0 and 1.13 to show what happens at peak movement: (both in windowed mode)

  1.0: 

1.13: 

As you can see, 1.0 has a slight blur that I'd attribute to either Window's built-in vsync or some other component; 1.13 clearly has some sort of pixel stutter.