Romani Crash 251BC

'Nuff said really, all working ok until now, persistently crashes at the end of the rebel turn in 251BC Winter, playing Romani..

REALLY IMPORTANT INFO:

Did you remember to post your savegame?. Here's how.

Here it is

Which version are you playing? If you do not use 1.0 yet, please upgrade and start a new campaign.

I'm on 1.0

On the same topic, do you have any unofficial mods installed?

A few personally modded files, have included with the .rar file

Have you applied all the permanent fixes for 1.0 in this sticky? If not, do that right now, even if they don't seem relevant.

All installed, and nothing seems to help..

Have you tried all the temporary fixes in the sticky mentioned earlier? If not, do that right now, even if they don't seem relevant.

Tried 'em out..

Does it still crash if you do not enable the background script?

It does indeed

Have you tried it 3 times or more, with consistent crashes?

I'm on my sixth or seventh go..


IMPORTANT INFO:

Have you diligently started the background script every time you loaded the game? Occasionally not having it activated will probably not make any difference, if you're lucky, but running most of the game without it is likely to make stuff inconsistent (this means crashes).

Have done so far

What is happening when the crash occurs? Are you attacking someone, were you attacked, were you conducting diplomacy, was the AI doing its turn (if so, which faction?) etc.

AI Rebels just finishing their turn it seems

Where does stuff happen when the crash occurs? This makes us able to focus more on the area in question instead of looking around the map.

Last movement, is AI rebel Family member garrisoning a city in Central Europe..

What year is it?

251BC, Winter

Are any cities about to rebel? There are apparently all sorts of bad stuff that can happen with this. We've eliminated most, but a few rare cases seem to remain.

Not to my knowledge

Thank you for a good and detailed report :2thumbsup:. I suggest you start a new campaign or revert to an older save until we find out what's causing this.

Ah, found the problem!

Turns out it was all my fault, I'd buggered up a trigger for inheriting a Cognomen, boy is my face red:yes: Put two and two together when a new game crashed the turn before one of my sons was due to come of age.

So yeah, thanks for your time, and sorry for taking it up!


:oops:

I think there was some mixup concerning the cognomens "out of the box" too, but then this was not your case. No problem about you posting here, I haven't spent any time on it yet anyway. Happy conquering :2thumbsup:!