[MC-42135] Troubles with VSync with and without Triple Buffering

Here are some tests:

1.1. Playing in windowed mode with VSync disabled, no frame limit and driver-side Triple Buffering disabled will result in ~100-150 FPS with tearing effects.
1.2. Enabling VSync will result in 60 FPS and the tearing does stop.
1.3. Setting the frame limit to 50 will result in 50 FPS with no tearing.
1.3.1 This could already be a bug as either there should be tearing effects with 50 FPS or the FPS should go down to 30.

2.1. Playing in windowed mode with VSync disabled, no frame limit and driver-side Triple Buffering enabled will result in ~100-150 FPS with tearing effects.
2.2. Enabling VSync will result in 60 FPS and the tearing does stop.
2.3. Setting the frame limit to 50 will result in 50 FPS with tearing.
2.3.1. Due to Triple Buffering the 50 FPS are here correct but the tearing should not appear.

Also I'm noticing heavy performance impacts on input as soon as Minecraft is minimized if Triple Buffering is enabled.

Attachments

crash.log

crash-2013-12-16_11.30.10-client.txt

Comments 15

kumasasa 2013-12-15T23:10:25Z

Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt) here.

kumasasa 2013-12-24T16:34:01Z

Cannot see anything strange in crash report.
Newest driver is used:

OpenGL: GeForce 8600 GT/PCIe/SSE2 GL version 3.3.0 NVIDIA 331.20, NVIDIA Corporation

Torabi 2014-01-29T20:08:23Z

Where are you getting the FPS numbers from? Are you sure they mean what you think they mean? There are different strategies for limiting FPS. Your first example could be fitting 50 frames into 60 by reusing frames.

Tearing with VSync and Triple Buffering seems like a bug though.

user-ed7ab 2014-01-29T22:57:43Z

> Where are you getting the FPS numbers from?

From the ingame menu (F3).

Deleted account 2014-03-31T12:13:58Z

Is this still a concern in the current Minecraft version 14w11b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. - bot

5 more comments

user-ed7ab 2014-04-02T14:38:37Z

I'm noticing a little difference:

> 1.3. Setting the frame limit to 50 will result in 50 FPS with no tearing.

I'm seeing tearing effects but they are hard to see (maybe they existed already in 1.7.4). Setting the frame limit to 40 FPS makes them easier to see. Currently I can't tets the part related to TripleBuffering as I'm noticing other issues (maybe a bug in the driver). But for now the issue is that setting the frame limit to a non-syncing value will break VSync.

fienxjox 2014-07-29T19:40:11Z

Your Java version is out of date! Please update your Java to the latest version (1.7.0_65): http://www.java.com/en/download/.

When using a 32-bit browser on a 64-bit operating system the automatic version detection will only show the 32-bit version of Java, the 64-bit version needs to be downloaded manually: http://www.java.com/en/download/manual.jsp.

Please report if the issue persists with the latest Java version as well as the latest 14w30c snapshot.

user-ed7ab 2014-07-29T20:01:03Z

Even with all updated the issue still exists but I figured out something new: The tearing issues appears if I enter a map with VSync enabled but disabling and enabling it fixes the issue. But leaving and joining again a map will cause this issue again until I disable and enable VSync again.

Edit: By accident you have closed this ticket and it seems I can't reopen it.

fienxjox 2014-07-29T20:05:24Z

The new process calls for moving stale (read: months with no update) to a status of "Awaiting Response" until something is updated. Please attach an updated forced crash report

user-ed7ab 2014-07-29T20:16:35Z

> The new process calls for moving stale (read: months with no update) to a status of "Awaiting Response" until something is updated.

Hm, I'm not sure what you are meaning.

> Please attach an updated forced crash report

In the attachments is the new log.

galaxy_2alex 2014-10-26T13:14:42Z

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

user-ed7ab 2014-10-29T07:56:23Z

Yes, the bug does still exist in this version.

> The tearing issues appears if I enter a map with VSync enabled but disabling and enabling it fixes the issue.

On this test disabling and enabling VSync has not fixed the issue but the tearing was more difficult to see (probably I have just not noticed it on the last test).

galaxy_2alex 2014-10-29T12:02:38Z

Reopened, thanks

kumasasa 2015-11-21T08:55:39Z

Is this still an issue in the current Minecraft Snapshot 15w47c or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

user-f2760 2017-02-14T15:12:17Z

Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.