Page 1 of 1

RHS Pwhex file reissue

Posted: Fri Oct 31, 2008 7:00 am
by el cid again
A hex North of Broome Australia is improperly coded as land when it should be coastal. This is hex 27.85.

The RHS installer/switcher program has this hex coded wrongly. It will be redone in due course - our programmer has returned home but isn't yet ready to go to work. This program will still change hexes (like river openings) even if you install a new pwhex file.

The original RHS system was to use just one RHS pwhex file. IF you want to do it that way - use the pwhex.dat file here.

The second RHS system was to have several files - which you rename when you want to use them.
These are also here. IF you want to use a different file - just cut out everything in its name except pwhex.dat - and copy it to the top level folder.

IF you LATER want to change back to the original file - simply rename STANDARDpwhex7.dat - and you will be back.

There are two "families" of RHS pwhex files.

The first ones apply until 17 October 1943 - and the later set applies after that date. That is the date the Burma-Siam opened. Four different rail lines all upgrade or appear in these files on that date (which is close to the right date for all of them). What happens is this:

1) The Burma Siam RR changes from trail to road = secondary rail line in Andrew Brown's scheme of pwhex

2) The Bengal and Assam RR changes from road to railroad. This feeds the area from India's main rail net to the Imphal and Ledo areas. This was a major and important US Army Railroad Service project.

3) The Whitehorse and Yukon RR changes from road to railroad. This is not important - but it was a US Army RR project.

4) The road on New Caledonia changes to railroad. This is another US Army project.

The basic file is changed by renaming RAILROAD17OCT43pwhex7.dat - the date is in the file name so you know when to do it.

But we give you other options in both families.

A) The Panama Canal can be taken out - and the Panama RR is reduced to trail status at the same time - IF there is greater than 90 per cent port damage at Panama City. To do that - rename
PANAMApwhex7.dat if before 17October43 - or LATEPANAMApwhex7.dat if after that date

When the port damage at Panama City is reduced to less than 10 per cent - rename the pwhex file back to fix the canal and rail line: STANDARDpwhex7.dat if early and RAILROAD17OCT43pwhex.dat if late.

B) The Kyushu-Honshu RR Tunnel can be taken out on a similar basis - if the Kagoshima hex suffers similar port damage to that described above. To do this you rename KYUSHUpwhex7.dat by removing all the name except pwhex.dat - if early; or LATEKYUSHUpwhex7.dat - if late.

When / if the damage is repaired, rename with STANDARDpwhex7.dat if early or RAILROAD17OCT43pwhex.dat if late.

C) If you wish to play with open interior river systems (this means players must be careful not to send large ships into shallow rivers) - you can rename RIVERpwhex7.dat . Originally this option was meant to be used only for a day or two so small vessels could leave an interior river system - and not be "trapped" in it - or vice versa. For the purpose of this - "small" ships include:

1) All river craft (a vessel with R in its name or an abbreviation beside its name - as in RGB) - regardless of type designation (a CL means it has 6 inch guns and armor; a CA means it has 8 inch guns and armor)

2) All landing craft

3) All junks, dhous, or vessels with "river" in their name (river tanker, river transport)

4) Any transport or tanker with a capacity of 500 tons or less

5) Any destroyer type vessel (although it occurs to me that a true DL should be exepted from this - if you can identify them from a DL in the name)





RE: RHS Pwhex file reissue

Posted: Fri Oct 31, 2008 7:23 am
by herwin
When and where available?

RE: RHS Pwhex file reissue

Posted: Fri Oct 31, 2008 9:17 am
by el cid again
These files were transmitted to the primary distribution list just before the above posting (a few hours ago).

They are available from me or from anyone on that list. I need an email address to send them - send by pm - since crawlers will lift it if posted here.

An updates file for RHS was posted yesterday by the same means - and a supplimental microupdate will go out shortly - see separate thread for details. Again - we have no access to th site (Mifune alone has the password and he is not in communication with anyone) - so they are sent out directly.

RE: RHS Pwhex file reissue

Posted: Sun Nov 02, 2008 8:42 pm
by Mifune
The RHS pwhex files are now available at the RHS web site.

RE: RHS Pwhex file reissue

Posted: Mon Nov 03, 2008 1:54 am
by el cid again
This file set is mainly created for posting on the RHS site - now that is an option again. That meant that we should have a single comprehensive file set instead of 9.75 comprehensive and an update to 7.951 micro.

I took the opportunity to update a little bit of planning - that is - planning fields of LCUs -

otherwise 7.952 = 7.951 comprehensive + 7.95.

More specifically, 7.95 and its tiny variations are mainly a rework of aircraft carriers with respect to deck armor and durability. In the beginning we were addressing Dili's concern that armor on lower decks should not protect a carrier as much as flight deck armor does. In the process of working out how to do that we discovered a good deal of inconsistency in carrier durability data - and some eratta in vertical and horizontal armor data (often for understandable reasons).

In addition, we included a few other eratta discovered or reported over time - and

one RN carrier (Victorious) changed sub classes - with the effect of increasing its air capacity by 9 -
and one RN carrier (formerly Unicorn - now renamed Irresistible) was upgraded to the third sub class of Illustrious - and the lead carrier of the follow on group was added - both of these ONLY in EBO.


RE: RHS Pwhex file reissue

Posted: Mon Nov 03, 2008 1:56 am
by el cid again
Since I just uploaded 7.952 comprehensive - I think Mifune is ahead of me - and that - when he discovers a new set in his inbox - there will be a single update instead of 7.95 comprehensive and 7.951 microupdate. As described above - they are almost identical - but is easier to just have one set.