2.3.5 performance seems much worse than 2.3.4

Running this on Fabric 1.20.1, and the new version has constant really bad stutters that last a couple seconds, and on starting a world the 'loading terrain' step takes around 2 mins compared to only needing a few seconds on 2.3.4 https://mclo.gs/1hbBC4U I am running a big modlist, but it seemed to run just fine before this update.
mclo.gs
Fabric 1.20.1 Client Log [#1hbBC4U]
15299 lines | 845 errors
9 Replies
Puhpine
Puhpine2w ago
Did you change the allocated ran amount?
Miki_P98
Miki_P982w ago
Maybe try disabling biome blending
Dexter307
Dexter307OP2w ago
I have 8 gigs allocated to Minecraft, do I have to give DH its own ram? I’ll give this a try next chance I have and I’ll report back Just gave that a try, unfortunately there was no change. I even tried disabling DH rendering and distant generator entirely but I still get these issues trying to run 2.3.5
Dexter307
Dexter307OP2w ago
The stutter looks like this with rendering and distant generation off, seems to happen anytime chunks are generated, its like DH is getting really mad anytime the game tries to load or generate chunks.
Skillnoob_
Skillnoob_2w ago
try the nightly #links-n-downloads
Dexter307
Dexter307OP2w ago
Yeah I just gave it a try and it fixes it, looks like it was the same issue. Thanks.
Graph3ne
Graph3ne2w ago
Just adding to this that 2.3.5-b is unplayable. I changed no other settings and just updated from 2.3.4-b to 2.3.5.-b. I have a Ryzen 9 5900x and Nvidia 3080. 16GB RAM allocated. MC says that the GPU is hitting 100% use every time a new chunk is loaded. Task manager says otherwise. I have the LOD set to 256 and the preset on high (unchanged between versions). I also have it set to minimal impact, which clearly 2.3.5-b does not understand
Dexter307
Dexter307OP2w ago
Use the dev build or go back to 2.3.4, this was fixed in the nightly build for 2.3.6, but yeah 2.3.5 is unusable.

Did you find this page helpful?