Instant crash when attempting to load a world.
MC version 1.20.1, DH mod version 2.2.1, I've attempted with Fabric, Force, vanilla launcher, ATlauncher, and nothing has worked. I've followed the steps on the #faq-problems-and-fixes to no avail.
To confirm, I've:
- attempted to load into a world with Distant Horizons as the only mod.
- attempted to load into a world using Forge on ATlauncher with only DH mod installed.
- attempted to load into a world using Forge on ATlauncher with DH mod, Oculus, and Embeddium, with and without shaders enabled.
- attempted to load into a world using Fabric on the vanilla launcher.
- attempted to load into a world using Fabric on the vanilla launcher with Iris, Indium, Sodium, and Fabric API installed, with and without shaders enabled.
- Deleted the DistantHorizons.toml file in my install's config folder, for each instance mentioned above
I click on a world, it gets as far as saying "0%," and then it crashes.
The only error code given when the crash occurs is usually "Exit Code -1," although on rare occasions I get a tick error of some kind. Unfortunately I haven't been able to get that error to appear again to copy and paste it.
Logs and crash reports are attached.
(Logs and reports are from an attempt at loading into a world using Fabric, the vanilla launcher, Iris, Sodium, Indium, and Fabric API.)
PC Specs:
- RTX 2070 Super
- Ryzen 7 3700X
- 32GB DDR4
- Minecraft instance is running on an M.2 NVMe SSD
The complete non-functioning across both Fabric and Forge, vanilla and ATlauncher leads me to believe the problem lies with something else. I'd love to get it working in my custom Forge modpack!
Thanks for the help.
34 Replies
is this with a specific world or does it also happen in a new world?
java.lang.RuntimeException: java.sql.SQLException: Unable to get repo with connection string [jdbc:sqlite:C:\Users\xxxxx__Desktop\testmc\saves\New World\data\DistantHorizons.sqlite]
Caused by: java.sql.SQLException: Unable to get repo with connection string [jdbc:sqlite:C:\Users\xxxxx__Desktop\testmc\saves\New World\data\DistantHorizons.sqlite]
It happens either way.
can you try with the nightly builds from #links-n-downloads
Are you on Windows?
I can. Give me a bit, I've decided to take a break from it for now, as I've been messing with it for a while.
Windows 10, yes
When you were testing on new world did you name every world the same?
A.K.A.
New World
Does this path and file exist:
C:\Users\xxxxx\Desktop\testmc\saves\New World\data\DistantHorizons.sqlite-# xxxxx is your username censored to not trigger the censor bot If so try deliting it
I didn't change the names for each New World but I did delete DistantHorizons.sqlite, but I will try again just for sanity, and also generate a new world with a different name.
Maybe try a name without spaces though that should not matter
Attempted to generate a ne world titled "test1" and immediately got a crash on 0% just as before.
With nightly or stable?
That was with stable, trying nightly now
Tried with Nightly and the game won't launch at all, doesn't even get to the Mojang loading screen.
Happens the same with or without Iris, Sodium, Fabric API, etc.
The reason for the crahs seems teh same, now it just tells you that at the start and with more detail
java.lang.RuntimeException: Could not execute entrypoint stage 'client' due to errors, provided by 'distanthorizons' at 'com.seibel.distanthorizons.fabric.FabricMain'!
Caused by: java.lang.RuntimeException: dh_sqlite.NativeLibraryNotFoundException: No native library found for os.name=Windows, os.arch=x86_64, paths=[/dh_sqlite/native/Windows/x86_64;\AppData\Roaming.minecraft\bin\d4beea1801cd73a795cf5122e7525084abd6fed1]IDK what to do next though... @Puhpine (GMT +2) any ideas?
Yeah, I'm not sure what most of that means. I'm a nerd but I don't know much about Java Runtime Exceptions
never seen this before
so no idea
SQLite drivers seem to be missing
But IDK how that happened
@Savage What JDK are you using?
Oracle? Adoptium? Zulu?
And what version? 17? 21? 23?

Can you search by
JDK
?
And JRE
neither actually comes up at all, at least not under installed programs. I don't know if it would come up there at all though, or how else I'd check
So I guess that will be Oracle version 22
Command prompt returns the same as my list of installed programs

Last think I can think of right now is to try change the JDK
Maybe try Zulu version 23
Azul | Better Java Performance, Superior Java Support
Azul Downloads
should I uninstall v22 first to avoid conflicts or should it not matter?
You will then have to change the JDK version used by the MC launcher
Should not matter, during install you can check the box to set JAVA_HOME variable
That will result in less issues if any would to appear
Alright, it's installed, how do I tell the vanilla launcher to use it?
Okay, I went to the Fabric installation and told it to use the Java executable "C:\Program Files\Zulu\zulu-23\bin\javaw.exe" and tried to launch the game. With the nightly build, it still crashes immediately on launch, and on the stable build, it still crashes when I try to load/create a world. Let me get logs and reports for you.
Okay, I think I might actually have kindof fixed it... by running Minecraft as an administrator...?
I should say, it runs now without crashing, but I don't notice a difference yet while playing. I suppose I just need to walk around and load some chunks.
I believe that running MC as an admin has fixed everything or it could've been doing Zulu version 23, at least it seems to be running fine. Although as stated, it definitely is pushing my hardware to its limits.
I'll have to ask around what settings others are using, especially with Forge and Embeddium.
thanks guys for your help!
weird, but glad you fixed it!
Now I just need to optimize. Never thought my 2070 would be inadequate for Minecraft... Thanks again!