Crash with just Iris and Sodium
I am only using Iris and Sodium of course, and on 1.18.2. tried with many other shaders, and no shaders, and still crashing. No crashlog is produced. just a Latest.log
58 Replies
lines 176-213 say they removed something from somewhere
:conc:
Thats wierd
What should happen?
well i just know it should not crash :ioa:
and no instance of mine ever had that :conc:
smarter people are yet to figure out the issue :thinkies:
heres another log
But with oculus and rubidium
And so it happens for both
What the hell could be happening
I have a RTX 3070 btw and a ryzen 7
heres another log
After some digging No crash logs are produced neither
Which is incredibly strange too.
The exit code is also -1073741819
God this is strange
well I can say the messages about removing stuff from the shader code are normal, that's just the compatibility patcher announcing that it's doing things. It's probably unrelated to your crash
try starting the game without a shaderpack selected
oh you said you've tried it with no shaders
well I can't see anything problematic in your game logs. and if no crash log is produced then idk what the problem is
What would you reccomend to do
wait for somebody who knows what is going on :ioa:
Ty
I think this is that widespread NVIDIA driver bug that's affecting many old versions of Sodium https://github.com/CaffeineMC/sodium-fabric/issues/1486
GitHub
Game crashes when using NVIDIA drivers version 526.47 or later · Is...
MODERATOR EDIT NVIDIA drivers (version 526.47) are known to cause crashes with Sodium. We are applying a workaround to get around this problem, by tricking the drivers on what version of the game i...
ah yes the crongification strikes again
try using a more recent version of sodium (which means you'll also need to use a more recent version of Minecraft)
alternatively, I don't know a way to do this off the top of my head but if you can find a mod to change the window title (so that you can remove the "1.18.2" version number from the title) would also likely fix the crash
:ioa:
How come?
That seems oddly specific
Plus iv been doing this to make the Dawncraft modpack work, and that has a custom title
Im more than happy to rollback my drivers though, but unsure which one to use
The NVIDIA driver applies custom optimizations to Minecraft when it detects newer versions, and some newly-added optimizations are known to break Sodium and other rendering mods, which means that to fix the crashes you have to make it fail to detect that a newer version of Minecraft is running
It's possible this is a different issue but the above linked NVIDIA issue has largely been responsible for all of the "game crashes out of nowhere with no clear cause or stacktrace when running with Sodium / etc" issues I've seen reported recently
Incasw that doesnt work, which driver would you want me to roll back to?
not sure but I'd try any driver before 526.47
Thank you, ill update this in the morning
Got NVIDIA 522.25 driver, got this as a latest.log
also @coderbot . what should i change the window title to?
Played dawncraft modpack.. which changed the window title and no crashing so far
Any window title will do as long as it's not a normal title with a version number
Still crashing.. With Seus PTGI And Seus Renewed
And many other shaders
Found a fix!
mixin.workarounds=false
This fixes it!
@douira this is 1000% the fix.. wierd as shit
managed to play for hours
no crash just my server crashed because not enough ram lmfao
interesting
@munt
before you go
can you check
.minecraft for a file named his_pid_xxxx.log?Sure.
(xxxx being any number)
Whys that?
those files are crash reports
but not minecraft crash reports, JVM crash reports
for when the game is so catastrophically broken that Java cannot continue running at all
Alright. no worries.. letme do some digging
👍
just so you know, they do contain partially personal info
(notably, your access token, which gives temporary access to your MC account)
Alright.. ill try and blurr it
you can remove it by just searching for
accessToken and deleting the lines with itThanks
Im using curseforge.. so would the JVM crash reports be there?
they'd be whereever curseforge considers .minecraft to be, I'm not sure
let me see
actually, just find whereever you go to find normal crash reports
and go one folder up
that's where it should be
This all i got pal.
so it would be in
rt, not in rt/logsAhhh understood
weird
Very strange isnt it?
it should be practically impossible for a crash to happen without a JVM crash report
Though.. i could see if the Dawncraft has any crash reports?
Dawncraft modpack was the reason i tried to get this working.. though that IS rubidium
Nope. not even dawncraft directory has it
(I am running java 18 by the emporium thing or however you spell it)
if you dont change the launcher options it should use whatever version of java the launcher thinks is best for that version
Yeah i set it to java 18 bc its required for dawncrat
dawncraft*
u sure it's not java 17 ?
@Watermelonn what makes you say that?
minecraft 1.17+ is made for java 17
Thats what it tells me to do
just test with 17 in case it's caused by that
Now its crashing more in multiplayer.. What on earth
What the actual fuck. woke up this morning and its not working anymore