Litematica

Litematica

8M Downloads

New nVidia Driver update causing issues perhaps?

sakura-ryoko opened this issue · 31 comments

commented

So, Litematica/Sodium has been working fine for quite some time, and I didnt even update the MOD or anything too recently, but this happens whenever I try joining a specific SMP server. It worked fine the night before, and I even just finished using Litematica on the same server. I tried going through and updating Fabric API and all of my other mods to no avail.

Maybe its a PaperMC / Pufferfish+ thing that they might have changed in the server settings recently also?

Removing Either Sodium or Litematica (But not having both) fixes the crash.

(Nvidia Driver 526.47)

MC: 1.19.2
Fabric API: 0.64.0
Mod menu: 4.0.6
Lithium: 0.10.0
Phosphor: 0.8.1

  • Sodium: 0.4.4.build18
  • Malib: 0.13.0
  • Litematica: 0.12.3- 0.12.5 tested

Other MODs, but without them I can still reproduce the error:
MiniHUD: 0.23.3
Tweakroo: 0.14.3
Itemscroller: 0.17.1
Xareo's Minimap: 22.16.0
Xareo's World Map: 1.28.1
Advanced Compass: 1.2.12

I've also been able to reproduce the error trying to edit the Sodium render distance while on the server = crash.

Crash Report Added:
snipped.log

Sodium Crash report link:
CaffeineMC/sodium#1491

(masa: snipped some stuff from the log that shouldn't be shared publicly)

commented

Update, they closed the thread under Sodium's side, stating that Nvidia broke something in the current version of their driver.

commented

Based on the Sodium issue report here: CaffeineMC/sodium#1486

I'm assuming that nvidia driver versions before 526.47 would not have this issue? Can someone test and confirm that?

commented

@maruohon
It's very unfortunate that this error has appeared.
These are the last logs I have before close the game:
log

commented

@Hellw0rker There isn't really anything I can change in the mod, AFAIK. I don't even know what/why/how exactly causes the crash all of a sudden.

commented

Based on the Sodium issue report here: CaffeineMC/sodium-fabric#1486

I'm assuming that nvidia driver versions before 526.47 would not have this issue? Can someone test and confirm that?

Had the Same Problem after updateing Nvidia. Just did downgrade again and i can go through portals without crashes again.

commented

Is it possible to fix this bug? Or wait for a new driver from nvidia ?

commented

@Hellw0rker try installing an older driver of nvidia. That worked for me. https://www.nvidia.de/Download/driverResults.aspx/193750/de I installed version 522.25 works fine for me again.

commented

I'm having this issue with NVIDIA 526.47 and 526.86, but if i downgrade to 522.25 my minecraft stop crash

commented

image
crashing with newest driver too (only when using sodium with litematica)

commented

@IlIlIlIIlIlIlIl best to downgrade your graphics driver for the moment

commented

GPU driver version 527.37
Minecraft 19.2
Hi I have a problem when I enter the nether portal the game crash with exit cod 1
temporally fix for it remove Litematica mod or sodium.
I think the problem happened when Nvidia updated the drivers they changed something that made sodium and Litematica crash. it is maybe something between the 2 mods is broken.
this problem can be fixed if @jellysquid3 and @maruohon looked into it together and see what went wrong

commented

#Game crashes when using NVIDIA drivers version 526.47 or later #1486
check this Issue on sodium GitHub to get more info

commented

Also occurs when reloading chunks (F3 + A)

commented

image

Still crashes

commented

I'm having issues with litematica mod, and I don't know why
If anyone can help, please respond to me at

https://github.com/orgs/FabricMC/discussions/2762#discussioncomment-4419359

commented

seek for CaffeineMC/sodium#1486 (comment)
It's might be the waiting game for now on

commented

@maruohon -- You can probably close this thread, and reference the Sodium issue; because from what I'm being told, it's specifically an issue with Sodium / Nvidia drivers. The snafu with Litematica + Sodium might be a non-issue.

See the link above.

commented

I know thread is closed, but it continues to crash on latest drivers still
image

commented

Jelly has released a new version of Sodium for 1.19.3 that simply changes the title for Minecraft. It fixes the issue with litematica! Download Here of Sodium.

EDIT:
Newer more stable versions are coming out, so just wait to see what is pushed properly

EDIT:
Updated link

EDIT:
DONT USE THE LINK

commented

Just change your Minecraft window title to something else beside Minecraft* (version) (which by default indicate the game was modded, vanilla should show Minecraft (version)) and you should be good
image

commented

@Scarlaid
I can't find the right file to edit.
Please help me.

commented

Deleting the old mod configs from "config" folder in .minecraft solved the issue for me

commented

@Hellw0rker try installing an older driver of Nvidia. That worked for me. https://www.nvidia.de/Download/driverResults.aspx/193750/de I installed version 522.25 works fine for me again.

I'll Re-Open this thread until the Developers confirm the issue has been FULLY resolved with the Nvidia drivers. As quoted, your best course of action is to downgrade your Nvidia drivers to 522.25 if you wish to use both mods without any issues under 1.19.2. I have not tested this issue with 1.19.3 yet because the server I play on, is still using 1.19.2.

commented

Deleting the old mod configs from "config" folder in .minecraft solved the issue for me

I've tried this also, as part of my Original troubleshooting steps, I deleted all MOD configs, and completely reloaded Fabric from Vanilla after purging my .minecraft directory, and slowly re-introducing my saved worlds, etc into the folder.

commented

Can anyone/everyone here test this version and see if it fixes the crash?

https://masa.dy.fi/mcmods/litematica/litematica-fabric-1.19.2-0.12.6-pre.3.jar

I rewrote some parts of the renderer after it was pointed out that the problem at least for the AMD driver related crash was the number of different VBO buffers that the mod created. Those are now created lazily and not always allocated for the entire view distance, and also the chunks are not split to 16-high sections anymore for rendering.

commented

Can anyone/everyone here test this version and see if it fixes the crash?

I'll get back to you later today, I'm currently at my day job.

commented

@maruohon

HOORAY! Problem solved. Game crash is not observed.
Снимок экрана 2022-12-21 213031

commented

@maruohon

HOORAY! Problem solved. Game crash is not observed. Снимок экрана 2022-12-21 213031

image

crash.txt

Stand down, it's not all good.
When you turn off the circuit, the game crashes. When you turn it on, everything is fine.

commented

Would it be possible to get a 1.19 version of the fix? Thanks.

commented

Thank you masa ;)

Readers, please take note of the Open issue with Sodium crashes, in particular (Related issue):
CaffeineMC/sodium#1486