Chunky not compatible with distant horizons 2.3.3
Is chunky not supposed to be used with distant horizons? I used chunky with distant horizons in 1.21 and it worked just well. Wanted to update to 1.21.7 and it no longer works
97 Replies
open fabric.mod.json in DH's jar archive and remove chunky from incompatibles
how do i open it
with the archive tool
Use of Chunky is ill-advised as it will cause LODs to contain holes.
this is fixed by flying over the chunk
Distant Horizons provides a new generator mode that provides similar functionality to Chunky called "Full - Saves Chunk".
lol
whats the command for it
It's recommended to install C2ME when using that mode, otherwise the generation speed would be abysmal.
or is that an ui
It's an option in Advance setting -> LOD Building.
okay thanks
hey also
Apparently it's in "World Generator".
after switching from dt 2.2.1 to 2.3.3 it now tells me that the chunks will be loading for 50 minutes
are they like being converted or is the newer version so much slower
Distant Horizons is probably upgrading the existing LOD data if this is your existing world.
Unless that speed shows up after you change the generator mode to Full, of which without C2ME, will be very slow.
Blame Mojank for making their vanilla generator so slow.
but this wasnt a issue before
im assuming its this
You can inspect if its upgrading the data from the game log console.
nope its generally much slower
well
Default CPU preset?
it generated some of the chunks so i went on disabled dt rendering and reenabled it
those generated chunks are now loading ultraslow
extreme
no
paid for the whole cpu
C2ME installed or no?
yes
Pi Guy, any pointers?
It was added for a reason and without a valid reason to remove it, it should stay there
the older version was so much faster wth
should i just go back
One thing I can say is that the difference in generation speed between Features and Full is that Full is at least 15% slower than Features.
The full generation is generally a lot slower than features
whats full
This.
i think u mean this
You can try setting the
globalExecutorParallelism in the c2me.toml inside your config folder to the number of threads you haveFeatures at 256 chunk on my 5600G took around 30 minutes on max CPU preset, and nearly 40 minutes with Full + C2ME.
but I didnt even have to use c2me in the older version
I do have it now though
In the old version dh had performance issues with c2me
to generate or to load?
Generate.
Generate probably
Loading takes less than a minute
best way to deal with a problem is to ignore it
Until holes start appearing, I guess.
Then why do you keep pointing them out in other servers
:widegladeline2:
so
Hmm???
im certain this version is slower in chunk generation
disable distant gen during chunky pregen i guess
is there a reason for this
!chunky
Using Chunky to pregenerate for DH is not recommended for several reasons. The first one is the swiss cheese that might show up when using chunky while DH is installed. The second reason is that it's pointless, as DH has a build in pregenerator that is better integrated than chunky:
- It saves space by only storing LODs, not normal chunks
- It is faster to use DH's pregenerator to generate the LODs than first using chunky to generate the normal chunks, and then using DH to convert the normal chunks to LODs
- It is part of DH, and therefore always/only called when DH needs it
- Chunky calculates it's radius in blocks, confusing the user if they are not aware of this
Distant Horizons' built-in LOD pregenerator is enabled by default, and can be sped up or slowed down by changing the
Cpu Load in DH's settings, or disabled by turning off Distant Generation.
If you want to pregenerate both LODs and normal chunks, set the Distance Generator Mode to Internal Server under Advanced, World Generator. This will of course take up quite a lot more storage space. Make sure you have C2ME installed if you want to use Internal Server, as the generation speed will be crap if you don't.
Note, this also applied to other similar pregeneration mods.
They've been talking nonesense in cortex's server
Calling ishland a bad coder without any evidence
If it's actually slower, then time for me to put that into testing.
Is
DH-Autobenchmark have any updates, Skillnoob_?
:cou:ishland is my favourite china spy
You can swap out the DH version and benchmark with that
What
Good enough for me.
i just realized how bad the holes problem with chunky was
how do i disable distant horizons generating chunks though
By removing it from the mods folder.
is there seriously no option for that
The way Distant Horizons work requires you to physically remove it.
No, chunky triggers chunk load events and DH always processes them
I dont want to use chunky
I mean that what needs to be rendered is already rendered the other side is a ocean
Do you want to save chunks?
doesnt distant horizons do that automatically?
Features mode only saves LODs
To save space
It doesn't save the vanilla chunk
huh I thought features mode allows you to see things like grass and flowers
Alright, let this 1 data point benchmarking commence.
DH doesn't render flowers or grass
Wait, this benchmarking is flawed.
Btw there's a update to the program
They're rendered as full blocks, or in this case, patch of colors after merging with the block below.
yes
well
now its merging with the block below
in the earlier version it didnt
and i liked that more
is there a way to reenable that
Then you can add the flowers to the ignored blocks
Thats in the dh config file i think
grass used to be 3d so it made plains and similar biomes look much nicer
now they just look bald
I don't think DH ever rendered grass and flowers as their actual blocks
It sure is flawed on the first run, now it's a lot more reasonable.
Wait...
look at the left side
Nevermind, false alarm.
you can see the plain being supper messy
super*
thats grass being rendered by dh
version 2.2.1
2.2.1.a
comparison to 2.3.3 where its bald
Interesting, did the default config changed for ignored blocks?
no idea
but i remember this was enabled by a setting
okay i found it
graphics > quality > blocks to ignore
sorry if i made this hard guys thanks for all of your help
Features seem to be much faster with 2.3.3. It finished 2 minutes faster than previous average.
Maybe this custom seed is best case for Distant Horizons?
Hmm, that estimated finish time doesn't seem good.
This is with C2ME installed with default settings.
C2me by default doesn't use all threads
Set the
globalExecutorParallelism in the c2me.toml inside your config folder to the number of threads you haveI'm going to cancel this run and do that.
Seems to be inline with previous test with C2ME. Will wait for it to finish and calculate the time difference.
40 minutes compared to 28. That's roughly 34% slower.
