1.02 Carriers at War Beta Uploaded to Members Area!!!

[Greg Wilcox]

Hi everyone,

The v1.02 Update for Carriers at War is now available as a Public Beta via our Members Club. While we do final testing we figured we'd offer you a change to get it early as well. This is still a beta, but it's stable and solid as far as we can tell. Barring any major issues being found, this will become the official update.

You can download this as a Registered Download as long as you have registered your Carriers at War serial number in our Members Club (click on the MEMBERS link in the top nav bar).

Here's the change list:

New Scenario

• Version 1.02 introduces Tarawa, a complete new scenario that covers possible Japanese reactions to the US invasion of Tarawa in November 1943. This scenario comes complete with mystery variants, so you can never be sure what forces are opposing you, or what their plans will be.

Game Changes

• Separated landbase names on the map to better cope with the situation of multiple landbases in a single hex.
• Added a 3 second pause after the last plane leaves the strike screen before the next report is shown (if the Wait for Click option is off).
• Added help text landbase orders.
• Added text to the profile of carriers being attacked that have planes arming and/or fuelling to let the player know of any extra damage.
• Added an extended range icon to squadron displays to let the player know that a squadron is ineligible for a strike because the strike is too far away. Also ensured that these calculations are made correctly in all circumstances.
• CAP now lands at the end of the Dusk hour, not the beginning, and CAP planes that happen to land after Dusk is officially over will not suffer landing penalties.
• Added Utility Windows to the game. These windows are customizable by the user, and appear above the map and to the left of the time and game speed windows. There is an area in the Options Screen to control them. A Utility Window FAQ is included with this patch with more details.
• Made minor changes to various scenarios.

Game Bug Fixes

• Fixed a problem where crippled taskgroups were not eligible for surface combat
• Fixed a problem with cohesive strikes ordered using the right click on map menu and a related problem where the TG included a carrier that was incapable of air operations.
• Fixed a problem with planes cycling through stations after a strike
• Fixed a display bug where plane totals were sometimes not updating correctly when a strike was being assembled.
• Fixed a display bug where occasionally ships that had been already sunk would show as not sunk in the combat screen
• Fixed a minor bug where gamelog text entries would be incorrectly displayed until the gameclock had run for 5 minutes.
• Fixed a display bug where fighter bombers would sometimes not have their armament shown when their strike wing was being displayed.
• Fixed a display bug where ships in combat could sometimes show damage animations before being attacked.
• Fixed a display bug effecting shadows and debris of planes in the combat screen.
• Fixed a bug where damaged planes that actually crashed while returning from a strike were shown as being destroyed in the combat screen.
• Fixed a rare hang bug that could occur when flicking between cohesive/noncohesive strikes and different targets while assigning squadrons
• Ensured that ship and plane reports always update correctly every 5 minutes.
• Prevented right mouse clicks on map orders window as being misinterpreted as destination orders.
• Fixed a problem where planes that actually died while on a CAP mission would still be shown in the total of planes available for CAP.
• Fixed a problem where floatplane fighters carried by capital ships would be counted as available for CAP

Editor Changes

• A number of changes have been made to the Editor. These improve the layout of data and include extra help text and info displays to help scenario creators.
• Stopped many Editor crashes when confronted with incorrect data, and substituted error messages to provide much better feedback to scenario creators.
• Added a resource search control to speed up locating resources.
• Added a number of functions and resources to enable creation of new countries.
• Increased the size of some textboxes and allowed for extra text entry.

Editor Bug Fixes

• Fixed a bug which prevented entry of large numbers for AA and DP guns for ships.
• Fixed an occasional crash when adding new submarines.
• Fixed a number of bugs when deleting or copying/pasting WarRoom actions.
• Fixed some display and text handling problems.

Options Changes

• Added the Max Autosave Space option in the Other Options section to specify the number of megabytes that autosaves may occupy. When the limit is reached, older autosaves are deleted so as to keep within the limit. Set the save limit to 0 if you don’t want any limit on Autosaves.
• Added the Utility Windows options area to enable users to choose which windows to show, and in which order.
• Added the internet stats options area to allow users to set details allowing them to upload their game statistics to the internet. Internet stats will only include in-game details such as side scores, number of ships sunk etc.

Editor Tutorial Scenario

• The framework of a new scenario, Cape Matapan, has been included in the ‘Mods’ folder. This scenario has a complete OB and AI, but lacks various graphics. An Editor Tutorial and template files accompany this scenario framework and explain how to integrate the various graphics into the game. The WarRoom cards in the scenario AI have been heavily commented in order to further explain their functions. We hope that this will help the user community better understand the CAW scenario creation process and the result will not only be a finished Cape Matapan scenario but the production of other scenarios as well.

[Blond_Knight]

I especially like the "Enemy Aircraft spotted on flight deck" notification, and the new aircraft destruction animation on the strike screen. If I could have one small additional feature it would be an import/export function in the editor, for aircraft, and ships.  Otherwise you have to start editing a copy of an existing scenario, or a purist will have to recreate the wheel each time they want to make a new scenario.
Well done, we appreciate your continued efforts.

