Scenario 17 in 2.30 ... ship record #1

Post bug reports here.

Moderator: Tankerace

Post Reply
User avatar
Mr.Frag
Posts: 11195
Joined: Wed Dec 18, 2002 5:00 pm
Location: Purgatory

Scenario 17 in 2.30 ... ship record #1

Post by Mr.Frag »

A while back I posted that the editor tends to corrupt record #1 in both ships and air groups when loading (I know you don't support the editor and it's easy to work around so no biggie.)

Looks like you got stung by this one in the patch.

Scenario #17
Captain in Akagi (record #1) = 1999 nobody instead of 423 T. Aoki

I always load the scenarios into the editor on the locations screen, and never see this happen. If loading on either the ships or air groups tab, you seem to have about a 50/50 chance of getting either Akagi or 24th Sentai with some form of corruption.

Nothing serious, and it's got a very simple fix ;)
User avatar
Oleg Mastruko
Posts: 4534
Joined: Sat Oct 21, 2000 8:00 am

Post by Oleg Mastruko »

Yes, there seems to be a problem with Akagi captain... since he's not specified you may even get a (randomly picked) Allied commander as Akagi captain later on!

Matrix would you be so kind as to post the fixed version of the scenario somewhere to download? I have scheduled PBEM game of #17 and am reluctant to start with Akagi in the hands of the "Allied" captain.

Now, before you ask me "why don't you fix it yourself", here are the reasons:

1.) Editor supplied with the game is buggy and broken. Whenever I used it strange things happened, equipment started disappearing in the game etc. So I'd rather not play with it. (Mr Frag correctly stated that editor seems to corrupt records in random manner)

2.) Whenever you tamper with scenarios in the editor, you must save it in slots other than 1-19, and "new" scenario is labelled as "unofficial campaign". By asking my PBEM partner to play "unofficial campaign", I ask him to trust me I didn't tamper with it in a "wrong way", and I don't want to do that.

Please post the simple fix for Akagi in #17 thank you.

Oleg
Post Reply

Return to “Tech Support”