Question regarding chunk loading
✅Solved
Fabric/Quilt
MC 1.21.x
Fabric/QuiltMC 1.21.xHello,
My friends and I have the following grid-like visual pattern when travelling at fast speed on chunks that DH server has generated and that we haven't entered yet, as can be seen here : https://www.youtube.com/watch?v=mQwSEKT9K3M
Is this the "hole in the ground" issue that is mentioned in the FAQ? The funny thing is that installing C2ME completely fixes the issue (which is awesome) but I am still wondering if the bug is indicative of either a slow CPU/storage/network on the server or an underlying bug in how DH works.
I've also tried removing DH on the server and exploring the LODs it had generated before and the issue was still there. No particular server logs, I did try with default garbage collector and with ZGC, no change.
Client mods :
- iris
- fabric API
- DH
- sodium
Server mods (fabric) :
- DH
- Lithium
So not a critical bug (if it is one) at all since C2ME fixes it, but i'm still intrigued
My friends and I have the following grid-like visual pattern when travelling at fast speed on chunks that DH server has generated and that we haven't entered yet, as can be seen here : https://www.youtube.com/watch?v=mQwSEKT9K3M
Is this the "hole in the ground" issue that is mentioned in the FAQ? The funny thing is that installing C2ME completely fixes the issue (which is awesome) but I am still wondering if the bug is indicative of either a slow CPU/storage/network on the server or an underlying bug in how DH works.
I've also tried removing DH on the server and exploring the LODs it had generated before and the issue was still there. No particular server logs, I did try with default garbage collector and with ZGC, no change.
Client mods :
- iris
- fabric API
- DH
- sodium
Server mods (fabric) :
- DH
- Lithium
So not a critical bug (if it is one) at all since C2ME fixes it, but i'm still intrigued
Solution
This hole is created because the vanilla terrain loading can't keep up
It is expected behaviour from DH side as DH can't know if a chunk is loaded or not, because getting this info differs significantly between MC versions, Sodium versions and Optifine versions.
Having so many different code paths would be hard to support and very bug prone.
There is however dynamic overdraw feature in current DH nightly that moves the circle closer the faster you move to reduce this hole
It is expected behaviour from DH side as DH can't know if a chunk is loaded or not, because getting this info differs significantly between MC versions, Sodium versions and Optifine versions.
Having so many different code paths would be hard to support and very bug prone.
There is however dynamic overdraw feature in current DH nightly that moves the circle closer the faster you move to reduce this hole
Was this page helpful?
