Armageddon 1.3 Beta 2 (24/04/2009) is now up (general comments/questions only please)

[xtfoster]

Thanck you man! There was the problem! After reinstalling over 10 times and trying different patch sequences I gave up yesterday, and today you give me the solution

I was playing with spanish language.

Please patch developers try changing the language to see if you got CTD

OK, I just switched to spanish and played for about 6 (game) months without a CTD. Some more info would be helpful.

1) What country were you playing as?
2) What date was the error occuring on?

 

[Modo]

The port problem is basicly a problem with the AI sending ships into port to repair,

True, but that is only one part of the problem. The other part is the AI placing its brand new fleets (the ones not ready for missions, so basically immobile) too close to enemy lines. This seems extremely bad for Britain, and possibly Germany, since their cores are in danger almost since the beginning of the war. While Japan or the USA has its cores far from immediate danger, the Brits basically put new ships at the mercy of enemy planes. Note that putting ships in northern England or in the Baltic would be an easy way to avoing German/British tactical bombers respectively, let alone CAS. Can that be changed via the AI files, perhaps?

 

[unmerged(93833)]

OK, I just switched to spanish and played for about 6 (game) months without a CTD. Some more info would be helpful.

1) What country were you playing as?
2) What date was the error occuring on?

I was playing as germany 1936, CTD were somewhat random in dates, but usually by putting the highest speed in less than 3 minutes in real time (allways way before spanish civil war in 1936) the game crashed. Tried loading an old savegame from 1.3beta1 and in about 2-3 weeks the game crashed. With every nation happened the same.

After changing the language to english the gameplay is perfect, no CTD at all.

 

[xtfoster]

I was playing as germany 1936, CTD were somewhat random in dates, but usually by putting the highest speed in less than 3 minutes in real time (allways way before spanish civil war in 1936) the game crashed. Tried loading an old savegame from 1.3beta1 and in about 2-3 weeks the game crashed. With every nation happened the same.

After changing the language to english the gameplay is perfect, no CTD at all.

Well, I'm able to reproduce it, and it is probably caused by an event text, but other than that, I have no idea on how to fix it...

 

[ADukes]

Use the beta 1 CSV config files and replace them one by one with the files from beta 2 to find out where the messed up strings are located.

 

[CharonJr]

Hmm, ok, so basically for now house rules that prevent bombing of already damaged fleets are the only way to go.

BTW, the AI is sometimes able to protect itself when it (incidentally?) puts about 60 RN in one port, even with escorted bombers the bombers are in for a world of pain if they attack

But telling the UK to build new ships/assemble its fleet in e.g. Scapa after France has fallen would be nice anyway if it can be implemented.

CharonJr

 

[MartinBG]

But telling the UK to build new ships/assemble its fleet in e.g. Scapa after France has fallen would be nice anyway if it can be implemented.

AFAIK this can be changed from AI files, but better someone with more modding experience to comment.

Well, I'm able to reproduce it, and it is probably caused by an event text, but other than that, I have no idea on how to fix it...

My guess is that it is not an event but a (spy) message or on-screen text that miss %s or %d somewhere.

ADukes, using files from beta 1 could make the things even worse because there are many changed message formats.

I will take a closer look on this problem later this week.

 

[ADukes]

My guess is that it is not an event but a (spy) message or on-screen text that miss %s or %d somewhere.

Most of the time it's the opposite, not missing but one too much.

 

[unmerged(93833)]

AFAIK this can be changed from AI files, but better someone with more modding experience to comment.




My guess is that it is not an event but a (spy) message or on-screen text that miss %s or %d somewhere.

ADukes, using files from beta 1 could make the things even worse because there are many changed message formats.

I will take a closer look on this problem later this week.

One thing I tried was overwriting the .exe file from beta2 with the one in beta1 and got no problems, but obviously I lost the AI tweaks...

I hope it helps

 

[ozman2]

A suggestion to try and see if this resolves the German and Spanish language crashing is to keep all the ARMA 1.3 beta1 csv files EXCEPT doomsdaytext.csv. Do a test run and see if this works. Then we can at least narrow down the problem. I'm hesitant to release any upgrades to my own mod until the crash issue is resolved and I hope a resolution can be found soon and a new beta2 download is released ASAP.

