With this done, the extra pressure in the pipe highlighted that both the nylon pipe and the master cylinder were leaking. She rebuilt the slave cylinder using an uprated seal kit, as the usual kits are known for not lasting very long. She's done all this herself which is pretty cool. I've done nothing on this but occasionally offer guidance, or stand and drink tea and watch. I keep encouraging her to sign up here and update her own progress, but for the moment I'll add this. Always make dedicated saves every few turns.Mrs Juular has been busy behind the scenes sorting this out. The battle AI performs better aswell.ĭisable autosave - this is something I have not found the need to do but apparently it can improve stability as recommended by the EB2 team - go into the base medieval 2 directory and change the autosave text line in Įven doing this, the game still occasionally crashes, and sometimes saves can go corrupt and you have to go a turn or two back. SSHIP is a more recently updated stainless steel submod that fixes a lot of issues, and I think it removes some of the battle CTDs that occur often with skirmisher heavy armies. 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)
