Possible Soft-lock Via too many items.

[MonkeyManRogue]

I chopped down a tree that was maybe a bit too large. After turning some wood into firewood for charcoal, my game crashed. I loaded it back up, and crashed again almost instantly after turning down major graphical settings. Any help is appreciated since I don't have a recent world backup and I'm hosting LAN for others.

Running on 64 bit Windows 10.0.19045.0 with 16311 MB RAM
Game Version: v1.20.4 (Stable)
3/15/2025 7:24:30 PM: Critical error occurred
Loaded Mods: chiseltools@1.12.11, extrachests@1.9.0, HangingOilLamps@1.0.1, moretreesmoreseeds@1.0.0, nailsmold@1.0.2, NoNegativeTraits@1.0.1, primitivesurvival@3.7.5, tprunes@1.1.1, temporal_gears_stack@1.0.0, game@1.20.4, zoombuttonreborn@1.6.0, additionalmolds@1.0.1, carryon@1.8.0-pre.1, commonlib@2.6.1, easyprospect@1.0.0, fishing@1.1.5, hudclockpatch@1.0.0, prospecttogether@1.4.0, creative@1.20.4, survival@1.20.4, helvehammerext@1.7.0
System.NullReferenceException: Object reference not set to an instance of an object.
   at Vintagestory.GameContent.EntityItemRenderer.DoRender3DOpaque(Single dt, Boolean isShadowPass) in VSEssentials\EntityRenderer\EntityItemRenderer.cs:line 117
   at Vintagestory.Client.NoObf.SystemRenderEntities.OnRenderFrameShadows(Single dt) in VintagestoryLib\Client\Systems\Render\RenderEntities.cs:line 174
   at Vintagestory.Client.NoObf.ClientEventManager.TriggerRenderStage(EnumRenderStage stage, Single dt) in VintagestoryLib\Client\Util\ClientEventManager.cs:line 188
   at Vintagestory.Client.NoObf.ClientMain.MainRenderLoop(Single dt) in VintagestoryLib\Client\ClientMain.cs:line 825
   at Vintagestory.Client.GuiScreenRunningGame.RenderToPrimary(Single dt) in VintagestoryLib\Client\MainMenu\Screens\GuiScreenRunningGame.cs:line 161
   at Vintagestory.Client.ScreenManager.Render(Single dt) in VintagestoryLib\Client\ScreenManager.cs:line 695
   at Vintagestory.Client.ScreenManager.OnNewFrame(Single dt) in VintagestoryLib\Client\ScreenManager.cs:line 670
   at Vintagestory.Client.NoObf.ClientPlatformWindows.window_RenderFrame(FrameEventArgs e) in VintagestoryLib\Client\ClientPlatform\GameWindow.cs:line 88
   at OpenTK.Windowing.Desktop.GameWindow.Run()
   at Vintagestory.Client.ClientProgram.Start(ClientProgramArgs args, String[] rawArgs) in VintagestoryLib\Client\ClientProgram.cs:line 334
   at Vintagestory.Client.ClientProgram.<>c__DisplayClass10_0.<.ctor>b__1() in VintagestoryLib\Client\ClientProgram.cs:line 130
   at Vintagestory.ClientNative.CrashReporter.Start(ThreadStart start) in VintagestoryLib\Client\ClientPlatform\ClientNative\CrashReporter.cs:line 93

Event Log entries for Vintagestory.exe, the latest 1
==================================
{ TimeGenerated = 3/15/2025 7:23:22 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.4.0, time stamp: 0x66470000
Faulting module name: openal32.dll, version: 1.23.0.0, time stamp: 0x63dd31ad
Exception code: 0x40000015
Fault offset: 0x00000000000df046
Faulting process id: 0x1754
Faulting application start time: 0x01db961a4adcc0a6
Faulting application path: C:\Users\b\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Users\b\AppData\Roaming\Vintagestory\Lib\openal32.dll
Report Id: ea65f454-6029-45e9-a556-84119652a5c1
Faulting package full name: 
Faulting package-relative application ID:  }

[Thorfinn]

That's a very similar render error to the one someone posted yesterday that he ran into exploring a BetterRuins structure.

This is a little disturbing in that you are running 1.20.4. @Maelstrom reported that he rolled back to something like 1.20.1 and that resolved his issue. Offhand, I don't see any mods that I would suspect might throw that kind of an error, but then again, I don't use anywhere near that many mods.

If I were to take a guess, since it appears to be some error thrown in rendering shadows, it might have something to do with the shadows and helve hammer error the team has already isolated. I think I'd try shutting off shadows, and if that doesn't work, disable your helve hammer mod and try that.

[EDIT]

Next, disable any nearby helve hammers, like by removing a single axle section. Again, I don't know. Not an error I've run into. Just what I'd do to isolate it, knowing what I've read in patch notes and know from modding.

Welcome to the forums, BTW, @MonkeyManRogue

 

Edited March 16, 2025 by Thorfinn