22 Replies
not possible to fix. it is intended behavior.
the bamboo looks like that because DH is not capable of rendering smaller than a 1x1 meter cube, this is the smallest it can render
I have the same problem, I understand, that the bamboo is rendered as 1 block, that is not the problem. It kinda is way too high and renders "on top" of the actual bamboo, then vanishes when you get close to it.
looks like the LODs still need to update. turn cpu load up and give it some time
i suspect the bamboo used to be that high when the LOD was created, and has not been updated yet when it got shortened
cpu load on max for several hours playing like this since installed DH. The bamboo is already on max height. it is impossible to be as high as rendered by DH
not sure then
turned down the MC render distance to force DH to kick in. Then you can see it was way too high. when I put something next to the bamboo the DH is updated for that single bamboo:
I reset the DH files of the save to force a new DH calculation. That solved it for bamboos very close. But Bamboos far away still got calculated too high again. Any other idea? would appreciate!
what do you mean with that you reset the DH files? did you delete the sqlite files?
yes
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
Why only bamboo...?
found out this only happens for generated bamboo where the chunks were never updated by removing a block or something. Once one block of bamboo is removed the chunk updates and the LODs look normal in that chunk. If you open the world per LAN to someone who has the problem in singleplayer as well, they do not have the problem on the world opened per LAN. So there might be a difference between the world data that is sent to another player per LAN and the world data you have yourself. As the LODs are generated right after the world is generated, could there be some sort of "temporary" bamboo generated (to check maximum generation hight maybe or something) that is removed shortly after, while LODs are already generated?
Just found it: if I switch "distant generator mode" to "pre existing chunks only" the problem is gone.
tipp: use chunky to generate the world so LODs then can be generated
Are you using C2ME? I'm guessing this happens because multithreaded worldgen has a slight difference to non multithreaded. DH multithreads, but it doesn't save the chunks, only the LODs. When exploring these chunks, the bamboo will be different, as the chunks need to be generated using vanilla world gen, as DH didn't save these chunks. Vanilla world gen isn't multithreaded, so theres a difference between vanilla chunks and LODs. Chunky also multithreads, so when using chunky, everything uses the same worldgen and the issue won't occure
If you aren't using C2ME, you could try using it and see if the issue still occures. If it does 't occure anymore after adding C2ME, it confirms above
i was not using C2ME, adding it does not fix it.
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
after changing the setting you need to delete the DH sqlite files in your save file -> data, so the LODs are re-generated
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
Problem is also present on forge 1.20.1 regenerating existing chunks without setting the "distant generator mode" to "pre existing chunks only" apperantly also dosnt help I still need to test if blockupdates(?) (placing/destroying blocks) will help
Distant setting was on whatever the default is
This worked for me.
I was getting LODs that didnt correspond to the terrain that loaded in when I came within vanilla Render Distance, changing this setting and exiting Minecraft then deleting the sqlite files then re-generating the LODs fixed it.