View Full Version : 237 bc bug
What is this 237 BC bug in RTW?
It's a bug that I believe made its first appearance with the 1.5 patch of the game.
Essentially what happens is that once you finish the turn 'Winter, 237 B.C.', the game immediately crashes to the desktop. I am told that this has something to do with the Carthage glassmaking event.
Is there an absolute certainty that the game will crash once 237 comes around? Or does it only happen to some people? Is there an unofficial fix for this?
A) If it happens to everyone, yes. I retried that turn over 7 times, and every time it happened.
B) I have no idea. But I know that it's happened to 3 people at least (including me)
C) Not to my knowledge. Hopefully, CA will release a fix-up patch sometime soon. If they don't, maybe Player1 will hook us up. I'd do it myself except I have next to no knowledge with computer software.
This is absolutely ridiculous for a mature product with numerous patches to have such a serious bug.
My first rtw in a long while and its buggy pos.
Does this only have an effect when playing as Carthage? I've made it past 237bc in my campaign as Julii. Also loading from autosave may kill that corruption bug as a workaround for now.
It happened for me using the Julii, and Autosave didn't help. This bug is getting more mysterious by the day.
Seasoned Alcoholic
01-11-2006, 11:00
On a side note, where did you download your RTW v1.5 patch from? Perhaps it is a corrupt patch? I'd downloaded RTW v1.3 from DOWNLOAD.COM (http://www.download.com/), and this was a potentially corrupt patch because I found 2 models which needed partial recoding. Everytime you met these 2 units (velites, velite gladiators) on the battlefield, the game would just crash.
If you're convinced that it is this Carthaginian through a glass clearly event, why not remove the entry from the descr_events @ C:\Program Files\Activision\Rome - Total War\Data\world\maps\campaign\imperial_campaign, just backup the file before you do the editing.
professorspatula
01-11-2006, 16:07
From what I read on the official forums, this bug tends to affect people who are continuing a campaign from version 1.3 or earlier. Certain historic events cause the crash. I haven't experienced it in my saves or campaigns since 1.5 though.
Removing the event from the descr_events.txt file apparently does nothing, because once the campaign has started and the file has been read and the game saved, it doesn't reference that file anymore. Or something along those lines.
A thread at twc says that Julii 1.5 crashes at 161BC.
http://www.twcenter.net/forums/showthread.php?t=40795
So 2 dates seems to have problems.
Would the cheat date year work by skipping over a probem year before it crashes.
From what I read on the official forums, this bug tends to affect people who are continuing a campaign from version 1.3 or earlier.
Surprise there. And I thought it was common knowledge that savegames don´t work after the application of patches. I´ve never, ever, heard that they did.
Surprise there. And I thought it was common knowledge that savegames don´t work after the application of patches. I´ve never, ever, heard that they did.
CA claims that 1.3 and 1.2 patches should work with 1.5. (1.5 Readme (http://www.totalwar.com/community/Romereadme.htm)). So apparently they overlooked something or it is a random problem.
I don´t have 1.5, so I didn´t know the readme said so. It just proves me right, don´t trust savegames to work after patching.
Philippus Flavius Homovallumus
01-14-2006, 23:10
I can confirm I do not have this bug in my Macedonian Campaign from 1.3. I tested it as soon as I heard about it and I go "Through a glass clearly" in 236 as normal. I had already got past that point but I reloaded, so its not universal.
I'm pretty sure it only affects patch 1.5, not sure about all cases, but it did happen once to me.
shadowarmy75
01-15-2006, 17:04
You could just use Romesage to alter the date just before it happens so you don't encounter it. Sorry for not having the like. It's somewhere on TWC.
gardibolt
01-20-2006, 20:51
Although it seems to happen most frequently with savegames from earlier versions (it happened to my Carthage game from 1.0 continued in 1.5), there are some reports of it happening in games started in 1.5. I tried a Brutii game I started in 1.5 and was able to get past 237 BC without a problem, so I'm not sure what the deal is.
shadowarmy75
01-20-2006, 23:11
I tried Romesage but it makes the year 60k something.:oops:
gardibolt
01-25-2006, 21:27
A fellow over at the Shogun claims to have fixed the bug. I haven't tried it since I've since gotten entranced in a 1.5 Brutii game, but those having problems might try this out:
http://p223.ezboard.com/fshoguntotalwarfrm44.showMessage?topicID=2557.topic
gardibolt
01-31-2006, 17:29
I've put together an improvement on chuggnut's fix for this bug found on the Shogun. Make a backup copy of your historical_events.txt file in the Data folder. Then go to my rudimentary page:
http://personalpages.tds.net/~mzimmer/
and save the historical_events.txt file that is the second thing on the list. Put that into the Data folder, replacing the original historical_events.txt file. That should allow you to play in 1.5 through 237BC and 167BC on both games started in an earlier version and in 1.5 (in chuggnut's version you had to switch back and forth depending on which kind of game you were playing). I tried it out and it allowed me to continue by 1.0 Carthage game that had stalled in 237BC, and it also allowed me to go through that date in by 1.5 Brutii game without any problems. So if you're experiencing the bug, try this out.
vBulletin® v3.7.1, Copyright ©2000-2025, Jelsoft Enterprises Ltd.