Home Trending Latest threads New posts Developer diaries

Constant GAME CRASH in january 1750 (or later)

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.
Show only dev responses
unmerged(677)

unmerged(677)

Family man
Jan 10, 2001
47
0
www.myspace.com
Constant GAME CRASH in january 1710

I'm playing Guyarat (Grand Campaign) and my game keeps crashing around 6-10 january 1710. I've tried to load the game and start as another country (Hderabad, Algiers etc. etc) BUT the same thing happends. This is really frustrating as I've spent days on this particular game.

Any help? Hints? Magic? :(

//Valdi
 
This problem is known, and I've now found out why.

It is because of native raids on small fortified colonies, where the colony is burned down before siege is finished.

This will be fixed in the next patch.
 
Re: Constant GAME CRASH in january 1710

Originally posted by valdi
I'm playing Guyarat (Grand Campaign) and my game keeps crashing around 6-10 january 1710. I've tried to load the game and start as another country (Hderabad, Algiers etc. etc) BUT the same thing happends. This is really frustrating as I've spent days on this particular game.

Any help? Hints? Magic? :(

//Valdi
Click to expand...

save your game in early january, restart the game and play at 1 min=1month or 4month max. The game will probably crash at a later date, so save every month and reload when it crashes. It's the only work-around I'm aware of now, until the patch is released.
 
1750 Jan 1 CTD

Hi

I read a thread in the EU2 Bug department about quite a few players who had CTD in EU2 at jan 1 (or a few days later) 1750.

Playing as Sweden my game also chrashed at jan 1 1750! This can't be a coincident.

I play on W2000 professional with 128Mb RAM.

I made some tries and once I got past that date and could play a few years more but then it chrashed again. It just chrases either before you can do anything or a few days after you have stated it. Before that I only had one single CTD (in the mid 1600's, after an civil war broke out, which I never got after the reload so that was a nice CTD indeed!) and then I just started the game again and it played on nicely.

I had started the game on EU2 1.01 and then installed 1.02 (the first one issued) and continued playing.

This was very sad for me because I had taken one week's vacation from the job just to play EU2. Yes, that is true, I am an addict if there ever was one. Well, now I have installed the correct 1.02 patch and started a new game as Aragon. I will be furious if it crashes around 1750 again. BTW I play about 6 hours each day and this early in the game that means 15-20 years per day so it will probably take a month before I am there.

If anyone want to see a saved game I have the file saved and can email it.

Yours
Daniel
 
Further comments

Thx all for your quick answers!
I eventually passed by using the last autosave (my own saves always crashed) and minimizing the game speed.

What I notice is that I in this game, when I save the game, it'll crash when loaded. But I'm able to "reload" the autosave at minimal game speed.

Berst regards,
Valdi
 
Daniel,

I have moved your thread here so you could see the solution.
 
Last edited:
but...

I'm overjoyed to see that the 1750 bug is going to be fixed in 1.03. However, I have two questions:

1. How is it possible that this sort of problem doesn't show up on some peoples' systems? If it's an internal bug that has to do with an event (something about burning down trading posts) which has nothing to do with graphics or sound, then what could the hardware possibly have to do with it?

2. Does anyone know if campaigns in progress will have to be restarted in order for the fix to take effect?

Thanks!

-Raphael
 
Re: but...

Originally posted by Raphael75
I'm overjoyed to see that the 1750 bug is going to be fixed in 1.03. However, I have two questions:

1. How is it possible that this sort of problem doesn't show up on some peoples' systems? If it's an internal bug that has to do with an event (something about burning down trading posts) which has nothing to do with graphics or sound, then what could the hardware possibly have to do with it?

2. Does anyone know if campaigns in progress will have to be restarted in order for the fix to take effect?

Thanks!

-Raphael
Click to expand...

1. I would say a part of it is random. Sometimes it will occur (the small fort being taken before the siege is over) and sometimes it won't.
2. For this particular problem no. But the next patch will include other fixes and possibly more events that might require you to start a new game to fully enjoy the benefits of the game.
 
Re: Re: Constant GAME CRASH in january 1710

Originally posted by viper37


save your game in early january, restart the game and play at 1 min=1month or 4month max. The game will probably crash at a later date, so save every month and reload when it crashes. It's the only work-around I'm aware of now, until the patch is released.
Click to expand...

Hi

If it is my own colony that is attacked I could go back to an earlier save (I always save a lot of saves) and send a troup to that colony which will defeat the rebels).

Could Johan please tell us if this is the case, then we have another workaround.

As Aragon/Spain I have now reached the 1660:s (averaging 6 hours play per day but only 1 year per hour) I am still some time from this dreaded date of Jan 1st 1750 but I am getting closer and no news about 1.03 yet.

Johan, please say it is a rebellion in my own colony, please.....

Yours
Daniel
 
Originally posted by Johan
This problem is known, and I've now found out why.

It is because of native raids on small fortified colonies, where the colony is burned down before siege is finished.

This will be fixed in the next patch.
Click to expand...

Hi Johan

This sounds strange. How can you know this is his (and mine) problem? Is there a hardcoded rebellion taking place somewhere around Jan 1st 1750 in a small fortified colony? But I sure hope you are right.

Yours
Daniel
 
the rebellion can be anywhere in the world, not necessarly in your colony. There are events creating rebellions somewhere.
 
Originally posted by viper37
the rebellion can be anywhere in the world, not necessarly in your colony. There are events creating rebellions somewhere.
Click to expand...

Coming to think about it. In my present GC it is the year 1667. I already own almost all colonies there are in the world. There are a few white spaces in America but to my knowledge there are no more provinces left to colonolise in the whole world, and if there yet were any they at any rate will be mine by the year 1750 so then I will get a message box telling me where it takes place and I can whipe them out immediately. Ha, that's a "work around" for sure!

Thanks Viper for clarifying this issue and putting my brain on the right track how to solve this problem.

Daniel
 
Originally posted by Daniel A


Coming to think about it. In my present GC it is the year 1667. I already own almost all colonies there are in the world. There are a few white spaces in America but to my knowledge there are no more provinces left to colonolise in the whole world, and if there yet were any they at any rate will be mine by the year 1750 so then I will get a message box telling me where it takes place and I can whipe them out immediately. Ha, that's a "work around" for sure!

Thanks Viper for clarifying this issue and putting my brain on the right track how to solve this problem.

Daniel
Click to expand...

most likely if you manage to do it fast enough, yes it would work. But the other work-around is to reduce the speed.
 
didn't work

most likely if you manage to do it fast enough, yes it would work. But the other work-around is to reduce the speed.
Click to expand...

I'm telling you, this did not work for me. I've tried pausing and setting the speed to every setting, and it always crashes like 5 seconds later.

I just wish it would crash in like 1420 so you would't have to spend hours and hours on a game and get 3/4ths of the way through and then be stuck. When is 1.03 coming out??????
 
Re: didn't work

Originally posted by Raphael75


I'm telling you, this did not work for me. I've tried pausing and setting the speed to every setting, and it always crashes like 5 seconds later.

I just wish it would crash in like 1420 so you would't have to spend hours and hours on a game and get 3/4ths of the way through and then be stuck. When is 1.03 coming out??????
Click to expand...

1.03 should be available for public within a month or so. The patch isn't ready yet as beta testers still have more testing to do and there are still some more stuff to correct and add. This crash was only a minor issue compared to the rest that happenned after that :D
 
Re: Re: didn't work

Originally posted by viper37


1.03 should be available for public within a month or so. The patch isn't ready yet as beta testers still have more testing to do and there are still some more stuff to correct and add. This crash was only a minor issue compared to the rest that happenned after that :D
Click to expand...

I am not sure I understand this correctly. Do you mean to say that if we use the slow down pace work around there will be a lot more bad things, of _major_ importance (how anythig can be more major than a CTD :) that are related to this specific bug? If that is the case it appears we have better skip this work around method or we will get grey hair.

Or do you mean that whether we have this specific bug or not there is a (great/small) risk there will be many more major CTD for other reasons in the late years of the game...

As I have said, I spend 6-7 hours each day at the speed of 1 hour = 1 year. I don't want my new 1.02 game to CTD and be unplayable when I reach the mid 18th century and onwards, not another one (the first one was 1.00 pathced up to the bad 1.02).

Yours
Daniel
 
Re: Re: Re: didn't work

Originally posted by Daniel A


I am not sure I understand this correctly. Do you mean to say that if we use the slow down pace work around there will be a lot more bad things, of _major_ importance (how anythig can be more major than a CTD :) that are related to this specific bug? If that is the case it appears we have better skip this work around method or we will get grey hair.

Or do you mean that whether we have this specific bug or not there is a (great/small) risk there will be many more major CTD for other reasons in the late years of the game...

As I have said, I spend 6-7 hours each day at the speed of 1 hour = 1 year. I don't want my new 1.02 game to CTD and be unplayable when I reach the mid 18th century and onwards, not another one (the first one was 1.00 pathced up to the bad 1.02).

Yours
Daniel
Click to expand...

I meant that the patch can't be released immediatly because there are multiple serious bugs that were discovered in the latest days by the beta testers. Your version of the game is not affected, it's something that was added to what will be patch 1.03. Therefore, don't expect the patch for next week, it's going to take a little while.

Generally, saving the game each month starting in January and reducing the speed to 1min=1month, the game will crash later. Then, you just reload the game you saved on April 1st for example and it goes to June or July before crashing, then you reload the game you saved at the beginning of the month, etc.

This is what I have done with other games that were sent to me to circumvent the problem. It is a pain in the you know where, but it was the only work to keep playing.

So, if it is still crashing and nothing is to be done, backup your save game and you'll play once 1.03 is released. In the mean time, you can try one of the other scenarios or start a new GC were hopefully the problem might not occur.
 
Originally posted by Johan
This problem is known, and I've now found out why.

It is because of native raids on small fortified colonies, where the colony is burned down before siege is finished.

This will be fixed in the next patch.
Click to expand...

Has anyone else seen this issue without the above mentioned situation
occurring? This is happening in my game and, while I do have colonies, I have not had any sieges from natives on them.

thanks,
Kevin
 
the siege might be elsewhere, in a province not under your control.
 
You must log in or register to reply here.
Top Bottom
Back