RHS 7.7871 comprehensive uploading

[el cid again]

We are punching eratta and things that might be eratta - just in case - to insure code is happy.

We also are working on coordinating with ship art - and creating options for more ship art (separating classes using the same images).

We also are working on EEO - and things that might retrofit from that to EOS/AIO - and any eratta the process discovers.

We also are testing - hunting for problems.

PLAN: a non-critical update as a courtesy for new game starts will issue in 1 to 3 days - or both. That is, Sunday and/or Tuesday.

[el cid again]

Looking at the Ki-64. It looks like a Ki-61. But burried in the body of the aircraft is a second engine, and it drives two airscrews on the same hub - contra rotating. It is FAST - but short legs (must feed both engines after all). Armed like a Ki-44 III with 4 x 20 mm cannon. Sort of like a Pfiel but available much sooner.

[Mifune]

The Ki-64 could be an interesting counter measure. What would be the expected availibilty?

[el cid again]

We have to work from the date of first flight of the first prototype - since it never went into service. In RHS we use the best case for Japan IRL as the conservative minimum standard: which is two months from first flight to start of regular production; two months for production of a single engine aircraft (not a prototype); and two months from service delivery to first operation. That is, six months from Dec 1943 = June 1944.

We will use the Ki-100 slot - not operational until April 1945 anyway - and the same code name as Ki-61 and Ki-100 - Tony - because it looks so much like the same thing there is no way to give it a separate code name (and IRL it would use the same one - although possibly with a suffex - e.g. Tony III).

Since the aircraft was not operational IRL, it will not appear in CVO or BBO family scenarios. Since it reasonably could have been, it will be in EOS family scenarios.

This is a bomber destroyer - or perhaps a bomber DESTROYER. It should be better than a jet.

[el cid again]

[quote]ORIGINAL: el cid again

We have to work from the date of first flight of the first prototype - since it never went into service. In RHS we use the best case for Japan IRL as the conservative minimum standard: which is two months from first flight to start of regular production; two months for production of a single engine aircraft (not a prototype); and two months from service delivery to first operation. That is, six months from Dec 1943 = June 1944.

We will use the Ki-100 slot - not operational until April 1945 anyway - and the same code name as Ki-61 and Ki-100 - Tony - because it looks so much like the same thing there is no way to give it a separate code name (and IRL it would use the same one - although possibly with a suffex - e.g. Tony III).

Since the aircraft was not operational IRL, it will not appear in CVO or BBO family scenarios. Since it reasonably could have been, it will be in EOS family scenarios.

This is a bomber destroyer - or perhaps a bomber DESTROYER. It should be better than a jet.

Two x 1175 hp engines BUT they only count as one in the RHS maneuverability formula. Not only are both on the centerline, they share the same propeller hub. [The Forward one is variable pitch and is driven by the after engine; rear propeller - both are in the nose - is contra rotating and fixed pitch - and driven by the forward engine.]


Fighter Index 29.0 !!!


Max speed 690 kmh. Cruising speed 440 kmh.

Service Ceiling: 12,000 meters.

ROC 909 meters / minute (meaning initial ROC will be very high indeed)


Sea Level Agility: 2.30
5000 meter Agility: 1.37
10000 meter Agility: 1.37 [Scale designed so 1 is a good fighter]

wow

No Load Range = 1000 km = 10/3/2 hexes.

[Mifune]

Yes the stats are good, but Metric? Alright let me get a couple of hours of sleep,then maybe I can convert and see what it looks like in WitP terms.

[el cid again]

Sorry. Scientifically trained, I keep all data in metric form - which I also think in terms of. I will convert.

[el cid again]

Considering taking the last three Baltimore class and having them appear a year sooner as CVLs of Saipan class - for EEO.

Or maybe only two - named Arlington and Wright - because we don't do wartime names (in general - Bataan being an exception since it is a likely battle to occur).

A Baltimore took 24 months from launch to commissioning, while a Saipan took 12 months - so the same hull appears sooner by a year. Now these hulls are not exactly the same - but close enough they can use the same steel, engines, labor and yards.

Note however that the wartime design differed from the post war form of the ships: fore and aft you have two single 5 inch guns - vice quad 40 mm.

We likely would use cruisers which replaced the Alaska class - to get the dates from.

Thus the Wright CVL-49 would replace St Paul - on 440517.

