-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New nVidia Driver update causing issues perhaps? #601
Comments
Update, they closed the thread under Sodium's side, stating that Nvidia broke something in the current version of their driver. |
Based on the Sodium issue report here: CaffeineMC/sodium#1486 I'm assuming that nvidia driver versions before |
Had the Same Problem after updateing Nvidia. Just did downgrade again and i can go through portals without crashes again. |
Is it possible to fix this bug? Or wait for a new driver from nvidia ? |
@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. |
@maruohon |
@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'm having this issue with NVIDIA 526.47 and 526.86, but if i downgrade to 522.25 my minecraft stop crash |
@IlIlIlIIlIlIlIl best to downgrade your graphics driver for the moment |
Also occurs when reloading chunks (F3 + A) |
GPU driver version 527.37 |
#Game crashes when using NVIDIA drivers version 526.47 or later #1486 |
seek for CaffeineMC/sodium#1486 (comment) |
@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. |
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: EDIT: EDIT: |
@Scarlaid |
I'm having issues with litematica mod, and I don't know why https://github.com/orgs/FabricMC/discussions/2762#discussioncomment-4419359 |
Deleting the old mod configs from "config" folder in .minecraft solved the issue for me |
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. |
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. |
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. |
I'll get back to you later today, I'm currently at my day job. |
This build fixes that crash: https://masa.dy.fi/mcmods/litematica/litematica-fabric-1.19.2-0.12.6-pre.4.jar |
Would it be possible to get a 1.19 version of the fix? Thanks. |
Thank you masa ;) Readers, please take note of the Open issue with Sodium crashes, in particular (Related issue): |
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
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)
The text was updated successfully, but these errors were encountered: