Anti-aliasing does not apply until framerate limit is changed

Anti-aliasing does not properly apply when launching Minecraft Bedrock on Windows.
Even though anti-aliasing is enabled in the settings, jagged edges remain visible until the framerate limit setting is changed manually.

As shown in the attached images/video, anti-aliasing only starts working after adjusting the framerate slider in the video settings.
Once anti-aliasing becomes active, it remains enabled until the game is closed. However, this issue occurs every time the game is launched.

Steps to Reproduce:
1. Launch Minecraft Bedrock
2. Enter any world
3. Observe jagged edges on thin blocks such as fences, chains, or glass panes
4. Open Video Settings
5. Change the framerate limit slider
6. Observe anti-aliasing immediately becoming active

Expected Result:
Anti-aliasing should function correctly immediately after launching the game without requiring any setting changes.

Actual Result:
Anti-aliasing does not apply on startup and only becomes active after changing the framerate limit setting.

Additional Information:
• GPU drivers are fully updated
• Tried changing the vsync setting in options.txt (vsync:1)
• Tried enabling/disabling “Improved Input Response”
• Tried reinstalling the game
• None of these resolved the issue

This issue started occurring around 2026-05-10, when version 1.26.20 was the latest release, before updating to 1.26.21.

The only other notable changes around that time were:
• A Windows 10 update
• Gaming Services being updated

Because of this, the issue may be related to Microsoft-side rendering/runtime behavior rather than Minecraft itself, although this is only speculation.

Please investigate whether this inconvenient problem can be reproduced within the company.