Between Turn Crash and Spinning Hourglass
I've encountered a crash during AI turns so I reloaded hoping it'd go away. I reloaded, activated a script and hit end turn. The second time it didn't crash but the hourglass kept spinning and I couldn't do anything except viewing settlements. I reloaded again and thought there's something preventing AI for completing its turns so I "removed" my pieces including the one that was besieging that city west of Alexandria. I hit end turn. AI completed its turn(s) and Seleucid attacked my army. I was happy to see something different, I autocalced and was back to my turn but hourglass spun again.
I consulted Frequent Issues and search feature. :book: I've learned about the rebellion. So my journey begins. My courage waned as I went through barbarians cities, greeted by foul stench and man titties. Just outside the city wall of Ebunorum, I've met a man name Beredos. I thought he was just another brigands trying to steal my eagle but he's not Gaul. He spoke of an tranquil island just a bit north of Belgae. So I wondered what brought him to German lands?
https://img199.imageshack.us/img199/2533/beredos.jpg
By the way, I've looked around for rebelling cities mainly in conflict zones but not found any. Well, I didn't check all but my question is how come I didn't crash when few of my cities rebelled before?
Re: Between Turn Crash and Spinning Hourglass
AFAIK the spinning hourglass is a vanilla leftover and I doubt the EB team can do anything about this. I encountered this twice recently when trying to sally. If you are trying to sally, don't do it - attack with reinforcements instead, and the damn thing will hopefully not bother you any more. I don't know what to do about it in other situations.
The random Casse armies are positioned by the script for some arcane purpose. AFAIK it is a part of the effort to keep the rabid Romans separated from the rabid Swêboz as long as possible.
Re: Between Turn Crash and Spinning Hourglass
Quote:
AFAIK the spinning hourglass is a vanilla leftover and I doubt the EB team can do anything about this. I encountered this twice recently when trying to sally. If you are trying to sally, don't do it - attack with reinforcements instead, and the damn thing will hopefully not bother you any more. I don't know what to do about it in other situations.
Strange. Non of my city was besieged that turn actually and no sallying either. Just couple stacks here and there and one besieging a town garrisoned by a unit (unlikely to sally). Also I have sallied many times and so has the AI even though they're doing it wrong - at last minute lol. What made it different this time? I know all this can be worked around by loading older save. I'm just curious.
Quote:
The random Casse armies are positioned by the script for some arcane purpose. AFAIK it is a part of the effort to keep the rabid Romans separated from the rabid Swêboz as long as possible.
Cool glad to know.
Re: Between Turn Crash and Spinning Hourglass
I pretended to forget about turning script on and hit end turn. Guess what? No lock up and no Casse dude. I've provided a save on bottom. Try it yourselves. Try first without script because you'll have to ctrl-alt-del. Well just for your convenience. Don't forget to toggle_fow before hitting end turn and go to province in question. You can see the Casse dude isn't even there yet. Then hit end turn. Voila he's not gonna be there. After that, try with script on and then end turn. Well duh. :smash:
EDIT - OK I've found some pitchforks on some Sauromate and Hayasdan and many AI's settlements. It's way below 75%. I reduced pop down to 1000 appx. but order isn't improving right away. Guessing the effect is for next turn. Well, drop on public order isn't really a rare occurrence I would think. So how you guys and girls not crash your game? You depopulate a lot?
Also how can I find list of alternate letters used for Sweboz' settlements? I'm trying to depop them but not sure what to type. Also there were no revolts on the last turn.
EDIT II - reverted to older save but same problem came up but at a different date in 192bc. The first one was in188bc.
EDITIII - I managed to get passed the crash by playing the save, one before last.
Re: Between Turn Crash and Spinning Hourglass
Quote:
Originally Posted by Weebeast
I pretended to forget about turning script on and hit end turn. Guess what? No lock up and no Casse dude. I've provided a save on bottom. Try it yourselves. Try first without script because you'll have to ctrl-alt-del. Well just for your convenience. Don't forget to toggle_fow before hitting end turn and go to province in question. You can see the Casse dude isn't even there yet. Then hit end turn. Voila he's not gonna be there. After that, try with script on and then end turn.
That's interesting, maybe there is a bug in the script for whatever he's supposed to accomplish (I'm not sure myself). I'll try your savegame, maybe I can find out something.
Quote:
Originally Posted by Weebeast
EDIT - OK I've found some pitchforks on some Sauromate and Hayasdan and many AI's settlements. It's way below 75%. I reduced pop down to 1000 appx. but order isn't improving right away. Guessing the effect is for next turn. Well, drop on public order isn't really a rare occurrence I would think. So how you guys and girls not crash your game? You depopulate a lot?
Actually, most revolts work just fine. It's something that really happens quite rarely, but it's more than often enough to be noticed of course. It's not easy to find the causes however, so mostly we try to help people work around them instead. Your case shows a bit more promise though. As the game does not crash without the script, it should be possible to narrow it down.
Quote:
Originally Posted by Weebeast
Also how can I find list of alternate letters used for Sweboz' settlements? I'm trying to depop them but not sure what to type. Also there were no revolts on the last turn.
That's not really very easy. It's more likely that you can avert the revolt by teleporting up a unit to besiege them, as cities can't revolt when under siege.
Quote:
Originally Posted by Weebeast
EDITIII - I managed to get passed the crash by playing the save, one before last.
That's great. Let's hope it doesn't return when you least expect it!
Re: Between Turn Crash and Spinning Hourglass
Quote:
That's interesting, maybe there is a bug in the script for whatever he's supposed to accomplish (I'm not sure myself). I'll try your savegame, maybe I can find out something.
Quote:
That's great. Let's hope it doesn't return when you least expect it!
I changed every single move on my third try and yeah I was lucky.
I've deleted other saves many turns before the crash so unfortunately (or fortunately lol) you can only look at one save, a turn before the crash. I'm almost sure that it's not the same as the frequently encountered revolt crash. I managed to continue on my third try because I changed every possible move. It's likely some pathing bug not necessarily EB problem but because it uses a script that spawns things, it could increase the risk...
Quote:
Actually, most revolts work just fine. It's something that really happens quite rarely, but it's more than often enough to be noticed of course. It's not easy to find the causes however, so mostly we try to help people work around them instead. Your case shows a bit more promise though. As the game does not crash without the script, it should be possible to narrow it down.
Yeah it's interesting. Turns out AI owned cities can rebel with no problem. I've had the game crashed on end turn when Meroe had pitchfork. I made it happy and there was no crash. It was controlled by obviously Ptolemy first who was no longer in the game and then AS. However a city next to it by Red Sea rebelled to Eleuthoroi after I took it from AS with no crash. Could it possibly because I planned to abandon it and destroyed every building except the undestructible ones? Sorry for the follow up but I'm trying to not crash often on next campaign, hoping to learn something.
Re: Between Turn Crash and Spinning Hourglass
If we knew exactly what causes revolt CTDs, we would be closer to figuring out a definite fix (we've reduced the frequency significantly already). I believe we've seen plenty of instances of crashes both for player-owned and AI-owned cities. Perhaps razing all the buildings makes a difference, I don't know. We've seen cases where destroying the game field has made the revolt work, without understanding why (and not reproducing in other games, only for those few savegames).