Arlington CVL-48 would replace Pittsburgh on 440215.

I think these ships as carriers are worth more than the same steel a year later as CAs.


Implementing this I find we cannot use the name Wright either - we already have assigned it to a different CVL. So we will use Arlington and Gettysburg.

I am adding CV and CVL numbers to US ship names. This will help players to know which hull is meant - as they change names IRL and we tend to use original names - but sometimes like here we use other appropriate names - mainly due to battle name or respawn issues. [We don't know what ships will get sunk and we don't want two of the same name kind of thing; we also don't know what battles you will fight and cannot before the game starts name the ships.] If this is popular we may add BB, CA and CL numbers.

[m10bob]

"Or maybe only two - named Arlington and Wright - because we don't do wartime names (in general - Bataan being an exception since it is a likely battle to occur)."

I know you did not mean this literally, as CVE St Lo was certainly a WWII battle.[:D]

[el cid again]

Well - so I assume was Casablanca. But it is fixed being ETO. Where was St Lo? Doesn't sound like PTO battle to me.
We assume ETO develops pretty much as it did - since any other assumption messes up reinforcements.

[m10bob]

Indeed...St Lo was the first major city retaken by the Allies just off the Normandy beachheads, (ETO). It was taken just prior to the kick off for Operation Cobra.

[el cid again]

Here we go:

Max Speed 429 mph Cruising at 249 mph for 150 minutes on INTERNAL tanks

yields 250 minutes with 2 x 50 gallon drop tanks (same as Ki-61 II and Ki-100 on same airframe)

for 17 hex range (5 extended/ 4 normal range)

Maneuverability 37

Durability 17

Can carry the same pair of 250 kg bombs as a Ki-61 II or a Ki-100

RHS Operational Ceiling 35,433 feet

I consider the Ki-61 family to be the "Japanese P-51s" - and this variant is certainly a contender for a fine fighter plane.
It spent a lot of time in testing of subsystems to insure a smooth development path, and likely would have worked as advertised. A most unusual feature was steam cooling for the engines. It could fly without problem on either engine.

[el cid again]

Saipan art distributed for bitmap 0016 - for use with RHSEEO. Two different people in Europe sent it to me. I con't see how to attach it here however?

These ships - called Arlington and Gettysburg - are outfitted with a composite air defense group. Modeled on night fighter groups on Independence class CVLs, the larger ship permits adding a day fighter unit, with the same basic type of aircraft (F6F) - so the ships will end up with 12 torpedo bomber based night fighters, 18 F6F night fighters, and 18 F6F day fighters. The ships are intended to work with two CVs - providing specialist CAP day and night.

[el cid again]

Looks like we have revised ship art. I have set the pointers to work with it - so if you get this set - get the new ship art as well. Nothing will crash - but you risk seeing an empty screen if you don't get the art.

Also did extensive work on the EEO file set. In particular, IJA engineers, AAA and armored units, and some divisions. Armored task forces now have Japanese names. Added one AA brigade in 1945. Upgraded 1st and 2nd AA brigades to division status. [Normally a division is all you get in a district - but eventually major cities get one] Two Saipan class CVL added (named Arlington and Gettysburg) with new air groups - air defense carriers with two kinds of night fighters and F6F dayfighters. These appear in early 1944 instead of in 1945 as heavy cruisers of Baltimore class.

Also created an IJA Pack Division OB - and 40th Division is converted to this standard. Other pack units will convert to this standard for now (that is, they will add support and field hand squads - over 600 of each - over time).

There is a new aircraft in EOS family: Ki-64.

There are corrections to aircraft data - notably durability of Ki-84 and range/payload of Wellington.

[el cid again]

These files should upload in a matter of hours.

[Mifune]

The new Allied ship art is uploaded to the RHS web site. The new art is found in the Basic Install folder.

[Mifune]

Well maybe minutes.=0

[el cid again]

Reworking Allied units in Malaya - which were not well done after all.

[el cid again]

With unexpectedly comprehensive review of Allies in Malaya for all scenarios, and more eratta than expected,
this set is now uploading.

It is virtually final. We will release EEO in two days - and Level 7 MIGHT update then again. But this is essentially the completed form for extended testing. Levels 5 and 6 will follow in 5 hours - and will NOT update again until after Matrix next release.

[Historiker]

Is there any list with the upgrade paths?