mojira.dev
MC-221002

Client doesn't load every chunk sent to it by server

My previous post of this issue was labelled as duplicate despite it being completely different from MC-166508 . So I have reposted. I ask you to look at this harder before grouping it with a vaguely similar issue. This is its own thing.

A server with 8 chunk render distance will only have 7 chunks displayed by the client, the outermost ring of chunks are not rendered despite them being complete by the client, you can see them render by using a mod that lets the clients vision move freely without moving serverside (free-cam), when viewed this way its apparent that the chunk has complete lighting and pallette, so why isn't it rendered? (even with client view distance at 32)

If this problem (intentional or not) were fixed, it would increase the view distance of every player on every server by 1 whole chunk, greatly improving quality of life for everyone.

Linked issues

Attachments

Comments

tryashtar

How about MC-54545?

migrated

Not the same thing @trayashtar

migrated

I prefer reopening [MC-220179] and linking this as a duplicate.

Avoma

Duplicate of MC-223350.

Arisa Bot

Thank you for your report!
We're resolving and linking this ticket forward as a duplicate of MC-223350, as that ticket contains more detailed information and/or has already been triaged by Mojang.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit

Brevort

As the reporter of MC-223350, this seems like quite a different issue.

This definitely isn't the FOV change bug, so it must be comparative to the world not rendering until the player moves their head after the world is first loaded. However, said issue is not present in 1.16.5, so this is likely a distinct bug, as this one is exclusively reported in 1.16.5.

migrated

(Unassigned)

Unconfirmed

(Unassigned)

1.16.5

Retrieved