RHS 4.14 [Eratta; Chinese Army planning]

[CobraAus]

RHS v4.02 all scenarios + PWHEX 4.02 posted on download link page

Cobra Aus

[el cid again]

Thanks Herrbear

I will evaluate and incorporate any corrections in 4.03 - but I have no idea when that may come out. I may release it as an optoinal non-critical update. Particularly if other tihngs come up.

[el cid again]

OL DOG:

I understand the problem with the AO Kaskaskia - it is too large a number in the field - this is interpreted as a negative number. Someone gave it a value over 16,000 - the binary just above that - a no no.

But I never found the ship. If someone finds a slot number I will fix it.

[witpqs]

ORIGINAL: el cid again

OL DOG:

I understand the problem with the AO Kaskaskia - it is too large a number in the field - this is interpreted as a negative number. Someone gave it a value over 16,000 - the binary just above that - a no no.

But I never found the ship. If someone finds a slot number I will fix it.

Ship class 349 - Kennebec. Endurance is entered as -11072.

In my game it seems that it does get corrected in an upgrade, but it's a long time to wait for that! The upgrade is to class 1483, with endurance entered as 15000.

[el cid again]

The upgrade is correct - range should be 15000 nm - and I have set it to this value for the original class. I will issue a micro update with this - and a lower speed LAGG-3 - and a few other things - but not just yet. I am sure some other things will come out. I have just got some dates to test for carrier air groups - maybe I can get a handle on the multiple squadron thing? And I always do a little cosmetic work - making lables more consistent - etc. It is already fixed in my file set - so I can send it to anyone who wants it who cannot run the editor for themselves.


The RCAF has its squadron names in front in RHS format now.
The IJN AMCs are redefined into four different classes - because of four different sets of armament and characteristics. They will all convert to APs if you want later in the war. This is historical - except that the EOS APs have better AA armament. In AMC form these ships are now all classified as CLs - as are cruiser minelayers on both sides.
Some eratta also corrected related to land units and supply depots, or reinterpreted to make it easier on AI at startup.
AI is getting good - but you still must load 18 division - it won't do it right.

[CobraAus]

RHS v4.03 all scenarios posted on download page

Cobra Aus

[el cid again]

We are going to try "one more time" for a "final" RHS 4.0 release -

4.04

This one will do away with trying to make code happy re resizing carrier squadrons.

Cobra confirms the art changes for planes - so they will be in there too.

I have secretly figured out how to make AI happy in several respects,
and snuck it into 02 and 03 already - mostly - and may fold in more for 04. Testers indicate it is working very well.

Unless someone WANTS a version to work with resize code, RHS is going to tell everyone 'don't disband in a major port with a major HQ' after 1943 begins. And it will keep four squadrons in RN and IJN as well as USN - and USS Midway will revert to four squadrons again.
Seems NOTHING works in RHS because the issue is squadron names - and probably EVERYTHING would work if only we were willing to call No 801 Squadron "VBF" - stuff like that. I am not willing.

[CobraAus]

arn't we forgetting the DISBAN to REPAIR if you have carrier you have to repair 43 and later
you would normally take it the nearest large port and disband to repair it
what happens now if you dont dispand it will take forever to fix

Cobra Aus

[el cid again]

I am not forgetting that. In fact, you ALSO need to disband to upgrade the ship. Just don't do it at the wrong place. I think the US should not have a Pacific Fleet HQ at PH after 1943 begins in the first place - or the Japanese are playing improperly (and violating what Adm Yamamoto concluded on Dec 10, 1941 - US time - two days after Pearl Harbor: Japan should take Hawaii - something staff pointed out long before). If the US has PH in 1943, Japan will never get it - and the US has a base halfway to Japan. Stupid. If Japan has it - the US probably will waste energy fighting over something Japan does NOT need - smart - crash those waves on the rocks. Do it right, you can offer to neutralize Hawaii (under the restored monarchy - a Japanese plan since 1910) to end the war. Or even give it back. An exit strategy. Or keep it - if the US is weakly playing its hand.

Japan has its choice of several ports to disband in. So do US and UK.
I see no big issue in any case. Only a US damaged ship in the central Pacific might want to go to Pearl. Well - if she goes - you will resize - and need to beach a squadron. You can live with that.

[witpqs]

Actually Sid, it's a bigger deal than that (as far as ports go). The rule isn't that it has to be their command HQ, it only has to be any command HQ. So, for example, San Francisco has Western US HQ. It also has the biggest shipyard, the one most useful for upgrading carriers. But under this scheme it would be out of bounds for fear of a re-sizing.

On the other hand, beaching a squadron is not too big a deal.

[el cid again]

You are sort of right. My thinking is that only at Pearl Harbor is it kind of "there are no other reasonable options close by" so it might matter.
At San Francisco you can go to Portland, Seattle, Tacoma, Vancouver, Los Angelus, San Diego or Long Beach (in RHS - slightly fewer in other scenarios). In Australia go to Brisbane or Sydney. In Ceylon, go up to Bombay or Vizapatnam or Calcutta. But in the Central Pacific there is only Pearl Harbor.

