romani crash to desktop when end turn button is clicked

[Joseph]

Yeah, I do what I can to manage my settlements, but I am an expansionist (have to be, to get victory). Anyways, the game is crashing again, like 5 turns later. so I cheated my way out of it, again, just as you did. EB is a good game, but man oh man oh man do the bugs suck.. I think its the buggiest game I ever tried to play. thank you for linking to the cheats, I didn't think I could so easily just do this to keep the game going at least till I win.

[XSamatan]

1. EB is not meant to play as blitzkrieg. Progress as fast as you can afford, meaning conquer with an offensive-army, afterwards send garrison troops and a governor into the newly aquired settlement, you won't have problems in most cases with that strategy.

2.

I think its the buggiest game I ever tried to play

That is simply false. The bug you received in your campaign is a well known vanilla issue, it is only slightly increased as EB includes more settlements as standard RTW. EB is, seen not only in comparison to its compexicity, a very stable build, however, if you come over bugs, feel free to report them (but honestly, in most times these 'bugs' are features of EB or hard-coded left-overs from vanilla).

XSamatan

[Joseph]

I play the game for 3 or more hours every day. I've been playing it about 45 day. Prior to this game I used to play Rome TW vanilla. I've also played Medieval 2 total war, also kingdoms expansion. also tried empire total war and also played alexander. I beat all these games. Some of them, like kingdoms exp I played as all 4 factions and alexander I've beat 2-3 times on both game modes. My PC runs all of those games quite well but they do crash occasionally. EB crashes twice (conservatively) as much as those other titles. In each and every one of these titles I constantly save, because crashes could come at any transition.

Battlefield 2 crashes once every 6 months. Battle for middle earth 2 (I just played through last month) never crashed once. Internet explorer rarely crashes, say I use it for 10 hours a day, It usually will only crap out once a day when a bunch of tabs are running large scripts. What I mean to say is, I don't think that my PC is the problem.

It crashes sometimes when battles are loading up right as the transition music begins. Sometimes it crashes right after I win and I click the accept button (really sucks after an epic 2 hour heroic victory). Sometimes it crashes right in the middle of battles. Usually these crashes are not replicable. So I just reload the game and play the battle again. Or play the battle a couple of turns later and just seige for a little longer (if applicable). One other thing that I think may be noteworthy: The prompt is over-actively popping up telling me to activate the EB script. Which I do. But then it pops up again and again, on the same play session.

I don't want to be mean and I don't want to be ungrateful for your help, but when you say EB is very sable and that this it is not the buggiest game I've ever tried to play, well, lets just say, I disagree. Further, you're surely correct when you point out the # of settlements is a factor.

[XSamatan]

I play the game for 3 or more hours every day.

If you are using RTW 1.5 as basis, don't play longer as 120 minutes or the RTW memory leak will strike.

It crashes sometimes when battles are loading up right as the transition music begins.

Do you have all fixes for 1.2 installed at its proper locations? If the crash is not repeatable, it is a random vanilla bug.

Sometimes it crashes right after I win and I click the accept button (really sucks after an epic 2 hour heroic victory).

You should wait at least 20 seconds after the battle-resluts are showing up to avoid the RTW memory leak, best is to wait until the music mutes.

Sometimes it crashes right in the middle of battles.

Disable in the settings (\EB\preferences) cutscenes, probably an issue between RTW and your graphical drivers, also a leftover from vanilla.

Usually these crashes are not replicable. So I just reload the game and play the battle again. Or play the battle a couple of turns later and just seige for a little longer (if applicable).

Just to clarify: If a CTD is not repeatable the reason for crashing is in most times the limitations of the RTW engine understanding EB's code in some error-situations. You sure can blame the mod for this, but as long as it is not repeatable the engine is responsible.

One other thing that I think may be noteworthy: The prompt is over-actively popping up telling me to activate the EB script. Which I do. But then it pops up again and again, on the same play session.

You never should start a campaign with another faction in one session of EB! If you want to play any other faction you have to restart EB so the script fires properly, a limitation of the RTW engine. If you reload a save, it is normal that the advisor pops up more than one time, just click it away, it won't appear more than three times in a row in my experience.

I don't want to be mean and I don't want to be ungrateful for your help, but when you say EB is very sable and that this it is not the buggiest game I've ever tried to play, well, lets just say, I disagree.

No harm done, however, nearly all of your mentioned 'bugs' are due to the limitations of the RTW engine, without a new patch from the creator (which won't be released anytime) there is nothing one can do about these issues. I would ask you to read the Frequent Encountered Issues of EB so you can get around by this hard-coded stuff yourself and understand my position in this aspect better.

Regards,
XSamatan

[Ludens]

To clarify: the R:TW engine has a number of issues that are don't arise or are negligible for the vanilla game, but become problematic when you attempt to max the possibilities of the engine. The memory-loss is one of these: on a powerful computer you won't even notice it when playing vanilla, but EB's huge data files seem to result in crashes if the game is played for a long time.

There are a number of unsorted issues with EB, but because most crash bugs aren't replicable* the problem does cannot lie in bad data-files. These stay the same. Presumably, the problem lies in the fact that the datafiles interact in ways that weren't attempted by the original developers, and this causes unforeseen problems in the core engine. In other words: EB's file do what they should. It's the engine that is causing problems, and because the crashes aren't replicable we cannot even guess at the causes.

(* the campaign to/from battle bugs aren't replicable in the sense that you can fight the same battle on the same location a few turns later without consequences.)