Matrix Games Forums

AE & RHS Surface Ship & Submarine Durability Formulas

General: These formulas were designed to replicate stock values in a consistent way. Three different formulas are used because surface ships with armor differ from surface ships without armor and from submarines.



Armored Surface Ship Durability Formula:

RHS Durability = Full Load Displacement / 300

Displacement is in tons.



Stock Durability = Standard Displacement / 250

Displacement is in tons.



RHS changed this value because RHS uses full load displacement, the universal standard used by damage control departments in all navies. This resulted in very large warships having durability values too large for the durability field in the editor and database.



Unrmored Surface Ship Durability Formula:

RHS Durability = Full Load Displacement / 450

Displacement is in tons.



Stock Durability = GRT (or similar) / 350

Displacement is in measurement tons, which have no direct relation to displacement at all. It is a measure of cargo volume rather than ship volume, usually 100 cubic feet.



RHS Changed this value to be consistent with the principle of using full load displacement, and to be relatively close to the stock ratio between armored and unarmored ship formulas.



Submarine Durability Formula:

Durability = Depth / 10

Depth is in feet. This formula is identical in RHS and stock.

RHS Comprehensive Update 6.17

https://1drv.ms/u/s!Ap7XOIkiBuUwha4tGHb ... Q?e=hmXZLM

This update mainly is to scenario and documentation files. The primary documentation file
updated is the Sorted Allied Radar Types Excel spreadsheet. The primary scenario files updated
are devices redefined by that sheet. However, some other scenario files and one other pwhexe.dat
file (for Monsoon, 1942) are also revised. Aircraft, class, location and ship files also were
updated in part.

"Radar" here means "detection devices" and includes a number of different technologies, following
practice in stock. Allied devices have been added for decades without a comprehensive review and
without universal standards. There are too many of them, including duplicates (apparently added
by different users). There are also missing devices. So we are combining devices, eliminating
duplicates, and adding new devices when discovered (during investigation of the details of existing
devices). Sometimes duplicates are due to different names for the same device. Thus, H2X is also
APS-15. So one is eliminated and the other has both names: H2X / APS-15 ABB Radar (where ABB =
Aircraft Blind Bombing). This in turn requires reassigning device numbers so the US uses the same
device as the British rather than a different (duplicated) device. Many US Bombers use the APS-15
(and indeed B-29s use the same device with a still different name = APQ-13 - but the name field won't let us
add a third one - so it is only found in the notes on the spreadsheet).

RHS Comprehensive Update 6.18

https://1drv.ms/u/s!Ap7XOIkiBuUwha4tGHb ... Q?e=es5gvE

This update mainly is to scenario and documentation files. The primary documentation file
updated is the Sorted Allied Radar Types Excel spreadsheet. The primary scenario files updated
are devices redefined by that sheet.

Note, however, that a new Russian "Type A" Radar was added. [That is, a Bistatic Doppler Interference
Detector, which is called "Type A Radar" in Japan]. This device was added in two areas of the Soviet Far
East - Vladivostok and near Kuibychev. I noticed Soviet fixed fortification units have outrageous morale
and experience levels (65) and revised most or all of these to 45. The designation is RUS-1 BDID EW Radar.

The Sorted Allied Radar Devices Excel spreadsheet is considerably updated. Apart from adding devices and
editing previous devices to be consistent with newer understandings, the sheet contains more explanations
and considerable technical documentation not needed for the game. This includes the radio frequency band,
if there is one, and the weight of the equipment. [This is in tons for land or ship use, or pounds for
aircraft use]. A new format in names is introduced. For example, ASV MK.VIII (APS-3) is used for identical
equipments with the British name used first and the US name in () - or vice versa. SF or SL DE SS Radar
is used for different equipments with the same in game performance. All abbreviations are now defined.

Once this work is completed, all Allied ships, aircraft and land units will be reviewed to insure the right
devices are in use.

RHS Comprehensive Update 6.19

https://1drv.ms/u/s!Ap7XOIkiBuUwha4tGHb ... Q?e=qWS2Wt

This update only contains documentation and scenario files.

