RHS Level 7.757 files and new pwhex set uploaded

[el cid again]

UK/CW HQ and air HQ units required rework - will look more like US HQ units. Almost done.

[el cid again]

After MUCH rework of Air HQ for UK/CW - a microupdate is uploading - location, ship and device files only.

[Mifune]

RHS level 7.754 scenario updates now available at the RHS web site.

[el cid again]

Microupdate 7.755 has been uploaded for about 12 hours now. This wholly replaces 7.754 microupdate and goes on top of 7.753 comprehensive update files. It addresses problems of disappearing units and locations. It also comprehensively reworks British and Commonwealth air support related units (independent or part of other units). It addresses some eratta in the location file and adds three USN LSTs.

We will issue an eratta update after completion of the tag team first turn. Anyone may reply to this turn - and run a game in parallel with the tag team game - which will be published in a sense not before attempted (with various kinds of statistical reports derived from game data). Creating a careful turn is a fantastic way to find eratta that error checkers might miss - so surely there will be some. Even so, we believe this release may be stable, and suitable for a game of some duration. We should know soon.

[el cid again]

This update addresses differences in hexes between Level 7 and previous forms of RHS. In particular, units appearing at the old Aden location could not be played.

It adds 9 more USN LSTs.

It reworks the IJA forces at Wuhan triple city complex.

It reworks again the RAAF air support units of several kinds, completing the process to the new RHS standard,
and slightly better modeling the location/force support situation.

It adds an engine to a Thai support bomber (in case you want to build any).

It changes one device upgrade which was found to have ahistorical impacts (EOS only).

It looks like we are ready to go - so these file sets are frozen. Future eratta may or may not result in an update, but if they do, it will not matter significantly to games in progress.

[Buck Beach]

Is this update (level 7.756) a comprehensive update or a microupdate for the 7.753?

[CobraAus]

Is this update (level 7.756) a comprehensive update or a microupdate for the 7.753?

comprehensive

Cobra Aus

[el cid again]

This slight revision to the pwhex files may be safely used with games in progress.
It includes:

a) Revision of some of the hexes in Southern Australia, including terrain type,
land/coastal status and hexside matching;

b) Revision of some hexsides in Central Asia (matching);

c) Revision of hexes where Ceylon meets India (adding one more land hex to Ceylon itself and revising appropriate hex sides);

[Herrbear]

ORIGINAL: el cid again

This slight revision to the pwhex files may be safely used with games in progress.
It includes:

a) Revision of some of the hexes in Southern Australia, including terrain type,
land/coastal status and hexside matching;

b) Revision of some hexsides in Central Asia (matching);

c) Revision of hexes where Ceylon meets India (adding one more land hex to Ceylon itself and revising appropriate hex sides);

I am confused. Is this PWHEX only for level 7?

[Buck Beach]

I too am confused.  I am one who very much who appreciates your RHS work, but your naming convention and continuity is lacking organization.

[CobraAus]

I too am confused. I am one who very much who appreciates your RHS work, but your naming convention and continuity is lacking organization.

to help with the confusion, PWHEX file follow a different version number than scenarios
because of the time frame that they are issued - a single release of the PWHEX could cover several releases of the scenario sets
the current 7.93 is for only for RHS version 7 scenarios
version 5 scenarios would be V5.93 and version 6 scenarios V6.93

As for continuity I try and keep a close eye on version numbers as Sid releases them and correct if wrong, a sort of quality control.

Cobra Aus

[el cid again]

Otherwise this set adds the last 15 identified as missing USN LSTs in the 700 series. There may be more in the 800 series and surely there are more in the 1100 series, but as 1944 arrivals the 700 series had priority.

Level 7 had two Aussie HQ units in the wrong place. All Levels had several HQ units in the wrong command. A tiny bit of AI assist programming was done in the form of assigning aircraft missions to groups.

Investigation of the B-25 Shangra La unit on USS Hornet (in EOS ONLY) indicates that while it appears to be a normal unit, code may not fly it (or not often fly it) on missions (other than transfer). So we have created a special B-25 aircraft - using the B-25C/D art and performance specs and loadout - but defined as a carrier plane in a different sense than other B-25s are. IF this works - we might someday convert the PBJ to a similar format - since it was intended to operate on carriers - and since tests showed it could do so. But this workaround might fail if players do not use the bomber as a medium bomber - at reasonable altitudes. There are problems - since you only give orders once a day - but it might be a good idea to restrict the Shangra La unit in the following sense:

IF the B-25s are given a mission, ALL OTHER squadrons must be stood down on the same ship (USS Hornet presumably); If you want to fly other squadrons, fly off the Shangra La unit to a land base first.