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.
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.
latest.log30.42KB
Was this page helpful?