The main work was on Allied Aircraft (wpa) files. The Group files (wpg) was updated to fold in revisions.
The Allied device (wpd) and location (wpl) files were also also slightly revised to deal with eratta. The
focus was on doing US heavy bombers and related types, as well as most PBYs. Work began at the top end
of aircraft slots - the least reviewed - and proceeded downward, doing related types in slots farther
down the slot list. CAF Beechcraft 18 bombers were revised so they (a) work as bombers or recon planes and
(b) convert back and forth with the Beechcraft 18 transport. Apart from being historical, these represent
a number of other similar light aircraft. Similarly, the USN OS2N-1 Recon aircraft and OS2U-3 Floatplane
were made able to cross convert. These are almost identical aircraft, with the landplane being faster,
longer ranged and more maneuverable while the floatplane is more durable and able to operate from ships.

The object of this work, apart from catching errors, is to integrate the now completed Allied sensor devices.
It was learned that the ELINT function works, so ECM equipment is being added. [This is intelligence type gear -
it helps identify ground unit identities]. Also, drop tank weight is being added. Sensors also have load
weight. This permits better control of what a plane can carry, and what the true load capacity of an aircraft is.
It also creates a foundation from which actual mission range can be determined for a given mission. [The idea is
to adjust the risk of loss reflecting the amount of reserve range available. A long term hook rather than a near term
goal.]

RHS Comprehensive Update 6.20

https://1drv.ms/u/s!Ap7XOIkiBuUwha4tGHb ... Q?e=tviBNh

Basically this update is a continuation of the integration of Allied "Radar" detection devices with
Allied Aircraft. However, it includes all of the pwhexe.dat files issued in update 6.19, and significant
editing of the documentation files. As well, more aircraft were done, and their effects on groups
were then folded in.

A large amount of eratta were addressed. This in particular includes things like locations where Allied
aircraft are produced. If a type does not exist in a given scenaerio, it is deleted from the location which
otherwise would produce it. Two Allied Thai land units were not properly defined. More Allied aircraft
were also reviewed, and new devices not previously available now show up in later war aircraft.

RHS Micro Update 6.21

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=TaOR9m

This update only has scenario files and related documentation updates.

Only aircraft, device, group and location files were updated.

Almost all updates are related to Allied aircraft and groups. Some eratta in Scenarios 124, 126
and 129 were folded in - notably the Thai Allied ground support unit on Ceylon - nominally fixed
in 6.20, somehow it was not fixed in these scenarios. Always double check your work.

RHS EW Microupdate 6.22

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=sKL55X


I reworked both sides EW devices because of learning how code works with respect to ELINT devices. I am handicapped by being
a real world EW guy, and game code is NOT consistent with physical reality. I must honor code to get working devices. Basically,

AE ELINT is only something airplanes can do. Never mind, now I grasp how that works, I get the same thing done other ways.

This meant I had to rework all aircraft.

In the process of reviewing EW devices, I found two Japanese actual ELINT devices defined but never assigned. I don't remember creating them, but I must have done that at some point. These only will work with extremely late war aircraft. Never mind, MOST AE work is with later types of units and devices - we do them all in case a game lasts long enough. OR because we keep working on the Downfall Scenario (where one can test late war things, but not yet play - the whole map needs reworking).

This update is limited to documentation and scenario files. It applies to BOTH sides. It only involves aircraft, class, device, location and ship files. It is just an increment - more review is needed. I find that some types of aircraft were done before the latest versions of maneuverability, durability or range formulas were defined, so eratta of that type is folded in. I find working in the weight of what a plane lifts helps get total load right. Total load is important in code terms because it means small airfields won't perform some missions - e.g. let you have drop tanks - just as lack of supplies limits operations.

Special Supplimental Microupdate 6.23

RHS Special Microupdate 6.23
https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=1hpoxK

This unplanned update is issued because 6.22 Scenario 129 was overwritten by 126. 129 was rebuilt.
However, all scenarios got a few more aircraft and groups reworked. Also, to test new art, some Allied
schooners were reworked to test the art (which failed). So these ships use for the moment older Large
Schooner art (two masted) instead of the 3 masted art still in test. These are modeled on a US Army
Transport in terms of data, and are superb sailing ships. Two of the schooners got new captains (because
I am always adding more captains to avoid the problem of the staff officer being assigned) - an experiment
in US Army ship captain definitions. The aircraft reworked are mainly a few more Liberator types in midwar.
These are defined according to the doctrine of the year, and more specialized than before - more or less
pure land attack bombers - not so general purpose (with ASW weapons) - or else what amounts to dedicated
maritime patrol planes. But both added ECM gear, which has the in game effect of causing the AI to "know"
more about things overflown, so in the next turn the player gets more information. The maritime versions
(both British and US) are low altitude planes, while the land attack versions are high altitude planes.
The low altitude versions are also slower.

RHS EW Microupdate 6.22

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=sKL55X


I reworked both sides EW devices because of learning how code works with respect to ELINT devices. I am handicapped by being
a real world EW guy, and game code is NOT consistent with physical reality. I must honor code to get working devices. Basically,

AE ELINT is only something airplanes can do. Never mind, now I grasp how that works, I get the same thing done other ways.

This meant I had to rework all aircraft.

In the process of reviewing EW devices, I found two Japanese actual ELINT devices defined but never assigned. I don't remember creating them, but I must have done that at some point. These only will work with extremely late war aircraft. Never mind, MOST AE work is with later types of units and devices - we do them all in case a game lasts long enough. OR because we keep working on the Downfall Scenario (where one can test late war things, but not yet play - the whole map needs reworking).

This update is limited to documentation and scenario files. It applies to BOTH sides. It only involves aircraft, class, device, location and ship files. It is just an increment - more review is needed. I find that some types of aircraft were done before the latest versions of maneuverability, durability or range formulas were defined, so eratta of that type is folded in. I find working in the weight of what a plane lifts helps get total load right. Total load is important in code terms because it means small airfields won't perform some missions - e.g. let you have drop tanks - just as lack of supplies limits operations.

RHS Special Microupdate 6.27

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... Kg?e=wPQD7

This update includes art (a major rework of the Allied Aircraft Side Filmstrip by Mifune)

documentation (aircraft documentation)

and scenario files

including aircraft, device, group and location files

plus unusually the scenario files associated with the scenario itself.

Integration in particular of Allied "Radar" and drop tanks is significant. Some "secret" radar data was found
- a radar said in the world of radar documentation not to have entered service in fact was issued to USMC fighters
in October 1943! See the Sorted Allied Radar Types for details.

RHS Special Comprehensive update 6.28

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=pjWCm4

This update includes art (another update to A PlaneSide),
Documentation and Scenario files.

Unusually, the CAM files are updated - in respect to pilots.
As usual, most updated records were in aircraft and associated air groups files.
Some erratta corrected in device files and location files. The documentation
files are all aircraft related. There is a new documentation file on pilots.
Pilots will be updated one more time, as it turns out we can define 1943, 1944
and 1946. [1941/2 and 1945 ar4 here updated].

RHS Special Comprehensive update 6.30

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=3V9gYC

This update includes almost every kind of file: art, pwhexe.dat, scenario and documentation files.

Most of the changes are in aircraft and group files, most of them British and Commonwealth Countries.
But a few technical eratta in the Monsoon pwhexe.dat files (both historical and JES versions) are included.
These include defining two islands as coasta/atol vice ocean/deep, and fixing a mismatched hexside pair North
of Flores Island. Two more Allied aircraft were improved on the Allied Planeside filmstrip. Ailied aircraft
production is significantly improved with respect to British aircraft, especially versions of the Catalina and
Dakota. Allied aircraft data was improved, often just in minor ways, but occasionally significantly - when
for some reason the wrong formula was used to calculate range, or a radar device needed to be added or changed.
[In some cases, the current formulas may not yet have existed when the type was defined]. The amount of eratta
in devices is almost nil - we are getting a remarkably clean database. Probably the final version of the pilot
database is included. It mainly changes China Air Force replacements from having an unintended 0 rate, and tweeks
1945 and 1946 pilot replacement rates for some nations in some scenarios.

When we complete review of aircraft (with a focus on Allies because of the later completion of the Allied radar
database), we will do the same thing for ships and then land units: insure the best radar data for each date version
of a class or ground unit is in use.

RHS Important Microupdate 6.31

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=eLiM6g

This microupdate contains scenario, documentation and pwhexe.dat files.

