• 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.
Status
Not open for further replies.
Found it. I fiddled around with the same save game I uploaded earlier. I can get past the 1 may 1940 date if I change the game's resolution :wacko:

I normally play the game in 1680*1050. In this resolution the game crashes at the declaration of war on the Netherlands by Germany at 0:00 2 may 1940. Playing at another resolution (1024*768 for example), I have no problem! The messagebox that Germany declares war on me pops up and the game continues to run.

Can anybody try the savegame in 1680*1050 and see if it crashes? This is really weird.

Edit: I switched to a low resolution to get past 1 may 1940. After that I saved and restarted from that point on again in 1680*1050. I played for a few weeks (Netherlands). My ass was handed to me by the German AI. Netherlands was conquered. Then, again CTD. I suspect the surrender event triggered. I just don't get it, what does resolution have to do with events that CTD???
 
Last edited:
Found it. I fiddled around with the same save game I uploaded earlier. I can get past the 1 may 1940 date if I change the game's resolution :wacko:

I normally play the game in 1680*1050. In this resolution the game crashes at the declaration of war on the Netherlands by Germany at 0:00 2 may 1940. Playing at another resolution (1024*768 for example), I have no problem! The messagebox that Germany declares war on me pops up and the game continues to run.

Can anybody try the savegame in 160*1050 and see if it crashes? This is really weird.

Edit: I switched to a low resolution to get past 1 may 1940. After that I saved and restarted from that point on again in 1680*1050. I played for a few weeks (Netherlands). My ass was handed to me by the German AI. Netherlands was conquered. Then, again CTD. I suspect the surrender event triggered. I just don't get it, what does resolution have to do with events that CTD???

This might actually be a very interesting cue...
I will be testing now...
EDIT: CONFIRMED! i got crash!

@Prioniere what resolutions do you run?
 
This might actually be a very interesting cue...
I will be testing now...
EDIT: CONFIRMED! i got crash!

@Prioniere what resolutions do you run?
Thank God! Confirmed. Good luck solving this little mysterie :)

Edit: Almost forgot Lennartos, you did see the insane numbers of lost convoys and escorts of Nat China in my savegame?
 
Last edited:
CTD in Mid-June 1940 (Vichy event has already happened, as has US Gearing up for war.) Playing 1936 scenario as USA.

Save game (autosave) file attached.
 

Attachments

  • savegame.zip
    1,8 MB · Views: 19
Screwing around as Cuba in a 1936 game. It's 1949 and I'm finally ready to attack the Dominican Republic. I land, launch an attack on their capital, and instantaneously crash.

I doubt a savegame will help, so I won't bother. I was attacking with two infantry divisions with attached engineer brigades and a cavalry division with an artillery brigade.
 
Last edited:
timeglitch.jpg


Initial orders to attack and such were fine but shortly after all of them went batshit to say the least, similiar to the stuff reported earlier.

Edit: CTD when attempting to issue ground attack orders in 1940. So far singular case. However prior the CTD using the mission menu next to the division's commander did allow you to use proper timetables for attack without any issues.
 
Last edited:
upgraded production message

When a new tech is discovered for an ongoing production, there is now a message, which is good.

But it seems it does not worl perfectly.

As ENG, i began INT lvl 2 production and refused to upgrade line when I found INT lvl3 tech.
But now, as soon as i find a new tech (any one) I still have message that I can upgrade.
Is it WAD? Guess not...
 
This might actually be a very interesting cue...
I will be testing now...
EDIT: CONFIRMED! i got crash!

@Prioniere what resolutions do you run?

Pioniere
1024X768 16Bit color is what I use in the game. My PC uses 1024X768 32Bit color. The game is from 2010 a little strange that cant sett it to 32bit. I guess the game wont need that many color.
 
resolutions

I tried earlier with the other beta patch to sett resolution from the PC at 16 bit colors but that didn't do the trick.

(It looks like that I can only use window mode when I change the PC
resolution to 16 bit color.) maybe its time for to update the graphic drivers. last time I did that was late January.
 
Last edited:
So far mentioned:
-double production cost of INFRA
-brigade production cannot be sped up.

Is there is a list of all changes somewhere?

They have added Motorised Engineers and Trucks brigades. So far Motorised Engineers won't differ from regular engineer other than they don't seem to have the dig in bonus but they give +1 to max speed while trucks acts as very rough motorisation.
 
Just fixed the 1940 CTD - again a tricky one... :p
Please see first thread for hotfix


So the last known bug in 105 is the date one...
I need more data on how to replicate it.
(also please do so wth the hotfix)
 
Day\Night seems to be mixed for aerial units. If I set E.G. order to bomb certain area for 4x days for day they are doing night bombing runs while doing night actually results into daytime bombardments or the ingame clock is just messed up somehow.

Any attack order I issue after 1940 (not sure of the exact date, other than it's 1940) results into CTD and the very brief moment you see the year, hours, date and UNKNOWN STRING WANTED well they're literally batshit crazy :rofl:
 
Last edited:
I know you weren't specifically trying to solve this issue but my inability to reload a savegame without crash is still unresolved by the high resolutions hotfix. I can reproduce it by loading as the USA in 1944 or 1945, saving the game immediately and then exit and try to reload my save. It crashes every time. I have the trial for 1.05 installed on a separate directory not connected to Program Files.
 
I unfortunately find this patch unusable. I cannot save games any more unless I run as administrator. But then I notice something else--when I try to reload my saved games it crashes. If I try Germany 1936 and do a save everything works fine. But then if I try USA 1944 and save I cannot reload my save. It seems as though the new executable has a limit on how much it can read and if that limit is exceeded--CTD.

Vista is jerking your chain my friend. You need to make vista allow AOD to operate freely and never install it in program files. I find vista to create problems out of nothing just to piss you off.
 
Actually I have Windows 7 and I tried installing the game in another folder and that did not work either. If I install in another folder I do not have to run as Administrator to save a game. However, the crash on reload of a savegame persists.
The inability to save games without running as Administrator and the inability to reload a savegame are two bugs INTRODUCED by 1.05B3.
As far as the savegame issue is concerned, what AOD 1.02 through 1.04 did was to save the savegames in a compatibility folder, so the Administrator Rights issue is only apparent if you have to go look for a savegame to patch it.
 
Last edited:
Actually I have Windows 7 and I tried installing the game in another folder and that did not work either. If I install in another folder I do not have to run as Administrator to save a game. However, the crash on reload of a savegame persists.
The inability to save games without running as Administrator and the inability to reload a savegame are two bugs INTRODUCED by 1.05B3.
As far as the savegame issue is concerned, what AOD 1.02 through 1.04 did was to save the savegames in a compatibility folder, so the Administrator Rights issue is only apparent if you have to go look for a savegame to patch it.

Crash while loading savegame found and fixed.

Still need some infos on how to recreate the time/date bug
 
CTD japan game

Lennartos have you looked into my CTD savegame?
 
Status
Not open for further replies.