[bbbf]

Cid,

Does the command radius of a Naval HQ affect this?

Actually, do any have ranges greater than 1? I've never really taken much notice.

[el cid again]

There is some controversy about this question. Some Matrix programmers think ONLY units in the same hex are affected by command radius. The only clear exception I am sure about is air ops. Air strikes can be coordinated out to the command radius of an Air HQ. But - wierdly - the air units need not belong to the command! ANY air unit on the same side will (sometimes) coordinate!

[witpqs]

ANY air unit on the same side will (sometimes) coordinate!

That's true, as far as I know.

As far as command radius range in general, the point often tripped over is how the range is defined. A range of '1' means 'in the same hex'. A range of '3' means 'in the same hex and up to 2 hexes away', a range of 5 means 'in the same hex and up to 4 hexes away'. It's weird, but that's how they did it. Subtract 1 from the command radius given, and that's how many hexes away it has effect.

[CobraAus]

RHS v4.04 now posted on download link page

Cobra Aus

[el cid again]

Regretfully, there will be an RHS 4.05.

I have found by playtesting 7 devices which do not fully work.
I have found by updating ship records a few cases where ship class records are wrong (although the ships are right) - and a few other issues.

I am incorporating a day and night experience rating into RHSESO and RHSPPO for widespread testing to see if this is better than the existing built in table system?

I found a Japanese AV improperly defined in RHSEOS.

EDIT: Nope - the art is fine! There appears to be a need to generate another planetop file - referred this to Cobra - for four planes.

There will be another pwhex file - to turn sea into land (and sync with art) on Sakhalin island - and make Ilagan impossible to approach by sea - because it is - and probably a couple of other things. For those of you not intimately familiar with the geography of Northern Luzon - Ilagan is a city in the Ilagan Valley NE of Baguio City - a moderately rich area in resources - and a path between Aparri and points south on the Eastern side of the island. But the path is inland, and there are no ports or useful beaches to seaward - just undeveloped mountains. In the present age it is the last stronghold of the NPA - a communist organization that actually controls territory right on Luzon. Don't travel there in a first class automobile with only white people in party - or you will be held for ransom!

EDIT: I also am working on making AI work better. The use of day and night ratings may contribute to this - putting Combat Proficiency Ratings into the system.

[el cid again]

I am reprogramming RHS Empire Of the Sun for AI purposes -

originally just changing what was built - and slightly what is assigned to a few units-

the present focus is on changing where things start. Turns out this helps a lot. Playing a real game I see lots of ways to do it better than history.

Otherwise, I am working on seven devices with issues - and when they work - 4.05 will release.

I keep finding little eratta too. One SNLF "disappeared" because of 9999 code - I have no clue why - things like that. A repair ship appears years too soon - a ship that never existed - but was authorized - and is in CHS from day one - is in RHS only in the alternative scenarios (BBO type) - and then you still need time to build it! [Or cancel it and get other things faster]. But I never had corrected the CHS date - so it was appearing on day one! Stuff like that.

[el cid again]

I have made all seven device slots with issues function inside units.
Now it is just a bit of art - moulding them to have the values I want - or as close as works.

RHS 4.05

with all devices working

with revised Command locations

with all attempts to humor AI re carriers with 4 squadrons removed

with some Russian air groups reassigned planes and

with the usual eratta (particularly in EOS where a AV was playing CVL)

with EOS and PPO revised for ship ratings to an RHS scheme (thousands of fields)

and with AI enhansed first turn for EOS

should issue tomorrow - 14 July.

I now need to play a game as Allies to be forced to look at things simple tests and utilities don't.

[CobraAus]

RH v4.05 PWHEX file posted on download link page

Cobra Aus

[el cid again]

The good news is that I fixed all artillery devices which should bombard so they will

and STILL have proper RHS firepower values (although that required a bit
of a trick)

The bad news is there are still hundreds of DEs and PTs and other Allied
vessels that need to be rerated for day and night - for EOS. I expect these ratings to help the simulation get combat more correct, year by year - on an average basis. Oddly - I have INCREASED US night ratings at the start by 20% - over stock - in most major warship cases - a bit of a surprise - it was awfully low - but from 1943 the Allied advantages at night appear in this system - and are wholly absent as it was.

So I need a day to get this data in. And I am running a control test - just because. It is my 100th game AI vs AI - not counting a similar number of brief tests with special test beds.

I tentatively plan to complete revision of RHSEOS - and to correct any eratta detected or reported in all versions - and then release all scenerios EXCEPT RHSPPO in one batch. Since PPO ALSO needs to have many ships revised - it will probably be delayed a day or so. ONLY EOS and PPO will have the new day and night experience ratings. Other scenarios will preserve the existing experience regime.