[NeoForge] [1.21.10] LOD not appearing in certain chunks
Hi all, I've tried searching through all issues in the Gitlab site and here, but I can't seem to find a precise solution to my problem.
I created a dedicated server with mostly vanilla configuration and did a small modpack to play with my friends, obviously having DH both in server and clients (DH 2.3.6-b). All is working fine, F3 shows client connected to DH in server, etc. As far as I'm concerned, I have no other mods that affect chunks/LOD besides C2M.
Mostly it's working fine but, strangely, I'm getting some "LOD holes" in the exact same chunks every time. As you can see, the rest of the surrounding chunks are rendering fine. The solutions I've tried:
- Tried deleting all generated LODs from Client and Server and restarted again, did /dh pregen <world> <center> 256 and let it run, other LODs around are generating just fine. It's the same zones even after deleting the .sqlite files and recreating them again.
- Changed generation mode in server to INTERNAL_SERVER, but log got filled by errors about non-existing chunks (even if I ran pregen with C2M installed), so I changed back to FEATURES
- Tried changing Minecraft render distance to minimum and playing with Overdraw Prevention values, other LOD is working fine besides in those chunks (Attached pictures). Increasing Minecraft render distance delays the issue a bit.
- Tried updating the chunk by adding extra blocks to trigger updates.
- Tried changing disableUnchangedChunkCheck to true to see if the LODs would regenerate, nothing.
Chunks as far as I'm concerned are generated perfectly since if I walk over those there's terrain, but as soon as I get away from the chunk(s), LOD starts to not appear in that zone.
I'll attach in another message some errors in the client logs that I'm getting but I'm not sure if they're related to the issue chunks/LOD.
Feel free to ask for more clarifications or anything else you could think of, I've been trying to search about the issue but I'm at my wit's end 😅
5 Replies
Tried also to follow the instructions in !forceupdate and can confirm that I'm able to update any other chunk beside those with the issue (I put some new blocks and they get rendered in the LOD after some seconds, so no overload apparently)
To force a DH LOD to update, you should go to affected chunks one by one and place/destroy a couple of blocks, then wait a while in close proximity to the outdated chunks.
To make the process more reliable, you can:
- Increase the number of placed/broken blocks
- Increase the DH CPU load preset
- Decrease the DH RD
- Re-enter the world before starting the process (but after decreasing the DH RD)
- wait longer in even closer proximity
Ok, I managed to isolate the issue. The chunks where this is happening contain trial chambers 😕. I just realized now that the log also mentions Lootr, but as far as I checked Lootr shouldn't be incompatible with DH, and also, other places where Lootr chests are available (underwater, villages, etc) are working fine, strange.
EDIT: Seems the issue could be Lootr-related since it's not exactly the trial chamber chunks that are failing to render the LOD, but some chunks of the trial chambers that apparently contain Lootr barrels? Chunks of the trial chambers without barrels are being rendered fine. Opened a Discord issue for Lootr, I'll leave this up temporarily until I get an answer from anyone. Thanks!
It seems that the issue was previously reported a month ago but I wasn't able to find it on the issue page: https://gitlab.com/distant-horizons-team/distant-horizons/-/issues/1117
I've managed to contact the creator of Lootr and they've replied in the issue explaining a bit in detail (detail I can't provide since I'm not a mod creator 😅 ) what the root cause apparently is. If you could take a look that'd be appreciated! Not sure if you want me to mark this issue as "resolved"? (It's not resolved per se but maybe you want the conversation focused on the Gitlab issue instead?)
GitLab
Unexpected issue creating render data for pos (#1117) · Issues · ...
Check off each item in this list before submitting: