60s BC crash issue

**joecool250** · October 02, 2007, 11:31 PM

i know this keeps coming up, but i am running RTRPE 1.9 and my game keeps crashing each time. it use to on 67 BC, but i had a saved game around the 80s, so i went back to it and now its crashing at 65, i dont want to go back again. is there a fix. i tried running the map bat file and it didnt work, and i deleted all references to the medica event and it didnt work either. i tried romesage but it wont let me create units or buildings after i change the file. it completely screws up the game. i am NOT using bi, although i have it. any suggestions?

**Switch** · October 03, 2007, 08:48 AM

It's quite possibly the Revolt CTD. See this thread. The hotfix seems to be save-game compatible (but back up the files anyway!), so there should be no harm in at least trying it

.

**florin80** · October 03, 2007, 11:26 AM

It`s this one most likely:

5.You get a CTD in the region of 66 BC.

from the List of Known/Fixed Bugs for RTRPE v1.9 pineed right above.
Presumably you are playing with the romans. Only thing you could try is to load the saved game after starting the game with the BI exe. Slim chances as some have tried it in the past and with no luck, but there is this theory that maybe it is hardcoded only for the RTW so you can try it.
RomeSage does that to RTW v1.5 or BI v1.6. It says in its readme that it is compatible with these, but at least when it comes to changing dates it messes the saved game. Don`t try it. It only works well with RTW v1.2 and mods based on that.

**joecool250** · October 08, 2007, 08:47 PM

i started a game over with bi.exe and still the bug hits.

it gets me angry, i know romesaga doesnt work, it really screws up the dates and i cant recruit.

**florin80** · October 09, 2007, 12:49 PM

So, you are playing with the roman faction, right?

**Marcus Camillus** · October 18, 2007, 12:12 AM

It appears to an inherent problem with the RTW game engine due to the removal of the Senate and other Roman factions, or at least the Senate faction, from not only the campaign, but via the mod, from the game too. If the mod were not as long as it is, and ended in 70 BC instead, or started later than it does, the whole issue. Other mods that have removed the Senate faction and do not experience this issue either are not as long in total game turns.

Personally, I'm creating a new mod for myself that should not experience this CTD issue. Until reading through the Roma Surrectum mod's forum, I thought I might be unique with my solution, but have now discovered at least one other individual who thought of the same idea as I. The exact details I'm sure will be different, but Roma Surrectum v2.0 looks to be featuring a similar approach to what I've been designing for myself.

**spqr_arcani** · January 17, 2008, 01:22 PM

Has anybody been able to run a campaign as Romans to 1 BC?

I've had a enjoyable campaign as Romans and I think I'm starting to hit this 66BC issue too. It started happening around 56-55 BC for me, and this seems to coincide with RTR starting 10 years earlier.

Aside from that, the game has been mostly stable with infrequent crashes.

The thing is that once in a while you can get the end turn to work after you reload the game. Other times you have to do a few things such as buy some units/improvements before end of turn. It seems to be pretty random, but it is possible to get the game to move forward. However, at this stage you're just dreading the end of turn and the high possibility of CTD just ruins the experience. It becomes a game of "what can I do to get around the ctd" instead of "what's the next plan of conquest."

Are there any RTR versions coming up that will for sure fix this?

Thanks,
a big fan

**florin80** · January 17, 2008, 01:37 PM

Roma Surrectum has tested (successfully according to their betatesters) a solution for this. It changes the year date according to the ab urbe condita concept. The changes are minor and anyone could make them. Basically you change the year dates for the timeframe since this CTD seems to be date related and not turn related. The auc next to the date is cosmetic. But, since it modifies the descr_strat it won`t probably take effect in an ongoing campaign. Here`s what they did:
http://www.twcenter.net/forums/showthread.php?t=139528

**spqr_arcani** · January 17, 2008, 03:16 PM

Hi again florin80,

By descr_strat not taking effect in an ongoing campaign, does that mean I have to regenerate the map.rwm? I still don't fully understand what the map.rwm does and when regeneration is needed or not.

Well, I'll try either way.

Thanks again!

**florin80** · January 17, 2008, 04:37 PM

You can try and force it to take effect by deleting the map.rwm file, but it`s very likely you`ll get a ctd or other issues. What I meant is that you`d need to restart the campaign after doing the modifications to the descr_strat to change the year dates and the old saved games might not be compatible anymore.

**spqr_arcani** · January 18, 2008, 03:39 PM

Originally Posted by florin80

You can try and force it to take effect by deleting the map.rwm file, but it`s very likely you`ll get a ctd or other issues. What I meant is that you`d need to restart the campaign after doing the modifications to the descr_strat to change the year dates and the old saved games might not be compatible anymore.

OK, I changed the descr_strat.txt and started a new campaign.
In regular RTR PE, the original start_year is -280 and end_year is 1.

It doesn't use the ad urbe conditia, and so it was easy to change.

Now I'm just thinking too much and wondering how the 66/67 BC instability comes into play. Is there a hard-coded mechanism by which this happens? What I'm saying is, if end_year is 1, then I'm really hoping that the 67-year instability is caused by the code relative to the end date. I've read somewhere that the original vanilla game, the civil war between the three Roman houses has something to do with it. If the 67/66 BC was relative to the start_year, then we'd still be in square one.

Anyway, I set my end year to something ridiculously far, and hope that I can complete a campaign in peace this time. The fact that florin80 mentioned that this was tested out gives me some degree of confidence.

Thanks!

**Candelarius** · January 17, 2008, 09:15 PM

Nice to see that Florin and Marcus are promoting this new fix...and interesting that Marcus thought of it on his own, too! :-)

I'd like to see this fix make it into the RTR 2.0 (final?) version. Any plans on that Marcus?

**jrae081** · September 02, 2011, 04:13 PM

I've been having this same issue through 3 consecutive Roman campaigns.
I have tried changing the starting and end years before each campaign. However, the problem dosn't seem to be the year, but the number of turns. For me the CTD takes place Between 426-432 turns (67BC-64BC).
I know its been three years since the last post on this thread but dose any one know a way around this issue?

**MasterOfThessus** · September 03, 2011, 09:43 AM

How about the hotfix in the 2nd post?

**Dave T** · September 23, 2011, 08:22 AM

I may be late to this particular issue but I've only just got this far into the game and it's driving me up the wall! I am experiencing this CTD at 65BC. I have installed the CTD hotfix and even tried the "ad urbe conditia" date change fix. Both have failed to work or make any difference. AND I've tried continually saving/loading games etc.

Does anyone know a guaranteed fix to this problem? Will changing the start or end dates work somehow? I still want (ideally) the game to end at 1AD. Would changing the end date to 70BC work around this - although meaning a shorter game, at least might 'officially' end?

I am running RTR PE v1.9, playing as the Kingdom of Bactria and use the BI start icon (I have tried the the non-BI start and this makes no difference either).

Any help MOST appreciated!