Open lartts opened 1 year ago
I encountered a similar crash today. It turns out the displayed error has nothing to do with the crash; in fact, removing Oculus/Rubidium temporarily reveals the underlying cause (for me it was kotlinforforge
being out of date). For some reason, the crash log is not referring to the correct cause of crash. I recall having this issue earlier when using the mod "Not Enough Crashes" (because, if my memory serves me right, it tries to be smart and stops the loading process in case of uncaught exceptions), but it seems this happens now even without that mod (I suspect this is actually a forge issue).
I have this same issue, but its for ViveCraft, the log looks similar lol
Much like the MUI situation, and one can only view the full log to get the real cause of the crash.
Hey, I think I found a solution for you. This issue happened to me many times this week, and I was finally able to fix it. The latest version of Oculus is the issue. I changed to the version previous to the current one, and everything worked fine. If this doesnt work for you, I dunno what to tell you- but this worked for me, so maybe try it?
I ran with similar issue crasher with same and latest version of Oculus. But I removed it simply by incompatible deleting incompatible mod 'WorldEdit Express Keybinding' (so unexpected huh). Shall try to find mod imcompatibility.
Minecraft Version
1.18.2
Oculus Version
oculus-1.5.2.jar
Sodium Version
rubidium-0.5.5.jar
Operating System
Windows 10
What is your GPU?
Nvidia GeForce GT 1030
Java Version
Java 16
Reproduction Steps
Crash Report file and latest.log
Additional context
No response