Note: This was fixed in a Windows Update, but the update does not get automatically installed by Windows 11. To install the update, go to Windows Settings > Windows Update > Advanced options > Optional updates and find either "2022-01 Cumulative Update for Windows 11 for x64-based Systems (KB5008353)" or "2022-01 Cumulative Update for Windows 11 for ARM64-based Systems (KB5008353)" and install it. EDIT: This is included in the February security patch for Windows 11
This was discovered while testing MCPE-110006
After upgrading to Windows 11, the hidden V-sync toggle in options.txt does not function and is always disabled, regardless of if the option is set to enabled. This results in higher framerates than expected, and can be a bit of frustration for some who prefer each game to have its own V-sync toggle (although I am not one of them).
Notes:
This option cannot be toggled in the game options. It can only be changed by modifying the options.txt file.
This issue has been tested on and does not occur on Windows 10, only Windows 11 has this issue.
Due to MCPE-110006, it is possible to enable V-sync by putting the game in full-screen.
If V-sync is enabled on the GPU, the game respects that and enables V-sync, this limiting the framerate.
It is not believed that this is a hardware-specific issue, as this has been tested on multiple hardware configurations and all were experiencing this issue.
Attachments
Comments 5
Someone said that V-sync will properly limit framerates if you install KB5008353. However, that is unverified, since I can't seem to get KB5008353 by itself (I'm seeing KB5009566, but even after installing that, the V-sync toggle remains broken). I haven't tried installing the Insider previews, as I had a feeling that there would be more issues there than on the public release of Windows 11.
I wonder if this is somehow related to the more recently discovered HDR bug in Windows 11. It sounds weird to me, but the only way to know is if the HDR bug is fixed.
I recently got the KB5008353 update and yes, it does fix the V-sync issue. However, Windows does not automatically install the update, so it needs to be manually installed by the user.
At this point it's probably okay to close this issue now that we know that it was fixed by a Windows update (we should be seeing the February security patch soon, which in theory, also includes the fix)
EDIT: Microsoft had released the February security patch (KB5010386) at around the same time I originally commented, and I did confirm that the fix did get carried into the February security patch.
[^20211218_204842[1].jpg]