Jump to content

Tyrant50187

Vintarian
  • Posts

    2
  • Joined

  • Last visited

Tyrant50187's Achievements

Wolf Bait

Wolf Bait (1/9)

0

Reputation

  1. Well I’m unsure what you mean by binary search, but I tried disabling all mods, changed the game update version and tried adjust what mods were active..
  2. i have mods enabled but i started getting an error that seems to pertain to Vintage story Directly. all I can do is supply the Error/crash log. Sadly, I am noy very tech savvy, Any suggestions? ystem.Collections.Generic.KeyNotFoundException: The given key 'fogSphereQuantity' was not present in the dictionary. at Vintagestory.Client.NoObf.ShaderProgramBase.Use() in VintagestoryLib\Client\ClientPlatform\ShaderProgramBase.cs:line 420 at Vintagestory.Client.GuiCompositeMainMenuLeft.Render(Single dt, Int64 ellapsedMs, Boolean mainMenuVisible, Boolean onlyBackground) in VintagestoryLib\Client\MainMenu\Composite\GuiCompositeMainMenuLeft.cs:line 384 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 3 ================================== { TimeGenerated = 4/23/2025 6:59:57 AM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.9.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: 0x0x36e4 Faulting application start time: 0x0x1dbb43e7a7077d3 Faulting application path: C:\Users\Usere\AppData\Roaming\Vintagestory\Vintagestory.exe Faulting module path: C:\Users\Usere\AppData\Roaming\Vintagestory\Lib\openal32.dll Report Id: b0fa050e-164e-4a3b-af93-e6a67c4b8309 Faulting package full name: Faulting package-relative application ID: } -------------- { TimeGenerated = 4/23/2025 6:43:30 AM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.9.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: 0x0x1380 Faulting application start time: 0x0x1dbb43c375c24a0 Faulting application path: C:\Users\Usere\AppData\Roaming\Vintagestory\Vintagestory.exe Faulting module path: C:\Users\Usere\AppData\Roaming\Vintagestory\Lib\openal32.dll Report Id: 95eef43c-e152-4b0d-b9be-8e600a27b966 Faulting package full name: Faulting package-relative application ID: } -------------- { TimeGenerated = 4/23/2025 6:41:10 AM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.9.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: 0x0xcbc Faulting application start time: 0x0x1dbb43b9c753c19 Faulting application path: C:\Users\Usere\AppData\Roaming\Vintagestory\Vintagestory.exe Faulting module path: C:\Users\Usere\AppData\Roaming\Vintagestory\Lib\openal32.dll Report Id: a11e736d-49b3-4b92-ac4c-135a6e88cb1b Faulting package full name: Faulting package-relative application ID: }
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.