I know a few people that are having this problem now. And its kind of a bummer im sincerely scared of fighting siege battles knowingly the game might crash once i have won.
Vicarius
CTD at the end of SIEGE
I know a few people that are having this problem now. And its kind of a bummer im sincerely scared of fighting siege battles knowingly the game might crash once i have won.
Re: CTD at the end of SIEGE
My experience: there is a massive memory dump at the end of big battles (especially sieges) causing a crash right when you end the battle. Lower your video settings by a lot and try the battle again then increase it from there. You will eventually find the setting that can handle the big battles and still look good. Hope this helps.
Re: CTD at the end of SIEGE
Wasn't M2TW released in 2006, 6 year old game?Originally Posted by Remonster6x
My computer can play pretty much any game on the market currently at the highest settings, I can't even fathom how M2TW/SS can be even considered 'graphic intensive' in 2012. I'm not sure what computer the OP has, but I think a lot more might be going on during sieges than a memory dump...although admitedly your theory is better than mine, since I have none!
My crash:
I had my first siege battle crash yesterday (and it was an epic one too!), I was assaulting Paris and barely pulled out a victory and had my first CTD after about 10-15 successful ones(only started playing again recently). I've also had over 150 battles with no battle crashes prior to this one. I didn't try to replay the siege because I didn't have the energy to do it again after that, but maybe I should have just to see what would happen!
Praefectus
Re: CTD at the end of SIEGE
Without checking the system log (see stickies in this forum) you won't get far. Imho the farther up you go with unit sizes and unit numbers involved in a battle the more likely you will get a crash at the end of a siege battle. As a sidenote: high-end-system or not - the engine stays the same.
Posting Permissions
Reply With Quote