If this does not resolve the issue then doomsdaytext.csv is the issue, and it is essential to have a bugfree edition of that file--otherwise you'll get a bunch of unwanted string errors, because they changed the spy messages. So take a good hard look at that section as well.

The new spy messages concern spy activities against YOUR country and they start with SPY2. It might be worth a diagnostic try to patch this section into the beta1 doomsdaytext.csv file.

Let me know if any of these answers solves your problem. Of course always make sure you have the originals backed up in some fashion.

 

[CSABadass]

icl_1936.ai file is missing the lines


military =
{
relative_build_scheme = no
max_batch_peace = 360
max_batch_war = 180
max_batch_home_front = 180

CTD for liberated Iceland games.

Regards.

The guy who fucked it up to begin with tries a fix:

You can download a corrected file here: http://www.savefile.com/files/2085370

 

[ozman2]

CSABadass,
You're still missing an end parenthesis somewhere.

 

[CSABadass]

CSABadass,
You're still missing an end parenthesis somewhere.

I couldn't find any, and this version loads up and runs fine for me.

Still, gave it another shot above, just in case.

 

[ozman2]

The one I've just downloaded looks fine--the number of parentheses and end-parentheses exactly matches. The inline text displayed on the forum has a mismatch. So I'd direct people to download your file.

 

[CSABadass]

The one I've just downloaded looks fine--the number of parentheses and end-parentheses exactly matches. The inline text displayed on the forum has a mismatch. So I'd direct people to download your file.

Thank you very much for helping me fix this!

 

[e_quality]

Later start dates for US leadership?

Sorry if this has been commented on before, but with the beta2 patch plenty of my USA land leaders have new and different start dates. Patton, for example, now starts in 1939 and was earlier available from 1936. The same goes for several naval leaders as well.

How comes? And, assuming this is WAD, what is the patch team's new organizing principle behind the later start dates?

(Not that I necessarily mind, only that I didn't catch that info from the change log).

 

[MartinBG]

Sorry if this has been commented on before, but with the beta2 patch plenty of my USA land leaders have new and different start dates. Patton, for example, now starts in 1939 and was earlier available from 1936. The same goes for several naval leaders as well.

How comes? And, assuming this is WAD, what is the patch team's new organizing principle behind the later start dates?

(Not that I necessarily mind, only that I didn't catch that info from the change log).

I think CSABadass could answer best on that because most (if not all) of the changes to US leaders are in result on his extended research on that subject.

 

[coreymas]

Sorry if this has been commented on before, but with the beta2 patch plenty of my USA land leaders have new and different start dates. Patton, for example, now starts in 1939 and was earlier available from 1936. The same goes for several naval leaders as well.

How comes? And, assuming this is WAD, what is the patch team's new organizing principle behind the later start dates?

(Not that I necessarily mind, only that I didn't catch that info from the change log).

Excerpt from the Wikipedia... assuming it is correct...

In the late 1930s, Patton was assigned command of Fort Myer, Virginia. Shortly after Germany's blitzkrieg attacks in Europe, Major General Adna Chaffee, the first Chief of the U.S. Army's newly-created Armored Force was finally able to convince Congress of the need for armored divisions. This led to the activation of the 1st and 2nd Armored Divisions in 1940. Colonel Patton was given command of the 2nd Armored Brigade, US 2nd Armored Division in July 1940. He became the assistant division commander the following October, and was promoted to brigadier general on the second day of that month. Patton served as the acting division commander from November 1940 until April 1941. He was promoted to major general on 4 April and made commanding general of the 2nd Armored Division seven days later.

Consider yourself lucky you get him at all in 39... should be only in 41 according to history.

 

[e_quality]

Consider yourself lucky you get him at all in 39... should be only in 41 according to history.

In a "normal" 1936 GC game, following a semi historical path, Patton can be available in '36, in '39 or in '41. I don't care as long as he's around when I need him. In such a campaign the US can do without ANY leader until '42, for that matter.

In an unhistorically early war however, these changes in the patch undoubtedly have increased the challenge a bit. Not necessarily a bad thing at all though.

 

[son of liberty]

More importantly, why was USA's only logistics wizard with general rank removed? Sommervell is normally one of 3 available generals in 36 and though only skill lvl1 was the important logistics wizard trait.