[decaro]

I was hoping something like this would happen; all we had to do is wait!

[decaro]

ORIGINAL: Greg Wilcox

Hi everyone,

The v1.02 Update for Carriers at War is now available as a Public Beta via our Members Club. While we do final testing we figured we'd offer you a change to get it early as well. This is still a beta, but it's stable and solid as far as we can tell. Barring any major issues being found, this will become the official update.

You can download this as a Registered Download as long as you have registered your Carriers at War serial number in our Members Club (click on the MEMBERS link in the top nav bar) ...

I can't find any CaW patch save the 1.01 fix on the Matrix Members site or the SSG patch page; what am I doing wrong?

I also assume you are referring to the serial number -- along w/a host of other numbers and codes -- on the CaW CD. I wonder what digital downloaders are supposed to do?

[Prince of Eckmühl]

Hey Joe,

It's under Registered Downloads

PoE (aka ivanmoe)

[Marc von Martial]

ORIGINAL: Joe D.
I wonder what digital downloaders are supposed to do?

[&:] Simply check their purchase receipt as it contains the serial number [;)]

[decaro]

I knew I was doing something wrong.

Matrix Members' Club password -- 6 capital letters -- is a separate password from the forum log-in; the first thing I saw was the (already) available patches, so I thought I was loged-into the Club, but I wasn't; my bad!

Got the zipped file; now for a test run; thanks everyone.

PS: Well, at least I'm now on the CaW mailing list.

[alexs]

Hi Blond night - there is an load function in the editor - its on the bottom left of the screens (where it's applicable), using the folder icon. There are 2 variations of it's use - the first is where you are trying to import a single ship class / ship / plane type / landbase etc from another scenario. Add a new ship, and name it correctly. Then make sure it's selected in the object list (on the left hand side) while you hit the load button, and select the scenario you want to load it from (that's the only hard bit - you have to know where it's used before). The information is then updated.
The other way to use it is to load ALL the ships / carriers etc from another scenario, and to do this, make sure nothing is selected in the listbox on the left hand side of the screen.

Alex

[McGlu]

Thanks for the new update!

Added the internet stats options area to allow users to set details allowing them to upload their game statistics to the internet. Internet stats will only include in-game details such as side scores, number of ships sunk etc.

Where can we see the stats that have been uploaded?

[alexs]

I'll be creating a php page for the display of stats shortly.

[derwho]

Fantastic!! [&o]

[Llyranor]

Improvements, fixes and a new scenario? Great support!

[vinboni]

I played a midway random scenario. I sow the Japanese all search planes have a range more short than before the beta-patch: only 120 NM (6 esa). It's this range correct? It's too difficult to spot enemy carriers for Japanese player. If he do it his carriers are so near enemy that it's very dangerous to strike therm and wait the planes come back. Better you go away quickly!

[decaro]

ORIGINAL: vinboni

I played a midway random scenario. I sow the Japanese all search planes have a range more short than before the beta-patch: only 120 NM (6 esa). It's this range correct? It's too difficult to spot enemy carriers for Japanese player ...

I wonder if that's deliberate by SSG to help simulate the fact that the Kido Butai was reluctant to use CV a/c as scouts because it would deminish its attack ability.

For the record, the scout planes on the IJN hvy cruisers didn't work too well that day, either.

[Gregor_SSG]

ORIGINAL: vinboni

I played a midway random scenario. I sow the Japanese all search planes have a range more short than before the beta-patch: only 120 NM (6 esa). It's this range correct? It's too difficult to spot enemy carriers for Japanese player. If he do it his carriers are so near enemy that it's very dangerous to strike therm and wait the planes come back. Better you go away quickly!

We're checking on this now and I'll let you know what we find.

Gregor

[Ola Berli]

Gregor,
 
excellent. I look forward for your feedback on this one. Thanks.

[vinboni]

I found the solution on search range too short in Midway scenario:
if you delete USA and Japan countries by editor the scenario works right. I would change the sarch doctrine bat I don't know  the historic values.

[Gregor_SSG]

ORIGINAL: vinboni

I played a midway random scenario. I sow the Japanese all search planes have a range more short than before the beta-patch: only 120 NM (6 esa). It's this range correct? It's too difficult to spot enemy carriers for Japanese player. If he do it his carriers are so near enemy that it's very dangerous to strike therm and wait the planes come back. Better you go away quickly!

Thanks for finding this one. The problem was caused by an improvement we made to allow multiple countries per side. This will allow the British to be separate from the US in Pacific scenarios.

Along the way, the Midway scenario got tripped up in the changeover to the new system. The other scenarios in the Beta patch should play fine, and naturally all will be fixed in the final version of the patch.

Gregor

[Llyranor]

British? Am I smelling future plans for more scenarios?

[Rekm41]

I am sure there are going to be some user created ones and who knows maybe Matrix will give us another