#"Random" crash
1 messages · Page 1 of 1 (latest)
Can you upload the log itself? The bot will take care of it cause the website you used doesn't work
@urban scaffold
I gave last axiom 3.1.0
we need logs to see what happening
the latest.log when you can't use the tools
Oh
again with that website
Ok
upload the log itself
5 min
Hello, sorry for the long absence, I could not cause a crash in any way, and when I turned on the downloaded shaders, everything became partially clear, here is the text file (I started to turn on the features and immediately flew out + if with shaders it is possible to break the blog at a decent distance, then the crash has the appearance of a black screen and you have to turn it off through the task manager
@urban scaffold uploaded a log,
- OpenJDK 64-Bit Server VM, version 21.0.3
- Fabric 0.15.11 on 1.20.6 with 10 mods
Recommendations: - Unless you know what you're doing, modifying your JVM args could have unintended side effects. It's best to use the defaults.
Remove notenoughcrashes, its ruining the crash report
Again, put the log as is, that website you think it's not for sharing logs
Please change me, but I'd better chew, I'm actually in Minecraft for the first time.
all good
just send the log
this is bad log?
Or this is not log?
send the file itself
the link is not working
@urban scaffold uploaded a log,
- OpenJDK 64-Bit Server VM, version 21.0.3
- Fabric 0.15.11 on 1.20.6 with 10 mods
Recommendations: - Unless you know what you're doing, modifying your JVM args could have unintended side effects. It's best to use the defaults.
yeah all good
is this the latest crash.log?
1.28.35v yes yhis last
alr now we wait
bc I cant read crash logs that good either
No problem :D
@urban scaffold uploaded a log, I uploaded a file for a fresh one
- OpenJDK 64-Bit Server VM, version 21.0.3
- Fabric 0.15.11 on 1.20.6 with 10 mods
Recommendations: - Unless you know what you're doing, modifying your JVM args could have unintended side effects. It's best to use the defaults.
Not an Axiom issue