Late Game "Super Long Turn" Bug

[Callistonian]

Did anybody ever satisfactorily figure out how to fix this? I’m referring to the bug wherein the AI’s turns start to take forever usually in the late game. This happens a lot with the Ottomans but it can happen with any faction that gets too many single unit armies running back and forth continuously thus, it usually happens in the late game around 1780 and later.

It’s a really unfortunate bug because very often your campaign will start to get interesting at this point. I have had several campaigns make it to this point and had to terminate them because the AI was taking over an hour for 1 turn. It happens in every campaign I've started. By the time you get to 1800 the game is unplayable.

If you know of any fixes for this please share.

[operating1]

Try lowering your graphics and check to see if your drivers are up to date.....

[Callistonian]

My graphics are already on very low settings and yes my drivers are up to date. I'm pretty sure I know what the issue is as I've seen the AI doing this bit where they move a single unit army back and forth continuously for an entire turn, usually accross some sort of narrow pass. If it were a graphics/driver issue I would probably be experiencing problems a lot earlier in the campaign but this problem is specific to the late game when the AI has tons of single unit armies. You can also check on HG to see that I'm not the only person who has experienced this bug.

[operating1]

Yes, have read other comments than yours along the same line. You could try SEGA support, they do answer questions, however they require that you provide more than just making your point...

[Callistonian]

Originally posted by operating1:

however they require that you provide more than just making your point...

I'm sorry, I thought explaining the problem I'm experiencing would be useful. Silly me. You know, you could have just said "I don't know" from the start but thanks for killing this thread for me instead. (is this where I write ellipses?)

[operating1]

"Oh, well"?

[Turd King]

I think your on the money friend. That and probably at that point in the game there is a lot of memory being used to remember all the various changes since the Vanilla start.

[Viral]

Sadly the only counter to this is to take out the ottomons / maratha who ever is the problem.
Generally by the time the game gets to that point im about 10 to 15 turns from being able to remove the problem by force.

I have treid unit size and difficulty changes, but its (i belive) the reinforcement and single unit rush tactics the AI and game use that slow it down so much.

Since we cant have access to the source code, we cant properly tinker with it. Theres 0 chance the IP owners will ever come back to fix it.

There fix was releasing napoleon. Great game, maybe superior in some to most areas, but feels so small compaired to the over reaching behemoth that is empire it was simply over reaching for its time.

[Bouncing Betty]

i know...i have just me (Prussia) ,Portugal and the Marathas left standing and ready to have a massive, worldwide battle royale...OOPS, we' re sorry!! AI takes 4hrs to cycle, therefore making my planned massive war a fantasy because the lag has rendered my game unplayable! And there is no way of fixing the bug! sux....bigtime.

[operating1]

Originally posted by Bouncing Betty:

i know...i have just me (Prussia) ,Portugal and the Marathas left standing and ready to have a massive, worldwide battle royale...OOPS, we' re sorry!! AI takes 4hrs to cycle, therefore making my planned massive war a fantasy because the lag has rendered my game unplayable! And there is no way of fixing the bug! sux....bigtime.

If you do not find a solution here Go to: https://support.sega.co.uk/hc/en-gb/requests/new

[Callistonian]

I've seen a couple posted solutions to this bug online. A lot of people mention using Darthmod with certain settings for the turns (3 turns/year iirc). Many people suggest just killing whatever faction is causing it (although in my experience, it's not just the Ottomans or Marathans but really any faction that gets too big and has too many one unit armies). There was one really specific solution where you have to have fewer than 49 territories by 1767. I tested all of these solutions to an extent and none of them resolved the issue.

Thanks for linking us to the Sega help forums operating1. Just so everyone is clear: this game has not had dev support for years and the single unit army bug is well documented. This means that your only solution will be a mod - you're not going to get a magic reply from Sega telling you to change a setting that fixes it (otherwise, I assume operating1 in his infinite wisdom, would have already posted it here because he's genuinely interested in helping... right). I have not unpacked the Empire files since I uninstalled (due to this bug) so I'm not aware if this is fixable (presumably, that would mean AI scripts external to the exe).

[operating1]

OK, I'm no computer techie, but I do read a lot of the posts here from which I get a general idea what is bug and what is not a hard bug issue. The lag problem overall does not seem to be a hard bug, but more of a OS problem or something related to your computer. Yes there is a lag at times when breaching fort walls when both sides have maximum stacks, although not always the case, but to have lag every turn is out of the ordinary, however very fixable if handled by those in Sega support. If you choose to complain about it and not seek those who can help you the most is your problem..

[Callistonian]

Originally posted by operating1:

OK, I'm no computer techie...

Clearly.

I was about to type out a long reply refuting you once again, but it's pretty clear you have nothing to contribute at this point and no idea what you're talking about. I can only reason that you're still replying to this thread because you're under the impression that we're somehow insulting your beloved game by pointing out that it has a major, ubiquitous bug and you're trying to tell us to email Sega (which will accomplish nothing as we have already been over) or we should shut the hell up.

[operating1]

First, this maybe your thread, but you do not own all it's content. Secondly, my post #9 was not directed to you, but to another member who is experiencing a problem. Thirdly, you butted in where you have no solutions of your own. Fourth, let the member or readers decide for themselves if Sega support can be a route for problem solving that they may not have been aware of, all personal opinions aside...

[Callistonian]

Originally posted by operating1:

let the member or readers decide for themselves if Sega support can be a route for problem solving

You have yet to tell us what you expect Sega to do about this. If Sega has already addressed this issue in some way, please by all means share your knowledge (I'll be waiting). Linking people to Sega support is not a legitimate response to this bug (or frankly any other bug). It is not only entirely unhelpful, but downright insulting to the intelligence.

I posted this thread in the hopes that by 2016, now almost 2018, someone in the community would have found a solution to this bug. Seeing as I'm being trolled by an apologist linking to Sega support, I surmise that the answer is a resounding "no". Thank you for absolutely nothing.

[operating1]

It's too bad about your attitude, cry babies always sound the same...