No Japanese aircraft production in any (production off) scenario!!!

[MadDawg]

Hi All,

Ive done a clean install, installed the patch, and started scenario 5 as the Japanese player for a PBEM. Ive notice that under the Aircraft Replacement Pool the rate at which planes are being built is set to '0' for all aircraft.

I dont know much about the production system for aircraft at all yet (which is actually off for this scenario) but I just wanted to check this is how it should be before continuing too far? This is only the second turn, so do the aircraft start to be produced some time into the scenario? Any ideas whats going on? [:)]

Dawg

[Drongo]

It's not just scenario 5. All the small map scenarios are like that.

Take note of the very large starting pools of Japanese a/c. It may be that this was the chosen design course rather than to give the Japs a monthly a/c build rate.

I've asked for confirmation in the development thread and if it is not what I mentioned above, I'll let you know in this thread.

[MadDawg]

Thanks Drongo,

I did notice the amount in the pool, but if this is the case it means that in scenario 5 I only have 51 A6M2's and 0 A6M3's to last for an 8 month campaign, which sounds a little odd to say the least.

Dawg

[mogami]

Hi, In Scenario 5 when you click on the intell screen and then bring up the Aircraft Replacement pool the column that is headed by "Replacement Rate" shows 28 A6M3 and 16 A6M2. THat is per month not total. The Production Rate is -
Replacements can be set by the designer in place of production or in addition to production.
But mostly production is only used in the large scenarios (where the Japanese player sets it)
If you run the Allies you'll notice he uses both. (There are allied aircraft that arrive via production and in the same scenario aircraft that have a replacement rate that does not include what is in the production system.)

Also there are over 300 A6M2/3 in the groups that either begin on map or arrive as reinforcements. There are 72 Oscars. (This does not include those that are on carriers that arrive later)

[Drongo]

ORIGINAL: Mogami
Hi, In Scenario 5 when you click on the intell screen and then bring up the Aircraft Replacement pool the column that is headed by "Replacement Rate" shows 28 A6M3 and 16 A6M2.

Well, mine has 0 under the replacement rate for all Jap aircraft types.

Either me or you have got the wrong version of the scenarios. [:)]

[coralsaw]

Same problem here. In the South Pac scenario, the a/c replacements rates are all 0, and the pool numbers seem warped. 50 odd zeros, and hundreds of transport a/c are a little odd. BTW, this was not the case before the patch, the same scenario had what seemed to be normal pool and rate numbers to last a year.

/coralsaw

[MadDawg]

Yup, I have a big fat zero too. This is a fresh reinstall with 1.20 installed over the top.

Dawg

[Nomad]

I took a quick look using the editor. Seems all the build rates are 0. [:(] New 1.20 version installed.

[MadDawg]

Hey could we get some feedback on this please?

Ive already spent hours setting setting this scenario up and doing the first couple of turns and all I want to know is if the game is working correctly or if this is another show stopper.

Dawg

[HawaiiFive-O]

Yikes! This certainly will put a damper on the small map scenarios.

I was reviewing Guadalcanal for my next possible PBEM, but no replacement planes doesn't sound like fun to me.

'Course the 'Return of the Battleship' might be fun to play too. [;)]

[Oliver Heindorf]

I have scen 4 started....no jap replacements at all, only in pool some A/C

The allied have replacement AC

no, I wont do this in a PBEM, boring for the jap then

[Bodhi]

If I'm correct in assuming that the aircraft replacement data is saved in the wpaXXX.dat file (XXX is the scenario#), then it appears that the ALL the restricted map scenario aircraft database files are identical to the one for scenario #15. This wasn't the case in the 1.10 files. As scenario#15 is set up for production and not replacements, this may be the cause of the problem.

Any possibility there's been a mistake in compiling the database files for the 1.20 patch?

[pry]

Yes there is a problem with replacements with all small map scenarios and it is solely my fault. 2By3 and Matrix are totally blameless.

I am sending in replacement files as I write this, hopefully they can be released as an emergency patch. I made a tragic mistake and error by overwriting all the scenario aircraft data files with the same copy, thus screwing the pooch big time for replacements for all small map scenarios.

I wish to make a public apology to everyone for this unforgivable error on my part, as I said 2by3 and Matrix are blameless.
No one in the world feels worse about this right now than I do right now. I am sorry.

[Tankerace]

Well, that's good to know then, at least it'll be fixed.

Of course, it seems Matrix needs to revamp its "Quality Control" to make sure this doesn't happen. It's not all your fault pry, if Matrix had done a better job of checking this, it wouldn't have happened.

[MadDawg]

Pry, no worries at all...your not getting paid for this and Im sure no one could hold it against you as mistakes happen! To be totally honest it shouldnt be your place to apologise at all....it should have been tested before being release which isnt your responsability to organise.

Any chance you could post it as an attachment for us so we can make use of it over this weekend?

Dawg

[HawaiiFive-O]

ORIGINAL: pry

Yes there is a problem with replacements with all small map scenarios and it is solely my fault. 2By3 and Matrix are totally blameless.

I am sending in replacement files as I write this, hopefully they can be released as an emergency patch. I made a tragic mistake and error by overwriting all the scenario aircraft data files with the same copy, thus screwing the pooch big time for replacements for all small map scenarios.

I wish to make a public apology to everyone for this unforgivable error on my part, as I said 2by3 and Matrix are blameless.
No one in the world feels worse about this right now than I do right now. I am sorry.

For me, it wasn't that big a deal. I knew Matrix/2by3 would get it sorted out real quick. Thank you for clarifiying the situation so quickly.

Don't feel too bad, I really appreciate all the hard work you've put in thus far. [:)]

[TF 38]

Thanks Pry,

All MG will have to do is issue a small .ZIP with the correct files. [:)]

TF 38

[mogami]

Hi, the solution is easy. (but time consuming.) Using the scenario files pre patch move the small scenario data files to a new folder. Install the patch and then move the data files back into the scenario folder.

[Stilletto]

ORIGINAL: pry

Yes there is a problem with replacements with all small map scenarios and it is solely my fault. 2By3 and Matrix are totally blameless.

I am sending in replacement files as I write this, hopefully they can be released as an emergency patch. I made a tragic mistake and error by overwriting all the scenario aircraft data files with the same copy, thus screwing the pooch big time for replacements for all small map scenarios.

I wish to make a public apology to everyone for this unforgivable error on my part, as I said 2by3 and Matrix are blameless.
No one in the world feels worse about this right now than I do right now. I am sorry.

Any idea how long this will take? I had waited to start anything serious until this patch. Oh well. A little more time will just make my wife happy.

[Bodhi]

ORIGINAL: Mogami

Hi, the solution is easy. (but time consuming.) Using the scenario files pre patch move the small scenario data files to a new folder. Install the patch and then move the data files back into the scenario folder.

Wouldn't that leave you with copies of the 1.10 database files, with their accompanying base errors and possibility of units disappearing? If it's only the aircraft replacement files that are wrong, you may be able to just replace the wpaXXX.dat files of 1.20 with those of 1.10.