World Chunk Errors on 0.5.3

Question

World Chunk Errors on 0.5.3

dusieq95 opened this issue 3 years ago · 16 comments

dusieq95 commented 3 years ago

Modpack version
0.5.3
Describe the bug
I created world in 0.5.2, vanilla preset and after upgrading world to 0.5.3 i got those chunk errors on new generated chunk's.

Logs

Screenshots

NielsPilgaard · Answer 1 · 2021-07-03T11:18:59.000Z

Oh no >< I'll investigate.

dusieq95 · Answer 2 · 2021-07-03T11:29:40.000Z

Maybe it's caused because i didn't delete configs before updating.

NielsPilgaard · Answer 3 · 2021-07-03T11:34:20.000Z

That wasnt required for 0.5.2 to 0.5.3 :) could you please check if you have the mod BiomeIdFixer?

NielsPilgaard · Answer 4 · 2021-07-03T18:22:07.000Z

Alright, I wasn't able to reproduce this.

Are you on a server?
Did you modify the modpack in any way? Added/deleted mods?

dusieq95 · Answer 5 · 2021-07-03T18:39:10.000Z

Singleplayer

In 0.5.2 i added OptiFine_1.16.5_HD_U_G8
After updating to 0.5.3 i deleted optifine and replaced it with sodium-forge-2.7+rev.168f15b

I will try run old world (0.5.2) with new instance (I could try upload my world but i have rly slow upload speeds and it could took a few hours so)

NielsPilgaard · Answer 6 · 2021-07-03T18:40:16.000Z

I'm about 95% sure Sodium is the reason here :P

dusieq95 · Answer 7 · 2021-07-03T19:15:39.000Z

Yeah, it was caused by Sodium i didn't know that this mod can cause chunk errors, problem solved :)

landretk · Answer 8 · 2021-07-03T19:32:57.000Z

Can it cause chunk errors on servers too or is this a singleplayer thing?

NielsPilgaard · Answer 9 · 2021-07-03T19:33:50.000Z

Probably both. I do not recommend using it.

landretk · Answer 10 · 2021-07-03T20:46:35.000Z

Oof, removing Sodium screwed up new chunks for me. It appears that worldgen is just different with/without it so if you start without it you don't want to add it and if you start with it you want to keep it. Readded Sodium and deleted the incorrect chunks and they generated correctly with it back in.

dusieq95 · Answer 11 · 2021-07-03T13:27:17.000Z

Yeah, i have this mod biomeidfixer-1.16.5-1.0.1.s4

NielsPilgaard · Answer 12 · 2021-07-03T14:38:28.000Z

Damn :P did you install 0.5.3 as a new instance and moved your files?

dusieq95 · Answer 13 · 2021-07-03T15:14:29.000Z

I just updated the pack through CurseForge and i didn't move any files, probably that's why i got those errors ( ｡_｡)

NielsPilgaard · Answer 14 · 2021-07-03T15:49:54.000Z

Nah you did exactly what you should have done :) I'll try to find the cause.

Erysch · Answer 15 · 2021-07-04T15:13:11.000Z

Probably both. I do not recommend using it.

My old secondary pc doesn't like to hear that :'(

Erysch · Answer 16 · 2021-07-04T15:18:09.000Z

Oof, removing Sodium screwed up new chunks for me. It appears that worldgen is just different with/without it so if you start without it you don't want to add it and if you start with it you want to keep it. Readded Sodium and deleted the incorrect chunks and they generated correctly with it back in.

You should still be able to use it without problems when the server is rendering the world and not your client.

Share to