Matrix Games Forums

Have a repeatable CTD from a save file [:(]. I have the two files in a zip, who do I mail them to?


This was the error message info, don't know if it helps, but maybe it will.

AppName: forge of freedom.exe AppVer: 0.8.1.0 ModName: maps.dll
ModVer: 0.0.0.0 Offset: 000051a1

Please send the zip to ericbabe@west-civ.com.  Thanks!

On it's way!

FYI, I was able to continue with my session by restarting the game and picking autosave3 or autosave4, don't remember which. Selecting the file "autosave" would give me the repeatable CTD of course.

Just as a heads up I got another CTD about three hours and three game years later. It was very, very late at night [;)] so I went to bed. I'll see if I can recover using a previous autosave.

Second CTD save is on it's way to you, too.

Regarding the second save, it's repeatable even from older autosave. The crash occurs right after I get the message the Little Rock has fallen after being besieged.

UPDATE: Yup, that looks like the smoking gun. I went back to a save about two turns previous and lifted the seige of Little Rock, so it wasn't taken. And guess what? Little Rock disappeared! It's not on the map anymore. Maybe that's what was causing the CTD, the fact that if I won the siege there was suddenly no city to occupy. Oops!

ORIGINAL: Temple

Regarding the second save, it's repeatable even from older autosave. The crash occurs right after I get the message the Little Rock has fallen after being besieged.

UPDATE: Yup, that looks like the smoking gun. I went back to a save about two turns previous and lifted the seige of Little Rock, so it wasn't taken. And guess what? Little Rock disappeared! It's not on the map anymore. Maybe that's what was causing the CTD, the fact that if I won the siege there was suddenly no city to occupy. Oops!

And I thought Sherman was bad...

Sam

Okay, everyone, until you hear otherwise, besiege Little Rock at your own peril...

I've also got a repeatable CTD involving a siege.  I was besieging Knoxville with four separate divisions.  Several turns ago, I told one division to start a siege of knoxville and then told another one as well.  Now, when Knoxville falls, I get the typical City has fallen pop-up window TWICE.  Then I get the CTD.  I suspect it was because I told two divisions to besiege the city on the same turn.  If I had only ever instructed one, I think it would have been okay.  I am emailing the zipped file of the autosave to Eric. 

Thanks. That's the third siege-related problem to have been reported. Which is strange, because sieges got a good deal of testing during beta. I'll be curious to know what Eric discovers.

ORIGINAL: Gil R.

Thanks. That's the third siege-related problem to have been reported. Which is strange, because sieges got a good deal of testing during beta. I'll be curious to know what Eric discovers.

Now to be sure I had a lot of sieges that didn't cause a CTD, so if I get another I'll pay particular attention to the circumstances.

ORIGINAL: Temple

ORIGINAL: Gil R.

Thanks. That's the third siege-related problem to have been reported. Which is strange, because sieges got a good deal of testing during beta. I'll be curious to know what Eric discovers.

Now to be sure I had a lot of sieges that didn't cause a CTD, so if I get another I'll pay particular attention to the circumstances.

So far it has just happened in Little Rock and Knoxville? Is it possible that the game gives up on people who bother to lay siege to cities no reasonable person would ever want?

/ducks and runs away... [8|]

Same thing, Crash to Desktop.  Didn't record or see the error message in detail.  Do notice the game plays a little buggy.
 
Hopefully, we will see a patch soon.  Nice game, but not too stable at the moment.

ORIGINAL: Texican

Same thing, Crash to Desktop. Didn't record or see the error message in detail. Do notice the game plays a little buggy.

Hopefully, we will see a patch soon. Nice game, but not too stable at the moment.

What do you mean by "same thing"? What happened, and do you have a save file? And what are your system specs?

ORIGINAL: jchastain

ORIGINAL: Temple

ORIGINAL: Gil R.

Thanks. That's the third siege-related problem to have been reported. Which is strange, because sieges got a good deal of testing during beta. I'll be curious to know what Eric discovers.

Now to be sure I had a lot of sieges that didn't cause a CTD, so if I get another I'll pay particular attention to the circumstances.

So far it has just happened in Little Rock and Knoxville? Is it possible that the game gives up on people who bother to lay siege to cities no reasonable person would ever want?

/ducks and runs away... [8|]

Also happened to me in Annapolis with both Ft. Carroll and Ft. Madison.

Please send save-files to Eric (ericbabe@west-civ.com) so that we can figure out just what's happening. Send the most recent save or autosave files, but be sure to zip them. Thanks!

I"m getting the same siege crash bug. Happens right after I get the message saying I've captured Wheeling. I have a save file if it is needed.

Edit: I've sent a save file with the bug to Eric.

ORIGINAL: Gil R.

ORIGINAL: Texican

Same thing, Crash to Desktop. Didn't record or see the error message in detail. Do notice the game plays a little buggy.

Hopefully, we will see a patch soon. Nice game, but not too stable at the moment.

What do you mean by "same thing"? What happened, and do you have a save file? And what are your system specs?

I have besieged a bunch of forts in a row (3 before besieging Annapolis). During the last siege, I got a Microsoft error that the application encountered a problem and would now close. The Microsoft error that gives you an option to report to Microsoft or just close it out.

Also, during an earlier game tonight, I tried to move some armies and when I pointed my cursor at other provinces, I did not see the arrow path as I normally would.

Earlier than that, during another tryout of this game, I had the screen freeze up after leaving the application unattended for a few minutes.

No, I never saved any file, but my system specs are pretty good. AMD 3500, Nvidia 7800 graphics card, 2 MB Corsair CAS2 RAM, etc... Basically, a nice machine for games; can run lots of RPG's at max graphics and almost zero lag.

ORIGINAL: Gil R.

Please send save-files to Eric (ericbabe@west-civ.com) so that we can figure out just what's happening. Send the most recent save or autosave files, but be sure to zip them. Thanks!

FYI...I experienced the CTD when laying siege to Ft. Carroll and Ft. Madison (Annapolis)with three armys , two on Ft. Carroll and one on Ft. Madison. Went back to my saved game and adjusted the orders to have only one army on Ft. Carroll and one on Ft. Madison. Ran fine w/ no CTD. I will try to send save ASAP.

One is not supposed to besiege more than one fort in a province at the same time, and only after one has captured any forts in a province can a city be attacked. This might be causing the problem.

Has anyone had a crash occur during a siege of a single target?

For now, therefore, siege one fort at a time, and only then move on to the city. Until Eric says otherwise.

So it appears that this is not really a bug, so much as a game design issue. The game was not intended to let multiple sieges be conducted in a province simultaneously, but there is no code to prevent someone from attempting it. My guess is that if you follow my boldface recommendation many of these crashes that are making some people claim the system is unstable will go away.