Significant surface features artifacts on DH 2.2
Minecraft version: 1.20.1
Distant Horizons version: 2.2.0-a
Mod loader: Fabric Loader 0.16.2
Installed mods: Lithium, Distant Horizons
Bug: There are large areas with few or no trees, but when you go there it's a forest. And Log file is bloating.
Steps to reproduce the bug: Generate LODs (seed: 3730872696997453204)
Log: https://mclo.gs/HUapFuH
58 Replies
Too Short; Will Read:
See for how this bug was found → https://discord.com/channels/881614130614767666/1277391201980518561
344mb log file 💀
I created a GitLab issue: https://gitlab.com/jeseibel/distant-horizons/-/issues/790
GitLab
Significant surface features artifacts on DH 2.2 (#790) · Issues · ...
Check off each item in this list before submitting: Check the...
Log is full of this error
Can you give the seed?
I already gave the seed
I would really appreciate it if you can reproduce this bug
ill take a look to see if i can reproduce
imma see if i can reproducce it with less mods
does NOT happen without entity culling, ferritecore and lithium
Watch out for your log file too man it adds up quick
ill delete the instance once im done anyway
still happens without sodium and indium
lithium is the issue
Should i update the issue on installed mods as lithium and distant horizons
yes please
Thx dude it was really late for me so i just couldn't dig into enough and left as it is
np!
@James Seibel (GMT-6) this may be a significant bug. lots of people use lithium
@Puhpine (GMT +2) does log bloating still happens with only lithium
not sure because i deleted the instance, but i think it did yea
Here are chunk, world and generation Lithium settings I dag up:
One (or more) of them is most likely incompatible
Disabling all of
gen
optimizations fix this
It is 1 of the first 4
Found it: mixin.gen.chunk_region
There are still holes in the world...They've got fixed after I've flew over them
.
.
The fix to the OP's problem is disabling
mixin.gen.chunk_region
Lithium option
The line:
mixin.gen.chunk_region=false
Should be added to lithium.properties
config file
.
.
@Puhpine (GMT +2) Can you add this to #faq-mod-support or confirm?i cant, as i cant edit james' messages
You can write a new one
dont know if james would want that, and maybe the bug can be fixed, so that you dont need to edit anything
It can always be deleted later, but OK
oh and i dont even have permissions to write in #faq-mod-support
xD
this also works for me
This is this option description:
mixin.gen.chunk_region
(boolean, default: true)
If true, an optimized chunk cache will be used for world population features which avoids array indirection and complex logic.
I'll take a look at the bug when I have time.
nice!
you are awesome
This bug feels like one of those classic seed-sensitive Minecraft bug where it only occurs on certain seeds. This world seed just so happens to trigger it.
Can't reproduce this on 1.21.1, however, other things I noticed is that there are many features that appears to be sliced at chunk borders. All screenshots are zoomed in with the spyglass. Same setup with OP with the exception of Minecraft version being 1.21.1.
Also, man this speed-up sure helps a lot with getting LODs quickly.
One question, is the button placement messed up in the main menu 1.20.1?
Nevermind, it resets itself once I joined a world.
This is already concerning.
That's a known and long standing world gen issue that isn't planned on being fixed.
That's caused because each DH world gen reqeust only works with 4x4 chunks at a time so anything outside of that will likely be cut off.
Usually the issue is very minor and/or far away so it isn't a big problem.
Either increase your CPU load and/or reduce your vanilla render distance.
I have reasons to believe it's not related to the CPU load setting. I immediately launch the world without much adjusting other settings.
I... probably should look at the logs...
harold emoji
The CPU load setting increases the max number of chunks that can be queued, so increasing it will reduce/fix this problem when first loading into a world.
Currently you have 1 thread set for LOD updating, which only allows 500 chunks to be queued, every thread you add increases that number by 500.
Let me try adjusting that.
Theory debunked, the feature placement bug appears to happen with other world seeds.
Fix works for modded gen as well, thank you
No problem 😸
I'm not seeing this issue in MC 1.21.1 and Lithium 0.13.0.
I'm now testing MC 1.20.1 and Lithium 0.11.2...
I am able to reproduce the issue in MC 1.20.1 and Lithium 0.11.2
Apparently it was removed from Lithium as of MC 1.21 (Lithium 13):
https://github.com/CaffeineMC/lithium-fabric/commit/b7cfd53a1ed0197e1d13dea2799b898eb52ecab3
Can you force disable it with a mixin on game start,
or add the workaround to the FAQ?
We’ll see, I’m still looking into it.
I just pushed a fix for this if someone is willing to test it out.
I might have done something wrong,
but after downloading newest nightly couple minutes ago,
and removing the lithium config workaround
the bug still happens
So just DH and MC 1.20.1 causes that?
Did you try a new world?
I've been able to generate fresh 1.20.1 worlds without issue.
I have faster random and Noisium too
I can try only lithium + DH
DH on its own does not cause this
If you can determine which mods cause the problem that’d be super helpful 👍
Redownloaded DH nightly,
mods:
- DH 2.2.1 dev
- Fabric API 0.92.2
- Lithium 0.11.2 (no manual fix)
- ModMenu
(All newest for MC 1.20.1 on Modrinth)
Works as intended
Good to hear
Added:
- Noisium 2.3.0
- Faster Random 5.1.0
- Dynamic FPS 3.6.3
Works as intended
Added:
- Fabric Language Kotlin
- ImmediatelyFast
- YACL
- Zoomify
Works as intended
The previous nightly I downloaded must have been without the fix?... IDK
It works now
Well I’m glad to hear it’s working as intended 🎉