Jump to content

game crashes for second player after host updates a mod ?


Oke518

Recommended Posts

hello all me and a friend have been playing a new world since 1.16 and have run into a strange thing that happens when "i" the host of the Lan game update mods. when i update a mod i.e. delete the old zip and put in the new one then relaunch the game it runs perfectly fine for me in every way signal player/Lan/internet. but if my friend try's to rejoin the world his game just crashes to the desktop full stop only deactivating the mod/ down grading will allow them to join again. we have a lot of time in this world and would love to not have to restart. any ideas?

Link to comment
Share on other sites

This is the friend in question. I've copied the error message I was getting when trying to join, hope this will help:

 

Spoiler

Running on 64 bit Windows with 8 GB RAM 
Version: v1.16.0 (Stable)21.01.2022 17:31:44: Critical error occurred
System.ArgumentException: Ein Element mit dem gleichen Schlüssel wurde bereits hinzugefügt.
   bei System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   bei System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   bei System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
   bei Vintagestory.Common.ModLoader.CheckAndSortDependencies(IEnumerable`1 mods)
   bei Vintagestory.Common.ModLoader.DisableAndVerify(List`1 mods, IEnumerable`1 disabledModsByIdAndVersion)
   bei Vintagestory.Client.NoObf.SystemModHandler.OnServerIdentificationReceived()
   bei Vintagestory.Client.NoObf.ClientMain.ProcessServerIdentification(_hpqb4cNQuSfxZLdFacKLPiYYWAN packet)
   bei Vintagestory.Client.NoObf.GeneralPacketHandler.HandleServerIdent(_hpqb4cNQuSfxZLdFacKLPiYYWAN packet)
   bei Vintagestory.Client.NoObf.ClientMain.ExecuteMainThreadTasks(Single deltaTime)
   bei _0dbBCVS4kT4NsuDZA84yDu7r3AG._1NlBQQ8qS5idQptIBQaAbARuOfxA(Single )
   bei _vFhcDU5n6Z0hUte90jdaxlrDjR5._HuDdfzha8ZKZvU2y0RbH58r7VzR(Single )
   bei _vFhcDU5n6Z0hUte90jdaxlrDjR5._XZOFA2JA54yZjH15yys9W7vL9hj(Single )
   bei Vintagestory.Client.NoObf.ClientPlatformWindows.window_RenderFrame(Object sender, FrameEventArgs e)
   bei System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   bei OpenTK.GameWindow.RaiseRenderFrame(Double elapsed, Double& timestamp) in C:\Users\Nexrem\Desktop\transfer\opentk\src\OpenTK\GameWindow.cs:Zeile 479.
   bei OpenTK.GameWindow.DispatchRenderFrame() in C:\Users\Nexrem\Desktop\transfer\opentk\src\OpenTK\GameWindow.cs:Zeile 454.
   bei OpenTK.GameWindow.Run(Double updates_per_second, Double frames_per_second) in C:\Users\Nexrem\Desktop\transfer\opentk\src\OpenTK\GameWindow.cs:Zeile 375.
   bei _FKpOpQGqqf3cJWdQyWh1ysxsDBb._pYad7oBcQ5qtzQkYGDu4NFHQxhK(_5x3PJgrln4IBXPDNSNN0fecxKFb , String[] )
   bei _sejP0Tcz8wTg70ptIdRr3CwQmrE._pYad7oBcQ5qtzQkYGDu4NFHQxhK(ThreadStart )
-------------------------------

Event Log entries containing Vintagestory.exe, the latest 3
==================================
{ TimeGenerated = 14.01.2022 17:27:22, Site = , Source = Application Error, Message = Name der fehlerhaften Anwendung: Vintagestory.exe, Version: 1.16.0.0, Zeitstempel: 0x61dc5145
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.19041.1387, Zeitstempel: 0x0b9a844a
Ausnahmecode: 0xe0434352
Fehleroffset: 0x0000000000034f69
ID des fehlerhaften Prozesses: 0x52c4
Startzeit der fehlerhaften Anwendung: 0x01d80963965f7aa3
Pfad der fehlerhaften Anwendung: C:\Games\Vintagestory\Vintagestory.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: a5205b94-ef71-4992-aa08-e511257fc4d9
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:  }
--------------
{ TimeGenerated = 14.01.2022 17:27:19, Site = , Source = .NET Runtime, Message = Anwendung: Vintagestory.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Exception
   bei Vintagestory.Common.ModCompilationContext..ctor()
   bei Vintagestory.Common.ModLoader..ctor(Vintagestory.API.Common.ICoreAPI, Vintagestory.API.Common.EnumAppSide, Vintagestory.API.Common.ILogger, System.Collections.Generic.IEnumerable`1<System.String>, Boolean)
   bei _vFhcDU5n6Z0hUte90jdaxlrDjR5._stt3ckg04XAvVNS4fr54wm89CXe()
   bei _vFhcDU5n6Z0hUte90jdaxlrDjR5._hndzNoMYcegNh6f26ARDQKxU9eE()
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   bei System.Threading.ThreadPoolWorkQueue.Dispatch()

 }
--------------
{ TimeGenerated = 14.01.2022 17:27:08, Site = , Source = Application Error, Message = Name der fehlerhaften Anwendung: Vintagestory.exe, Version: 1.16.0.0, Zeitstempel: 0x61dc5145
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0x00000000
Fehleroffset: 0x0000000000000000
ID des fehlerhaften Prozesses: 0x39e4
Startzeit der fehlerhaften Anwendung: 0x01d809638e0acaf7
Pfad der fehlerhaften Anwendung: C:\Games\Vintagestory\Vintagestory.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 8d08a22a-e38d-42b1-aacc-2986661b4cf8
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:  }

 

Link to comment
Share on other sites

Are both of you using the same exact game client release version AND the same exact mod file versions on each computers at the same time?  Your comment reads that you are upgrading a game modification file, then running it while your friend is not using or hasn't  updated the same modification file on their computer. Both computers need to use identical game client versions and mod file versions to ensure compatibility problems are minimized during multiplayer or co-op games. Ensure that the game client version and the mod files version are identical on both computers first and see if that resolves the problem.    

Link to comment
Share on other sites

×
×
  • 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.