Servers with dynamic render distances causes the render to start from scratch and reload all chunks (like doing f3 + a)

[lostallmymoney]

Bug Description

Playing on anarchy servers lead to the dynamic render distance based on speed revolution...
This means we have lots of servers dynamically changing render distances.
Which leads to this sodium bug where the rendering is fully refreshed and effectively flickers instead of un-rendering outer chunks.

Reproduction Steps

Join 2b2t, fly with elytra at max speed with elytra packetfly.
MC 1.21.4
sodium 0.6.13

Log File

Logs

Crash Report

Crash

[lostallmymoney]

Also happens when view distance is increased server side

[douira]

We need to reload the renderer when the render distance changes to invalidate the state of the chunk tracker. Changes to the chunk tracker and probably also Minecraft's client-side chunk handling logic would be necessary to deal with this as far as I can tell.
To triage this issue,

• please send us a video with the F3 screen open of what this issue looks like on 1.21.11 with Sodium 0.8.4.
• Also confirm whether vanilla, i.e. the game on 1.21.11 without Sodium, has the same issue and send us a video of that.
• Send us a log file
• Send us a crash report

Without this information the issue will be closed.

[georgepabvloski-crypto]

It does.. And everyone's on 1.21.4 btw