Home Trending Latest threads New posts Developer diaries

Reproduceable Crash in EU2 GC -

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
unmerged(3466)

unmerged(3466)

Captain
Apr 28, 2001
388
0
Visit site
I've run into a problem in a GC game (EU2, 1.01).

I'm at 1750 in a game as Milan, but the game will now always crash on about January 9th (I have the autosave). I've tried runing with no sound, running at the slowest speed, etc., but this appears to be some kind of internal thing, not a hardware issue. The fact that I've played from 1419-1750 with only one or two random CTD's would seem to support this.

I have a PIII/500 with 128M running Win98, for the record.

I'm not really concerned with continuing that game, and mainly posted to offer the saved game up for potentially finding and fixing the problem in future patches. Run it through with the debug code going, etc.

Austria is a monster in this one, having diploannexed both Poland & Lituania, Venice, a 4 province Bosnia, and inherited Hungary & Bohemia. I think Russia is afraid to declare war, and France certainly is. I had to wrest Venice and Istria from their grasp to free my Italian brothers, though.

The Ottoman Empire put up a sorry fight, and was ultimately diploannexed by Oman. I think the Macedonian capital makes them too easy to smack around.

Anywho, I can supply the saved game files (there seem to be two associated) to wherever it needs to go, or further test it here if anyone has any ideas.

It has crashed on cue about ten times so far, and I've played around with a couple of other EU2 games in between tries without this type of issue.

- Raife
 
First, keep your savegame, it can be useful.

Second, try disabling the autosave to see if you have the same problem.
 
Hi Raife.

there are 2 things that need to be done wich seem to address some issues.

1) kill all TSR's (CTRL+ALT+DEL end task all except for systray and explorer) if you are running NT or 2k then you need to use a different approach.


2) disable the joystick also defrag your hard disk. not to mention upgrade your drivers.


cheers
 
viper:
Yep, I have the autosave backed up in another folder. I'm not sure what you mean by disabling it helping, though. I used yearly autosave for about a week without any problems. It seems to be an internal problem with processing the events/AI's moves. It always happens on the 9th/10th of the January of the 1750 autosave, after the Portugal's Marquis de Pombal event (6th?). Portugal had annexed Castille earlier (Aragon's still around, Castille went with the 'Keep Castille' option in 'Viva Espana'), so there may be some conflict. Seems like another potential late-game crash bug. The first time it happened it wasn't after a reload, it was during normal play (after about an hour). I figured it was a random CTD, and reloading would clear it up. It's completely consistent, though.

Since I got from 1419 to 1750 over several gaming sessions, I'm not sure how disabling future autosaves would help in this instance. Nevertheless, I just tried again with it switched off (along with sound and music), and it crashed again.

Nabil:
I do and have disabled all TSR's before playing, keeping only Systray & Explorer active. It's a good frustration-saving gaming habit, regardless. As I said, I'm running Win98.

I did have a joystick plugged in, so I pulled that and tried again. It still crashes on cue.

I've since played through about 100 years as the Palitinat in an Age of Exploration game. Everything works fine.

I do defrag regularly, usually after clearing out a bunch of old games.

As I said, I can supply a copy of the autosave. If it crashes for you folks, then it's certainlty not system-specific.

- Raife
 
Originally posted by Raife
viper:
Yep, I have the autosave backed up in another folder. I'm not sure what you mean by disabling it helping, though. I used yearly autosave for about a week without any problems. It seems to be an internal problem with processing the events/AI's moves. It always happens on the 9th/10th of the January of the 1750 autosave, after the Portugal's Marquis de Pombal event (6th?). Portugal had annexed Castille earlier (Aragon's still around, Castille went with the 'Keep Castille' option in 'Viva Espana'), so there may be some conflict. Seems like another potential late-game crash bug. The first time it happened it wasn't after a reload, it was during normal play (after about an hour). I figured it was a random CTD, and reloading would clear it up. It's completely consistent, though.
- Raife
Click to expand...

My mistake. I thought the game was crashing upon saving with the autosave in january, and the crash happenned just after that; on my machine, after the January 1st, I jump to January 11th (full speed), so I thought that on your machine it was the same but on the 9th.

As I doubt something so specific could be machine related, I am going to ask you to send me the file by e-mail. I will send you a private message about it. It might not crash on my machine because I have a later version, but if it does, I will send it to Johan and he will fix this (he always fix things :D )
 
Ok, sent.

Thanks viper.


- Raife
 
I have the same problem

I chose to play Novgorod. There are many random CTD's throughout the game and like Raife I just reload and it seems to be ok. I have also gotten several hard crashes where I have to reboot. Admitedly I should update my drivers, I don't have net access now at home so I am winging it.

I am also getting a date-related CTD, so it might not be anything hardware/driver related after all, unless a special visual effect or driver is called at this date.

For me it crashes Feb. 15th, 1568... again and again...
:(
 
Originally posted by Raife
Ok, sent.

Thanks viper.


- Raife
Click to expand...

Raife, I have loaded your game and it works fine on my comp. However, I did notice something strange: When I go to the loading screen, there are two Milan to be chosen.

I'm going to have you edit the save game file and try again.

Open it in Wordpad. In the first few lines, you will see the following:
MLO = {
desc = "MLO_DESC"
picture = "scenarios\data\latin_data.bmp"
countrytactics = "MLO_DESC"
missioncountry = ""
missiontactics = ""
playername = "Milan : HVWYT"
countrydifficulty = 3
countryeconomy = 2
countrymilitary = 2
countrydiplomacy = 3
missiontype = -21

if you have two identical entries as I have, delete one.

Your game runs fine on my system, so I suspect it's a weird bug that got fixed in the latest beta patch. That's the good news :) The bad one is that I don't know when the patch will be out, so in the meantime, if it still doesn't work, you'll have no choice but to try a game with a different country :(
 
Re: I have the same problem

Originally posted by Riurik
I chose to play Novgorod. There are many random CTD's throughout the game and like Raife I just reload and it seems to be ok. I have also gotten several hard crashes where I have to reboot. Admitedly I should update my drivers, I don't have net access now at home so I am winging it.

I am also getting a date-related CTD, so it might not be anything hardware/driver related after all, unless a special visual effect or driver is called at this date.

For me it crashes Feb. 15th, 1568... again and again...
:(
Click to expand...

Try the latest drivers first, it might be that, even if it's date related.
 
Thanks viper, it worked fine after I deleted the duplicate Milan.

That's been like that since the very beginning, so I'm not sure why it suddenly started crashing, but hey, it's working, so I'm not complaining.

I did shuffle around the majors before starting that game, though there were definitely not two Milans when I hit 'Start.' I think one was Austria, actually. I had switched China (I think) to Milan first, then swapped it with Austria to have it on the end. This was all in-game, though. Somehow Milan ended up in there twice. Weird.

I thought about editing one out in the save, but didn't really feel comfortable messing with it.

Anyway, it works now. Thanks again.

- Raife
 
I'm glad it worked.

I know it's weird, but I have no idea why it was like that.
 
You must log in or register to reply here.
Top Bottom
Back