37 Replies
First try updating to DH 2.3.1+ (nightly as it has many bug fixes)
I don’t see anything DH related in the logs though
Does it happen with DH as the only mod?
https://discord.com/channels/881614130614767666/882038774861819954/1302316023780999238 here?
well i mostly ask help related to not just to dh
lemme remove dh and see
it crashes without dh
aswell
Send new logs with DH 2.3.1+ or without DH
And include the crash report if one generates
If no crash report generates I don’t think anyone will be able to deduce the issue
latest log and crash report?
So you might need to do a /binary search
Try a binary search and figure out which mod is causing it.
So disable half of the mods, see if issue is still there, if yes disable half again etc etc until you find the mod that's causing the issue.
Yes
heck no
not with 120 mods
With 120 mods binary search should take around 7 iterations
There is an error from physics mod and couple from corrupted jsons
Try removing physics mod and deleting the whole config folder (maybe even every other json you can find in the game files)
it didnt work without physics mod too
I did it before with 300+ mods, a binary search doesn't take long
Here Exordium seems to be the reason for the error
Try removing it
i wonder why
the game freezed now
but doesnt crash
oh
it launched
but it took sooooo long
but i think i actually played well with exordium, i added a couple of mods today, and it stopped working
thank you for your help
Not compatible - VulkanMod - MiniHUD(bug on their side, the fps counter shows the gui fps instead of the world fps) - Canvas - Fast Crosshair will not work with ImmediatelyFast, just keep it off - In BetterF3 disable the slide in Animation or Debug screen buffering - Many other mods that render their own GUI elements, the wilder the mod, the more likely it is to not work with this mod. No point in reporting this, Exordium is for the Vanilla UI onlyThis is from Exordium mod page. You have Appleskin and Xaeros that have GUI changes and maybe more mods. This 2 and other have great chance of conflicting with Exordium
Oh, for the vanilla UI only? weird though, it worked perfectly fine with essential mod
From my experience it is random if it will or won’t work
also on the mondrith app, the exordium mod desripction doesnt have that line "Many other mods that render their own GUI elements, the wilder the mod, the more likely it is to not work with this mod. No point in reporting this, Exordium is for the Vanilla UI only"
huh
my dumass downloaded that mod, it's not even made for 1.21
It is present on Modrinth website at least: https://modrinth.com/mod/exordium
nevermind, i just didnt read the last line 😭
i am sorry for that
No problem
but also i wonder how did it even launch previously, this mod isnt for 1.21
It has 1.21 versions: https://modrinth.com/mod/exordium/versions?g=1.21
i meant 1.21.1
mb
1.21.1 and 1.21 are the same
they'ren ot
Every 1.21 mod will work for 1.21.1
oh
well it doesnt change the fact exordium crashed
Yes, except one crash fix
what is this ?
i think it should have different colour
same as the wate
nah, that was the fog
fixed
/overdraw
Q: There are holes at the edge of vanilla Render Distance, especially during movement
A: 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 three mods, but the affect will be minor:
- Noisium
- Faster Random
- C2ME (DH 2.3.0+)
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.
Q: There are low quality full blocks behind and around non-full block, e.g. fences or ladders
A: 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.1 will mean that DH render very close to the players position.
0.0 sets it on auto mode.
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.
Q: Where do I edit the overdraw prevention setting?
A: Overdraw prevention setting can be edited inside the DH config under:
Advanced > Graphics > Quality
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.
The ring is from fading
Setting fading to single pass will get rid of it but has other drawbacks
it was the fog