I found this totally eliminated the number of virtual function call crashes that my game got.īugfix compilation for Stainless Steel 6.4 - This is essential for campaign stabilityīattle CTDs - go to here and copy and replace all your files in the directories from AISet1 to AISet5 with the ones on that github. Installation directory, the guys on the EB2 project discovered there is a cap on the length of texture paths that MTW2 can load, so try to move your installation out of program files into a new folder such as C:\Games\MTW2\mods and cut out any excess path sections such as /SEGA/. There area few things that you can do to reliably increase stability and possibly remove ~75% of the CTDs.ĤGB patch - this one helps a lot with the late game CTDs and possibly battle CTDs The desktop campaign only had 1-2 crashes over the 700 turn duration while the laptop generally crashed every ~30 turns, so the difference is pretty striking, so it seems hardware makes a huge difference to Medieval 2/Kingdoms stability. Everything was identical down to the installation directory, with both systems running the latest Windows version + 4GB patch (which helps a lot).
I tested AI-only campaigns on my 2 systems, one was a reasonably fast desktop and the other was my slightly ageing but still decent quadcore-ivy bridge laptop.
I have been playing stainless steel 6.4 a lot recently and after having stability issues with late game end-turn CTDs and corrupted saves did a bit of investigating.
0 kommentar(er)
