Resolved [1.5.2 Beta +HF] Starting siege of Chaikand causes CTD, problem persists long term in campaign

Users who are viewing this thread

Version number
1.5.2
Branch
Beta
Modded/unmodded
No, I didn't use any mods.
Summary: I go to Chaikand and press besiege option and get a crash to desktop. For days I have tried once a day and sent a crash dump, then done something else in the game hoping it would resolve whatever the problem is. The problem persist and I'm at a point where I really need to take Chaikand as taking another fief first would over extend... me. This same CTD occurred some versions ago and got patched. Who knows if it's the same cause, hope it's an easy fix!
How to Reproduce: Load .sav below and go to Chaikand and try to besiege it.
https://drive.google.com/file/d/1ZwZuEZe2-BBD6y8A5FZO7XHWaBze2U8s/view?usp=sharing
Scene Name (if related):
Media (Screenshots & Video):
Installed community-made modifications: none
Computer Specs
:
OS: windows 10
GPU: NVIDIA geforce 1050 ti
CPU: i5-4570
RAM: 16gb
Motherboard:
Storage Device (HDD/SSD): OS on HDD, game on SSD
 
Forwarding this issue to the QA team for further investigation. Thanks for reporting. In the meantime, if you can send a crash report and post the ID here, that would help us a lot as well.
 
I have been informed that this issue is fixed on our development branch and the fix will be implemented with the upcoming patches. Thanks for reporting!
 
Back
Top Bottom