Crashing when trying to self attune
Rerver88 opened this issue ยท 13 comments
I'm playing the medieval minecraft modpack by SharkieFPS. Note that astral sorcery is something I personally added myself and isn't part of the pack normally. I just created an attunement altar and set it to... vicio?(the 'motion' one), anyway it crashes when I try to stand on it. The game didn't generate a crashlog, so here's the regular log: latest.log
Guys, it is by far more worse:
https://drive.google.com/file/d/1exKm3SKiEy8qiiqgq679eruHRxXNIw6Q/view?usp=sharing
(the performance of the video is worse, yes, but you can see the black screen parts)
Just look at the video behind the link, the attunement table is 100% buggy, the cam is totally weird and no progress to the attunement.
I play a self created 100 mods pack on a server.
(no Optifine / OptiForge)
Not remotely the same issue (so you shouldn't have placed it under this ticket), and doesn't occur with only AS.
Some other mod is conflicting with the camera controls. A list of mods would be needed, but this is better handled in the Discord, not here.
That said, if Agricraft is in your list, that's the issue since it's a bug with the needed InfinityLib, which has a fix but it doesn't appear to be pushed with an update yet: AgriCraft/AgriCraft#1408
Yes, Agri is installed and good to know that this is fixed already.
And sry for posting it here, I just saw "attunement" and "all in" :D
I am currently not on your DC.
outside of a bunch of recipe errors when shutting down, and a tone of null errors from ASM patches from various mods, I don't see any crash cause. Without a crash log of some sort, nothing can be done, because the cause cannot be determined.
dang, is there any way to make the game generate a crash log somehow? Also, what are recipe errors and null errors from ASM patches?
Here's a new log: latest.log which seems different from the last one. Not sure if it'll be helpful though, I don't have high hopes at this point.
Yeah, I was just figuring that out. Welp, I just installed the latest version of java and got Minecraft to actually use it by adding a command line argument to curseforge's Minecraft settings, but it doesn't seem to have helped. It still crashes, and still refuses to generate an actual crashlog. sighs Well, I've pretty much given up here. If nothing else, thanks for pointing out that my Minecraft wasn't actually using the latest version of java, I never would have figured that out myself. Thank you all for being so helpful. Unless there are any other suggestions, please feel free to close this issue thread if you want.
If there's no crash log, MC isn't what's crashing, it's Java instead, or something else is sending a shutdown signal. Your latest.logs look like a "clean" MC shutdown with server thread stoppages, etc.
I would recommend trying updating your Java, looks like you're still launching with 1.8.0u51, which is pretty old. Try updating to a Java8 that's u300 or higher, and making sure your launcher uses that instead of the u51 that's built-in.
That's strange, "settings" -> "apps" tells me that the version of java I have installed is "Java 8 Update 251". So unless you missed a number and meant to type u251 then something is very wrong. Well, installing the latest version is a good suggestion anyway so I'll try that first.