66-67 BC late game crash, RTRPE 1.8 (Possible problem being researched, unable to duplicate in testing.)

[FMvonKleist]

RTRPE 1.8 is fantastic, however, the late game crash of 66 - 67 BC still exists. Install was done correctly with no other modifications run. Please advise on this issue. I have still yet to be able to play out what I consider to be one whole game.
I have already play tested this issue twice, to confirm it exists. I really would like some resolution to this issue, given it continuously has plagued the game, in both gold and the superior PE version.

FMvonKleist

[MacLiam]

Does every campaign crash around that date or just randomly ?
Because my Roman Campaign is nearing that date.

[FMvonKleist]

Yes

[FMvonKleist]

You will soon discover the agony I have always had with the mods in this game.

[MacLiam]

Well that's a nice thought to start the weekend.

[FMvonKleist]

If you are like me, I think the game is just getting really fun by that time. I hope they eventually fix it. It can't be a mistake on my part. I tested it with two computers, confirmed installation. No viruses, spamware, or programs running to mess it up

[gazdagod]

hi all, i have a problem, i have just done everything it says to install this mod by installing 1.5 etc. i get onto the game but when i click advance to start a battle once iv selected teams and troops the game cuts off and takes me back to windows with no error message. can anyone help?

[FMvonKleist]

Make sure you have deleted all the map.rwm files. Look at solutions to common problems and installation of RTR PE 1.8

[Salvor Hardin]

FMvonKleist, I know that Marcus Camillus had taken measures to fix this issue for PE. But, as far as I remember, there was no way to find anybody who had reached this date and could report wether the fix was working or not. Unfortunately, it is quite obvious that it was not. Nevertheless, it might be very valuable to have your save-game in order to see if this is the problem that Marcus Camillus struggled to solve or a new one. This way, as soon as RTR Forums are back I could contact him and try to add a solution for the next Platinum version (or a fix for the existing one).

Thanks in advance.

[Quinn Inuit]

I recommend commenting out all references to the De Materia Medica event. I'm almost positive that's the culprit, but I don't know why. All of its names are identical, unlike the 273BC bug where one of the files got out of step during the 1.5 conversion (I'm pretty sure RTRPE still uses the events.txt file I edited to fix it...I'm so proud! That was my first bugfix for RTR.)

[FMvonKleist]

So to summarize, Quinn, I need to go into that file and delete all references to that event? Is that the only file needed fixing? Where is it located at? I have my own suspicions that it might be that event. Please elaborate briefly so I make sure to execute the proper deletions, so I may try this fix out for the benefit of all.

[Quinn Inuit]

Yes, but I recommend making backups first if that isn't it.

Easy way to find it:
Just do a search in your root RTR directory for "medica." Every file you find that has it, back up and then edit.

List:
Descr_events in data/world/map/campaign/imperialcampaign
historic_events and strat in data/text

[FMvonKleist]

Ah no worries, if it doesn't work, or does, it is all a reinstalll anyway. Edit is a special word for delete, right? LOL

[Quinn Inuit]

Yeah, or comment out. Your call.

[florin80]

Hi FMvonKleist! Long time no see. Darn about the crash. Please let us know how the above proposed fix worked. And also please attach a saved game for MC to take a look at it.

Also, can you tell us which of the two versions available are you using? The mod switch or the simple one? And, are you playing it via the BI.exe or the regular way?

@Quinn Inuit wouldn`t that edit require a campaign restart to take effect?

[Quinn Inuit]

...
@Quinn Inuit wouldn`t that edit require a campaign restart to take effect?

I don't know. Why would the game integrate the historic events files into its savegame? That seems like the sort of thing that would just get checked at the start of each turn.

[FMvonKleist]

when you say "comment" rather than delete, please explain. And secondly, I am running the simple one, no additional modifications. I have reinstalled again, pure. I want the test to be absolutely without a doubt. So give me a couple of weeks of play. LOL. At that point, if any trouble still exists, you will receive the file. We have to solve this issue. It is just silly to still have it, with the great job 1.8 is.

[florin80]

You don`t have the saved game anymore?

[AngryTitusPullo]

when you say "comment" rather than delete, please explain. And secondly, I am running the simple one, no additional modifications. I have reinstalled again, pure. I want the test to be absolutely without a doubt. So give me a couple of weeks of play. LOL. At that point, if any trouble still exists, you will receive the file. We have to solve this issue. It is just silly to still have it, with the great job 1.8 is.

By running the simple one I assume you're using the non mod:switch version and using the RTW.exe instead of BI.exe

If you already have BI installed maybe you can try running the last save game using the BI.exe and see if this problem still exist.

[Marcus Camillus]

Ok, I'm back, and my AI test campaign has run past the 66/67BC time frame with no CTD problem at that date. The campaign is currently at the Winter of 59BC.

I've got some new questions for you. This saved campaign that you are having CTD problems with, is it a new campaign that was started with RTRPE v1.8? If not, what version of RTRPE was it started with?

The reason I ask this is that the fix for the 66/67BC CTD problem requires a new campaign to be started for it to take effect. Saved campaigns from previous versions of RTRPE will not get the effect of this fix, along with several other fixes too. Its why I state in the RTRPE v1.8 Release and Download Links Info that the RTRPE v1.8 Release is not savegame compatible. Even though older saved campaigns may appear to work with RTRPE v1.8, several problems, including the 66/67BC CTD problem, will not be corrected unless you start a new campaign using a fresh RTRPE v1.8 install.

Now if this campaign was started with a fresh RTRPE v1.8 install, I would be greatly interested in getting a copy of a savegame file from a date before the CTD occurs at. I have not been able to recreate this problem with my testing of the RTRPE v1.8 release. Access to your savegame file would be invaluable for testing to find out what your CTD problem is.