All pwhexe.dat files needed updating because South Island, New Zealand needed to
be expanded by one hex. An offshore island hex at the extreme "East" (map
orientation rather than true bearing) end of the island also contains a penninsula,
so a land unit can march into it overland. Additionally, some pwhexe.dat files
still needed to turn two atol hexes into coastal hexes rather than Ocean Shallow,
and some had a land hexside in the Malacca Strait still marked as an Ocean hexside.
Permitting and constraining movement in pwhexe.dat in ways consistent with map art
is an RHS principle. Players only see the art; code assumes the pwhexe.dat is the
actual map. This is almost certainly the first time South Island is presented with
all its hexes reachable by land unit movement. It also slightly restricts naval
movement near the critical approaches to Wellington.

Otherwise, RAF Hurricanes were reworked, with associated effects on air groups.
The Hurricane IIc Tropical is now the Hurricane IIc Night Fighter, complete with
Radar. The Hurricane IId is now the Hurricane IId AT. And the Hurricane IV FB
is now classified as a fighter bomber in code terms, and it carries bombs to extended
range, not just to normal range as other "Hurribombers" do. This is practical because
it has greater internal tanks than earlier models, and can perform fighter missions
at greater ranges than they could do if not presented in "clean" profile. Also they
rarely would be needed as fighters given their late appearance, so are more useful
if they can carry bombs farther. Modding is an exercise in making compromises.

RHS Comprehensive Microupdate 6.32

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=qJy1ih

This update contains a few files of every sort. Ship art. Scenario files. Documentation files.
Pwhexe.dat files.

Some midwar pwhexe.dat files (1943 & 1944) are updated.

There is a new class of sailing ship: a square rigged Barkentine. The Kailulani USAT was modified from an
ocean (3 masted) schooner to this three masted class, because she was that. The Boxer was added (a USAT ship
serving Alaska) along with a captain. Both ships are not present in the 1945 Iwo Jima Scenario (renamed
from Downfall to avoid confusion with Operation Downfall).

A few aircraft on both sides were reviewed, and some radar corrected or worked in. This required updating air
groups and RHS documentation re aircraft.

I think a bit of location file eratta was included (unless they were in the previous update). I think I found an issue
with an actual location, and with a land unit.

RHS Comprehensive Microupdate 4.0

https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIA ... g?e=DoQLtV

This massive update includes almost every file except art files. So you need to copy all the files into their appropriate
folders (unless you happen to use default Matrix folders for RHS, in which case the copy may be automatic).

Numbers of issues have been addressed. Scenario 129 was overwritten by 125 at some point, so it had to be rebuilt. This
was done with reference to documentation files, and significant eratta was detected. Often this applied to other scenarios.
For example, Mogami and Tone Class cruiser data for six inch gun versions of the ship was found to often have the right gun
but only twin turrets. Before that work began, hundreds of aircraft types were updated. Mainly because of newly available
Allied "Radar" (detection) devices, which is now essentially complete. Also because of a change in drop tank data. In particular, both detection devices and drop tanks have weight. This, in turn, forced changes in the "load" field for each aircraft type. That will have the game effect - for larger types - of restricting operations from smaller airfields. Task
Force data was found to need changes. Apart from 129, where all task force records needed review, it was found that there were
cases of eratta that crept in over time.

This update is not completed. One example is the discovery that the Eastern Fleet (since Matrix created the game) does not change its name at all, nor did it change its location (and appear in that location in Scenario 126). In 1942, Eastern Fleet moved to Addu Atol. It also changes commanders, and should appear in Scenario 126 with a different commander at Addu Atol
instead of at Singapore. More changes will be folded in, time permitting.

TBD-1s are not carrier capable, only trained

ORIGINAL: Weidi72

TBD-1s are not carrier capable, only trained

Are you sure that it doesn't say carrier trained. If carrier trained then they are carrier capable as well....GP

They are "carrier trained" but not capable. The need 4x the space on the carrier.
Haven't played for a long time and got the last update.

ORIGINAL: Weidi72

They are "carrier trained" but not capable. The need 4x the space on the carrier.
Haven't played for a long time and got the last update.

Can you post a picture of this squadron....GP

squadron

carrier