Exit Code: -1073741819
Rooted around here for past issues surrounding this exit code.
Minecraft is able to get all the way in the load process to right before bringing me to the main menu and then crashes.
Prior instances seem to indicate this was an AMD issue (6700xt on this system).
Followed instructions for using the up-to-date Oculus (1.7.10) mod, used a 2.2.1 version of DH.
I couldn't find any mentions of a fix of this outside of migrating to an NVidia GPU. Have isolated it to DH itself as DH is the only .jar file that consistently produces this error.
No big deal if there's no solution.
15 Replies
Exit codes don't tell much. A log would be much more helpful
/logstored
You should send your
latest.log file to provide additional useful information.
Logs are usually located in the .minecraft/logs directory.
On Windows: %appdata%\.minecraft\logs
On Linux: ~/.minecraft/logs
On Mac: ~/Library/Application Support/minecraft/logs
Please upload the file to mclo.gs instead of sending the raw file. This makes reading the contents of the file a lot easier and improves the chances of you getting the help needed.
After uploading the file, click on Save and send the link.Also, are you sure you're using Oculus 1.7.10? I don't think that version exists
the mod version is 1.7.10, but for 1.20.1
There's a lot of errors in there but most of them are from supplementaries and are there every time the game launches without issue
It's quite a large modpack so it's not surprising if something in there doesn't want to play nice.
In the event its a minor fix I'm overlooking; great.
If its not going to work; not a huge deal
Thats Oculus 1.7.0, not 1.7.10
/oculus
Oculus may work, but can produce unexpected results, it is preffered to use Iris on Fabric or Neoforge instead.
To use oculus with DH, it is only possible to use minecraft 1.20.1 with forge. Oculus 1.7 is the only officially released version of Oculus that works with DH, and only works with DH 2.1.x. If you are using DH 2.2.x with Oculus 1.7, that is the reason for your crash.
For DH 2.2.x, the only option is to use an unreleased version of Oculus found at https://github.com/Asek3/Oculus/actions/runs/11198312573/artifacts/2020008921 (you need to be logged in or it will 404). Unzip the given file, take
oculus-mc1.20.1-1.7.0.jar. and put it in your mods folder.
For DH 2.3, you need the unreleased version mentioned above, and edit it to make it work with DH 2.3:
- unzip the mod .jar
- go inside the META folder
- edit mods.toml to say it is Oculus 1.8.0
- save the file and zip the mod file back (zip the files and not the folder)I have MC version 1.7.10 burned into my mind - but that is the 1.7.0 from the github
I have the unreleased oculus version and was using 2.2.1 for DH
I looked through prior help threads that mentioned oculus and followed the steps outlined in the oculus command, this happened after doing those steps.
You're the third person the GitHub Oculus version stopped working for
I don't know how it is even possible
Probably a good chance we're all AMD GPU users. Its not unusual to have them sidelined :amd:
Maybe one day we'll see Vulkanium to mirror the Nvidium mod someone made but until that day we wait 🫡
I can mark this closed if you want - there may not be a solution just yet
There is actually great progress on that. Nvidium support should arrive in a not too distant driver update
GitHub
mesh shader support? · Issue #4 · GPUOpen-Drivers/AMD-Gfx-Drivers
When can we expect OpenGL mesh shader support?