Mod Version: DynamicSurroundings-1.16.4-4.0.4.2
Forge Version: 36.1.24
Modlist: https://paste.ee/p/6fXvj
Full (Including Generated) JVM Arguments: -XX:+UseG1GC, -XX:+UnlockExperimentalVMOptions, -XX:G1NewSizePercent=20, -XX:G1ReservePercent=20, -XX:MaxGCPauseMillis=50, -XX:G1HeapRegionSize=32M, -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump, -Xms4096m, -Xmx6168m, -Duser.language=en
Main Log: https://gist.github.com/pm065/2ea229ca009bd2a4d0338ac79b4f6f8b (this many lines of Blame and error spam makes paste.ee die; in fact I think I'll just use gist in future)
Crash Log: Game isn't crashing
Screenshot: https://imgur.com/a/QQgzJJP

Going on to a world, within a few seconds log spam (which can be seen at the bottom of the latest.log) appears.

Excellent, looks like it ISN'T DSurround after all... Urgh.

Actually, even though the render issue isn't DSurround, the log spam should probably be addressed.

Okay, this is weird. It only happen when the totally separate issue occurs, which isn't happening on a new world.