Lentern
- Lentern
- JIRAUSER563891
- America/New_York
- Yes
- No
MCL-16374
REALMS-7558
MC-241193
MCPE-152608
Normal
When enabling the "Use VSync" (or just "VSync" in new snapshots) option from the video settings menu, your FPS will be set to a value that is above your monitor's refresh rate before setting it to your actual refresh rate.
In the video attached, the monitor I am using is set at 60hz. When I enable VSync, the FPS is set to 61 before going to 60.
Windows 10, Java 8 Update 271Bundled Java Executable, Windows 10
Enabling VSync sets FPS to a value above monitor refresh rate before setting to correct framerateCapping FPS/enabling VSync sets FPS to a value above monitor refresh rate before setting to correct framerate
When enabling the
"Use VSync" (or just "VSync" in new snapshots) optionfrom the video settings menu, your FPS will be set to a value that is above your monitor's refresh rate before setting it to youractualrefresh rate.In the video attached, the monitor I am using is set at 60hz. When I enable VSync, the FPS is set to 61 before going to 60.
When enabling the VSync option or capping your FPS from the video settings menu, your FPS will be set to a value that is above your monitor's refresh rate before setting it to your intended cap/monitor refresh rate.
In the video attached, the monitor I am using is set at 60hz. When I enable VSync, the FPS is set to 61 before going to 60.
Capping FPS/enabling VSync sometimes sets FPS to a value above intended cap/monitor refresh rate before setting to correct framerate
When
enabling the VSync option or capping your FPS from the video settings menu, your FPS will be set to a value that is above your monitor's refresh rate before setting it to your intended cap/monitorrefresh rate.In the video attached, the monitor I am using is set at 60hz. When I enable VSync, the FPS is set to 61 before going to 60.
The Bug:
When you set an FPS cap, your FPS sometimes goes above the intended cap before setting to the correct value.
Reproduction Steps:
- Open your debug menu
- Cap your FPS/enable VSync
→Notice how your FPS goes above the intended cap before setting to the correct value.
Additional Information:
- May be invalid (https://bugs.mojang.com/browse/MC-206019?focusedCommentId=991289&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-991289)
- This bug affects 20w48a and 21w05a but I forgot to add them.
Capping FPS/enabling VSync sometimes sets FPS to a value above intended cap/monitor refresh ratebefore setting to correctframerateCapping FPS/enabling VSync sometimes sets FPS to a value above the intended cap before setting to correct cap
Capping FPS/enabling VSync sometimes sets FPS to avalue above the intendedcap before setting tocorrectcapCapping FPS/enabling VSync sometimes sets FPS to above cap before setting to cap
The Bug:
When you set an FPS cap, your FPS sometimes goes above the intended cap before setting to the correct value.
Reproduction Steps:
- Open your debug menu
- Cap your FPS/enable VSync
→Additional Information:
- May be invalid (https://bugs.mojang.com/browse/MC-206019?focusedCommentId=991289&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-991289)
- This bug affects 20w48a and 21w05a but I forgot to add them.
The Bug:
When you set an FPS cap, your FPS sometimes goes above the intended cap before setting to the correct value.
Reproduction Steps:
- Open your debug menu
- Cap your FPS/enable VSync
→Additional Information:
- This bug
affects 20w48a and 21w05a but I forgot to add them.The Bug:
When you set an FPS cap, your FPS sometimes goes above the intended cap before setting to the correct value.
Reproduction Steps:
- Open your debug menu
- Cap your FPS/enable VSync
→Additional Information:
- This bug most likely affects every version of Minecraft that includes VSync, so missing versions don't really matter.
Bundled Java Executable, Windows 10Java 16.0.2, Windows 10
Debug Menu Screenshot.png
Capping FPS/enabling VSync sometimes sets FPS to above cap before setting to capLimiting framerate sometimes sets framerate to wrong value before correcting
The Bug:
When you
set an FPS cap, your FPSsometimes goes above the intendedcapbefore setting to the correct value.Reproduction Steps:
- Open your debug menu
Capyour FPS/enable VSync
→Additional Information:
- This bug most likely affects every version of Minecraft that includes
VSync, so missing versions don't really matter.The Bug:
When you limit your frame rate (or enable VSync) your frame rate sometimes goes above the intended limit before setting to the correct value.
Reproduction Steps:
- Open your debug menu
- Limit your FPS/enable VSync
→Additional Information:
- This bug most likely affects every version of Minecraft that includes FPS limiting, so missing versions don't really matter.
Limiting frame rate sometimes sets frame rate to wrong value before correcting
Limiting frame rate sometimes sets frame rate to wrong value before correctingFrame rate gets set to wrong value when adjusting limit
The Bug:
When you limit your frame rate (or enable VSync) your frame rate sometimes goes above the intended limit before setting to the correct value.
Reproduction Steps:
- Open your debug menu
- Limit your FPS/enable VSync
→Additional Information:
- This bug
mostlikely affects every version of Minecraft that includes FPS limiting, so missing versions don't really matter.The bug
When you limit your frame rate (or enable VSync) your frame rate sometimes goes above the intended limit before setting to the correct value.
Steps to reproduce
- Open your debug menu
- Limit your FPS/enable VSync
→Additional information
- This bug likely affects every version of Minecraft that includes FPS limiting.
The bug
When you limit your frame rate (or enable VSync) your frame rate sometimes goes above the intended limit before setting to the correct value.
Steps to reproduce
- Open your debug menu
- Limit your FPS/enable VSync
→capbefore setting to the correct value.Additional information
- This bug likely affects every version of Minecraft that includes FPS limiting.
The bug
When you limit your frame rate (or enable VSync) your frame rate sometimes goes above the intended limit before setting to the correct value.
Steps to reproduce
- Open your debug menu
- Limit your FPS/enable VSync
→Additional information
- This bug likely affects every version of Minecraft that includes FPS limiting.
The bug
When you limit your frame rate (or enable VSync) your frame rate sometimes goes above the intended limit before setting to the correct value.
Steps to reproduce
- Open your debug menu
- Limit your FPS/enable VSync
→Additional information
- This bug likely affects every version of Minecraft that includes FPS limiting.
When the ender dragon is sitting at the portal, arrows that bounce off of it are lit on fire. It is quickly put out automatically about
2seconds after it bounces.When the ender dragon is sitting at the portal, arrows that bounce off of it are lit on fire. It is quickly put out automatically about 1 seconds after it bounces.
When the ender dragon is sitting at the portal, arrows that bounce off of it are lit on fire. It is quickly put out automatically about 1 second
safter it bounces.
Java 8 Update 271, Windows 10
FPS withvsync occasionally goes above monitor refresh rateFPS with VSync occasionally goes above monitor refresh rate
Java 8 Update 271, Windows 10Bundled Java Executable, Windows 10
With
vsync enabled in video settings, your fps will occasionally go above your monitor's refresh rate.In the attached screenshot, my fps is above my monitor's refresh rate (60hz).
With VSync enabled in video settings, your fps will occasionally go above your monitor's refresh rate.
In the attached screenshot, my fps is above my monitor's refresh rate (60hz).
With VSync enabled in video settings, your
fpswill occasionally go above your monitor's refresh rate.In the attached screenshot, my
fpsis above my monitor's refresh rate (60hz).With VSync enabled in video settings, your FPS will occasionally go above your monitor's refresh rate.
In the attached screenshot, my FPS is above my monitor's refresh rate (60hz).
FPS with VSync/FPS cap occasionally goes above monitor refresh rate
With VSync enabled or having your FPS capped in video settings, your FPS will occasionally go above your monitor's refresh rate.
In the attached screenshot, my FPS is above my monitor's refresh rate (60hz).
'll continue to add effected versions until this report is closed.
W
ith VSync enabled or having your FPS capped in video settings, your FPS will occasionally go above your monitor's refresh rate.In the attached screenshot, my FPS is above my monitor's refresh rate (60hz).
The Bug:
When capping your FPS/having VSync enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- May be invalid
- This bug affects 21w05a but I forgot to add it.
The Bug:
When capping your FPS/having VSync enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- May be invalid
- This bug affects 21w05a but I forgot to add it.
The Bug:
When capping your FPS/having VSync enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- May be invalid (https://bugs.mojang.com/browse/MC-206019?focusedCommentId=991289&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-991289)
- This bug affects 21w05a but I forgot to add it.
The Bug:
When capping your FPS/having VSync enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- May be invalid (https://bugs.mojang.com/browse/MC-206019?focusedCommentId=991289&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-991289)
- This bug affects 21w05a but I forgot to add
it.The Bug:
When capping your FPS/having VSync enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- May be invalid (https://bugs.mojang.com/browse/MC-206019?focusedCommentId=991289&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-991289)
- This bug affects 20w48a and 21w05a but I forgot to add them.
FPS with VSync/FPS cap occasionally goes abovemonitor refresh rateFPS with VSync/FPS cap occasionally goes above cap
The Bug:
When capping your FPS/having VSync enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- May be invalid (https://bugs.mojang.com/browse/MC-206019?focusedCommentId=991289&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-991289)
- This bug affects 20w48a and 21w05a but I forgot to add them.
The Bug:
When
capping your FPS/having VSyncenabled, your FPS will sometimes go above the intended cap.Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- This bug affects 20w48a and 21w05a but I forgot to add them.
The Bug:
When you have an FPS cap enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- This bug affects 20w48a and 21w05a but I forgot to add them.
I'll continue to add affected versions until this is marked as resolved.
The Bug:
When you have an FPS cap enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- This bug
affects 20w48a and 21w05a but I forgot to add them.The Bug:
When you have an FPS cap enabled, your FPS will sometimes go above the intended cap.
Reproduction Steps:
- Cap your FPS/enable VSync
- Open your debug menu
→Additional Information:
- This bug most likely affects every version of Minecraft that includes VSync, so missing versions don't really matter.
Bundled Java Executable, Windows 10Java 16.0.2, Windows 10
screenshot of f3:
Hello, this is my new account.
This bug does not appear in new releases of Bedrock Edition.
Confirmed in 1.16.4, affects horses too
Fix: https://streamable.com/zliaut
OptiFine issues aren't tracked on the bug tracker, they can be reported on sp614x's github page.
This bug was magically fixed in 21w10a. Not sure how, but if anyone from the mod team sees this, mark it as fixed in 21w10a.
Can't confirm for 21w11a because of
MC-219849Not sure how this is a duplicate if this issue was created first.
Unblocked in 21w14a.
I should mention this in case it hasn't already been posted.
PaperMC fix: https://github.com/PaperMC/Paper/pull/4872
PaperMC version before fix (build 326 is unavailable): https://papermc.io/api/v2/projects/paper/versions/1.16.4/builds/325/downloads/paper-1.16.4-325.jar
PaperMC version after fix: https://papermc.io/api/v2/projects/paper/versions/1.16.4/builds/327/downloads/paper-1.16.4-327.jar
FPS in 1.16.5: 463
FPS in 1.17.1-rc2: 310
OS: Windows 10 21H2 19043.1081
CPU: Intel Core i7 9700F @ 3.00 GHz
GPU/GPU driver version: NVIDIA GeForce GTX 1650 (version 471.11)
Profiling ZIP: https://bugs.mojang.com/secure/attachment/422512/2021-07-05_15_06_17-PerformanceTest1_17-1_17_1-rc2.zip
Probably a duplicate of my
MC-241193report, but thank you for adding additional information. Feel free to comment/attach stuff to my report. I am using a Windows 10 PC so there may be different results.Can confirm for 1.18-pre4
This issue was fixed in 1.18-pre2, but
MC-241194was used to track the bug, despite me creating this report first.I didn't see this report when I made
MC-252059, so you're welcome to look at that for another example.This should be closed as a duplicate of MC-63, it's been a while.
I've restyled the description to hopefully contain enough information.