sodium problems
I'm using iris, sodium, DH and tectonic as my main mods and couple of other optimization mods (all for 1.21) but i found that the newest version of sodium 6.0.0 with the newest versions of other main mods gives notesably worse performance than previos versions (sodium 5.11, DH 2.1.2, iris 1.7.3). theres also a problem where shaders wont load if i have DH enabled, so i have to disable DH, enable the shaders and enable DH again. i am using amd cpu and gpu and i'm playing fabric 1.21.
Solution:Jump to solution
you have another mod changing the max render distance. Bobby does that but I don't know why you'd want to increase it if you're already using Distant Horizons, which by default gets you 128 chunks of LODs for less of a performance impact than something like 48 chunks of normal render distance without DH
30 Replies
do you have litematica?
other issue with DH sounds like the usual DH crash that breaks shaders (prevents Complementary from compiling and causes the terrain to create copies of itself over the skybox with Bliss). The fix is restarting the game and not touching certain DH shaders without first disabling shaders
i dont use it, i can send you the list of mods i use, but even when i used only the nevest version of the main mods, i still get worst performance than older versions
can you compare performance of ONLY sodium and iris, between 0.5.11 & 1.7.3 vs 0.6 & 1.8
and send a screenshot of your F3 menu of both tests if the performance is still worse on the newer betas
ok, it will take like 5-10 min tho
yeah no problem, I'll be here
new versions have less bugs and are better with DH and such, but the main thing thats bothering me tho is that the chunks generate, render slower and are capped at 32 (even tho i'm using 8gb of ram), i am usualy using c2me tho (not in this 2 screenshots)
java edition has a limit of 32 chunks no matter what your hardware specs are. It doesn't dynamically change like on bedrock edition
anyway, looks like they perform relatively the same between the two versions?
if that's the case, could you try adding DH 2.1.2-a and Indium for the older version test and adding DH 2.2.1-a for the beta test and see if it's DH causing the difference in performance
Distant Horizons renders its own chunk. It would be best to set your vanilla render distance lower and use the LOD Distance option in Distant Horizons settings instead for that. Besides, Distant Horizons works around Java Edition's render distance limitations.
Bedrock Edition have no issues rendering 256 real chunks and it does that at blazing fast speeds because :thonkjang: writes a much better chunk building code for it.
also you mentioned you usually use C2ME. It's not recommended to use that in conjunction with Distant Horizons as it may potentially hinder the speed at which DH does its own chunk loading
And yet Bedrock Edition players want Distant Horizons on their platform... Either they don't know how stupid fast Bedrock Edition is, or they're not willing to shell out for a better device that allows Bedrock Edition to flex its blazing fast chunk builder.
:linus:
i do use DH but its performance is normal, if i disable it, the normal chunk generation and such is worse
here i'm using old sodium with c2me and cuple of othe optimiation mods, 66 render distacne, and the chunks render/generate much quicker than with new wersion of sodium
so it could be sodium-c2me related
Well, about the performance impact of C2ME towards Distant Horizons is that, it slows down Distant Horizons chunk generation speed by 5 to 15%, even with optimized threading setting as per pinned message in #iris-help. One person in Distant Horizons Discord server have done the benchmarks.
66 chunk vanilla render distance? That will cause a HEFTY performance drop