Also were you using the farlands debug flag?
I have a few questions:
- Did this happen to a brand new world you created in this version or a world from a previous version that you upgraded?
- If this was an old world what was the last version it was opening in before this one?
I don’t think so. Feel free to make one
Requesting ownership.
The reporter seems to have not migrated
Can confirm in 26.2
I can confirm.
To add extra context this issue seems to be triggered by loading chunks that have already been loaded previously
Ergo:
- Fly in one direction
- Turn around
- The issue will only affect chunks that you did already load in the past
To be clear I simply didn’t know about the five second timeout. Anyways thank you for this comment I was confused why this was a feature request.
Fixed in 1.21.10 RC1
Updated the reproduction world to load on the latest version
This doesn’t appear to be an issue anymore
This doesn’t appear to be an issue anymore
FPS now is higher than it was 1.21.4
This doesn’t appear to be an issue anymore
Actually it was 26.2 Snapshot 6
Also I suggest you report the VSync issue in another report as it’s completely unrelated to this report.
I have captured two spark profiles which might help understand this issue
Is this still an issue on Linux on 26.3 Snapshot-6?
Ergo, does the Vulkan backend still have lower FPS than OpenGL?
(You might wanna compare the Snapshot-6 Vulkan performance with Snapshot-5 OpenGL performance with since OpenGL got its own performance regression in this snapshot, MC-310568)
The issue seems resolved on windows now.
Idk about Linux.
This issue should be reopened.
The issue was fixed via the improved transparency option but it remains not fixed with that option off.
And this issue is trivial to fix without the need to sample the skybox. It’s just the fog color that needs changing.