GalCiv crashed in diplomacy screen

I was moving the money slider for the Aeceans (the last of the 5 civs I was selling techs to that turn) and.... zzzt. The game crashed. No error, just back to the desktop.

I'm running a 2.2GHz Pentium IV with a GE-Force4, 512 Mb Ram and Windows XP Professional.

Oh, and I'm running the latest patch.

~SDC~
254 views 10 replies
Reply #1 Top
if you're having lots of CTD's you might want to run the Smartexception program you can download in the Free Stuff tab under software in Stardock central. Run it while you run the game.

~SDC~
Reply #2 Top
Well, I've just had one so far. If I get another one I'll do that.

But from now on I'm putting the 'auto-save' to every turn!
Reply #3 Top
I started getting a lot of crashes in the latest build as well, in the diplomacy screen. I never had any problems with crashes in previous builds, so I'm guessing maybe something new in with this latest patch?
Reply #4 Top
The couple times I've had this happen to me, I noticed I was trying to use the slider when they had under 100bc. (the default slider position) When I type in the number instead, everything works fine.

Can't say that's the problem till I try it a few more times, but I guess we'll see.

~SDC~
Reply #5 Top
Just tested on a few saved games I had, and that's exactly what it is. Talked to a minor race with 250bc. I made a trade to bring em down to 90... everything worked fine. Tried another trade and used the slider... crash to desktop. So, I guess check their cash before usin the slider till it gets patched.

Not saying this is the only problem, but I can recreate this one 100%

~SDC~
Reply #6 Top
Gweedo53, thanks for figuring that out. It caught me completely off guard so I could not remember the details that you guys noticed.
Reply #10 Top
Midnightsun,
well I imagine that Brad (or someone) didn't consider this possibility when he was changing the update code to trigger off of the slider updates. And since he was just in there, he probably knows exactly what to change. As a programmer, I can tell you that this happens a lot more than is let on :p

Most likely, the programmer was doing a Homeric DOH! as soon as he heard about this problem. ;)