Weird bug where client/server desynced
I updated from 1.21.1 to 1.21.4 and upgraded my distant horizons mod to
DistantHorizons-fabric-2.3.0-b-dev-1.21.4. After playing singleplayer for a while, I went on a blue ice boat track and while travelling I changed my vanilla render distance (not simulation distance) from 16 to 32 chunks, noticed some holes, and changed it back. Then, after a while, I travelled back across the same track and suddenly my client and server were desynced, and when I quit to title it couldn't finish saving and I had to shut minecraft down. During the desync I placed a shulker, which I no longer have after rejoining the world. The same thing happened when I went back to the same area. I shut minecraft down again, removed the distant horizons mod, and now the game no longer desyncs when I enter that area.
Luckily I had made a backup and only lost a couple hours of progress or my shulker (depending on wether or not I choose to reload from backup) but this seems like it could be devastating
Please let me know what further information to give.15 Replies
Can you replicate it again if you re-add DH? Because this does not sound like something DH could cause
I probably should have made a backup of the world before removing dh because now I can't really test anymore, but I'll try to recreate it anyways
Alright
I can't recreate it anymore
It probably was a one off thing then
I understand it's difficult for you to do anything with this but I still think it's pretty likely an issue with DH because otherwise you would expect it to either not happen a second time or happen a third time
The main reason we can't do anything with this is that there is no way to replicate it, which makes fixing any problem very very hard
yeah I understand
sorry for not making a backup for you guys before removing it
anyways, I found some logs from the first crash:
also here's my mod list:
are the warnings
worrying?
No that's a common warning
Nothing to worry about
As for the hole at vanilla RD 32:
/overdraw
Hole at the edge of vanilla Render Distance, especially during movement:
This is caused by either vanilla terrain not loading in fast enough, or shader's incorrect overdraw prevention implementation or configuration (if you use one)
Some world gen speed improvement can be found when adding these two mods, but the affect will be minor:
- Noisium
- Faster Random
There is another mod that may help:
C2ME. However, it can decrease DH generation speed by up to 35%.
The easiest fix is to move slower and/or ignore it. This hole is most visible while moving over not generated (by vanilla) terrain. Moving over that terrain every subsequent time may not create the hole. And moving slower will give MC more time to load the chunks as you go.
If none of that helped, you can also tune the overdraw prevention, look at the third section to know how.
Low quality full blocks behind and around non-full block, e.g. fences or ladders:
This is intended behavior, to prevent holes in the world while you move, DH will overlap with some part of the vanilla terrain.
How much of the terrain is covered is determined by the overdraw prevention:
- 1.0 will mean DH LODs start where vanilla chunks end.
- 0.0 will mean that DH render everywhere starting from your position.
To fix this, you can either:
- Increase your vanilla RD, which will move the DH LODs further from you.
- Tune the Overdraw Prevention setting, see the next section to know how.
Where to edit the overdraw prevention setting?
Overdraw prevention setting can be edited inside the DH config under:
Advanced > Graphics > Advanced Graphics
But if you use shaders, they will override and take control of the overdraw prevention.
In that case, check the shader's settings, if overdraw prevention is not there, contact the shader devs or change the shader you use.this happened twice again today, both times either while I was exploring or while I backtracked after exploring
(btw I'm not so sure anymore it is DH's fault)
also my minecraft uses about 30 GB whereas in the jvm arguments I allowed 16GB
my bad, it's not DH. It even happened without DH.
alright, good to know