Resolved Siege crash in 1.3-1.4

[sodrian]

Hey,

My game always crashes when I enter the siege field. "Send troops" works ok, "Attack" option gives me crash 2-3 seconds after the field and troop are loaded and I send troops.

I have no mods at the moment. I have completely uninstalled them.

This appeares on both 1.3. and 1.4 versions. And started after 1.3 update right away.

I have checked the save on 2 PCs. The same crash.

I have tried to siege different cities and castles - same crash.

I have up to date version of .Net framework which is auto updated with Windows update system and version is 4.8.

I have lowered graphics settings to the lowest ones and decresed number of troops in battle to 200 - same crash.

Here are the details. I can provide any info, the save as well, I have a lot of crash logs.

Here is the error log:

Spoiler: Error crash

Starting new log file...
16 May 2020 Saturday 00:10 RTZ 2 (ceia)
Computer: SODRIAN-CM-WIN User: sodrian
Build Version: 229335

<##########################################################################################>

#kernelbase.pdb@{7D42F2FCA0F02E76EFBE1EEBF10F3102} (1): 0:239673
#clr.pdb@{6017733E0FFB4326B3FA4CBAD6CF43AC} (2): 0:4585
#clr.pdb@{6017733E0FFB4326B3FA4CBAD6CF43AC} (2): 0:4635
#clr.pdb@{6017733E0FFB4326B3FA4CBAD6CF43AC} (2): 0:4645
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
#clr.pdb@{6017733E0FFB4326B3FA4CBAD6CF43AC} (2): 0:8734
#Game.pdb@{004B53D10F8A4D3F9EB65310D4B2650F} (1): 0:893021
#Game.pdb@{004B53D10F8A4D3F9EB65310D4B2650F} (1): 0:915296
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
@unknown_module@unknown_source (unknown_line): unknown_function
#clr.pdb@{6017733E0FFB4326B3FA4CBAD6CF43AC} (2): 0:8734
#Rgl.pdb@{F23CFD19C80B41CC93D0B1B4FFDF9123} (1): 0:4531990
#Rgl.pdb@{F23CFD19C80B41CC93D0B1B4FFDF9123} (1): 0:4529772
#Rgl.pdb@{F23CFD19C80B41CC93D0B1B4FFDF9123} (1): 0:4464757
#Rgl.pdb@{F23CFD19C80B41CC93D0B1B4FFDF9123} (1): 0:4320473
#Rgl.pdb@{F23CFD19C80B41CC93D0B1B4FFDF9123} (1): 0:4319691
#Rgl.pdb@{F23CFD19C80B41CC93D0B1B4FFDF9123} (1): 0:4323047
#ucrtbase.pdb@{A90164F7788144CD9392D8286C6F20F6} (1): 0:134770
#kernel32.pdb@{5A77DE8CE8D58731F0EA38F1C92F48D8} (1): 0:97236
#ntdll.pdb@{FB60D3E08B5E4960376A4E73BD35F24E} (1): 0:446161
-----------------------------------------------
#TaleWorlds.DotNet.pdb@{BCF5A8882BFC43798EAE339633FBAA5A} (1): 100663397:8
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100673047:24
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100669634:35
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100669837:173
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100669842:462
#TaleWorlds.MountAndBlade.AutoGenerated.pdb@{73EB983EE7724AEEA7723B094144E1FE} (1): 100663354:70
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100668710:643
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100668708:235
#TaleWorlds.Core.pdb@{2866B7AACFE14E75AD1D89B57A6B8F38} (1): 100664570:41
#TaleWorlds.Core.pdb@{2866B7AACFE14E75AD1D89B57A6B8F38} (1): 100664412:25
#TaleWorlds.Core.pdb@{2866B7AACFE14E75AD1D89B57A6B8F38} (1): 100664465:70
#TaleWorlds.MountAndBlade.pdb@{7F27F654EA0C4589B25A251A0FA5025B} (1): 100670868:200
#TaleWorlds.DotNet.pdb@{BCF5A8882BFC43798EAE339633FBAA5A} (1): 100663415:56



Working Memory: 4950 MB
Commit Memory: 5990 MB

Page Allocator Memory: 0 MB
DumpSendPath: \\rgldumpserver.taleworlds.com\Crashes/2020-05-15_21.12.41
AutoReport: Disabled

 

[sodrian]

According to the error report, this is 100% core error. It's written here: TaleWorlds.MountAndBlade.pdb and TaleWorlds.Core.pdb and TaleWorlds.DotNet.pdb

When will you fix the error? I am not the only one here with this siege crash!

 

[Poenzor]

Same issue here! This error, also Core:

Mountand-Bladeerror-Start-Ofa-Siege

Image Mountand-Bladeerror-Start-Ofa-Siege hosted in ImgBB

ibb.co

 

[uçanbiblo]

Hello, thanks for reporting it in. I will inform the devs about the issue. In the meantime, if you are playing the game with mods please remove the mod files and verify the integrity of the game files afterward. And if you can share your PC specs i am sure it would speed up the fixing process.

 

[elysebluemoon]

Hi, can you share your save files? You can use a cloud service and post an open link on this thread.

 

[sodrian]

I made a save right before the siege. Just manually siege the castle and you will get the crash. I also included the crash debug report, that I got on my pc.

save.and.crash.zip

drive.google.com

 

[uçanbiblo]

Hello, i have forwarded the file to devs. Thank you for the additional info.

 

[uçanbiblo]

Hello, @sodrian. Our dev team have inspected the save file you have sent. It seems a mod you have installed has corrupted the data and its irreversible. You can start a new game but you might want to remove the mod to prevent further corruption.

 

[sodrian]

Can you be more specific?
1. What mode has done the uppermentioned?
2. What kind of corruption is that? I can still load the save and play everything but not the siege.
3. I have prodived you the save without any mods. How come that some mode can save anything in you save files and partially corrupt it?
4. Can't you fix this corruption? Or maybe release the fix to it? It must be very narrow place, because everything else works.

 

[uçanbiblo]

Hello, sure we can!
1. We don't know the exact mod that caused the corruption.
2. Our dev teams report says the game crashed on multiple occasions, not only sieges but field battles as well.
3. Once the save game gets corrupted because of the mods, even if you remove the mod the save game will be corrupted because the coding will be altered, thus resulting a permanent problem on your save game. That's why we ask you to delete the mod files, verify the integrity of the game files and start a new campaign to see if the problem is at our end or caused by the mod.
4. Unfortunately,we can not offer support for the mods or bugs that are discovered within the mods. Your best chance is to get in touch with the mod developer.