Re: Roman campaign CTD on opening savegame
This problem is around since 2.1 and no one has been able to solve it so far. One probable solution, which I haven't tried yet, is to remove the whole crusader attack script.
See also:
http://www.twcenter.net/forums/showt...mpire-Campaign
http://www.twcenter.net/forums/showt...ds-(CTD-issue)
http://www.twcenter.net/forums/showt...=1#post6538780
http://www.twcenter.net/forums/showt...=1#post6563687
http://www.twcenter.net/forums/showt...=1#post9452509
http://www.twcenter.net/forums/showt...=1#post8653532
A probable workaround:
http://www.twcenter.net/forums/showt...8#post10274598
Originally Posted by
mandalore
Hi, yesterday I decided to try another approach with my Armenian campaign.
This time I decided to avoid saving until Constantinople was no longer under siege. So, I sent an spy, let a couple of turns pass, to 62, saw it wasn't besieged and then saved and reloaded. It worked!!
So I can go on with my campaign, at least while a mongol siege or some scripted event doesn't cause a similar problem. I know It's only a workaround, but you may try that, Marutukku, if your CTD upon loading is related to some scripted event, like mine was.
Originally Posted by
mandalore
Hi again,
Just wanted to let you know that my previous Armenian campaign finished successfully and without issues to the end around turn 100. Also, I've just finished a Malikate of Sindh campaign in which I've had just the exact same CTD issue with the siege at Constantinople at the same turn 60, bypassed again by avoiding reloading any savegames until 62. I've had no other issue at least again to around turn 90.
Don't know if there are issues later, but for me since I've changed the script there is only the (repeatable) Constantinople issue, which can be walked around.
Last edited by Garbarsardar; May 16, 2016 at 11:49 PM.