el cid again
Posts: 16922
Joined: 10/10/2005
Status: offline
|
6.71 link
https://onedrive.live.com/redir?resid=30E506228938D79E!2716&authkey=!AMrDULsG2RJdsI8&ithint=file%2cmsi
This is a comprehensive update in that it involves different kinds of files.
As expected, its primary focus was on updating pwhexe.dat files to a new standard.
This time, Spring files as well as Winter files have been updated. However, that
process turned out not to be as easy as expected, for a variety of reasons. One of those is that more information became available, more than once - so I redefined the standard (kind of like working on a DOD project when the specs keep changing - generating retroactive work in the process). Nevertheless, eventually the standard was set, and it is better in important respects. Another problem was I made some mistakes. For example, Pratas Island was defined as an island instead of an atol.
Other examples are bad hex-sides or mismatched hexside pairs which have apparently been around for a long time. Information theory says there will be errors in any large data set, but the RHS standard is to fix errors when known, or at least when that part of the data is being worked on. So in several cases I went back and retrofitted the files correcting obscure and minor eratta.
Related to the pwhexe files is the RHS Seasonal Construction documentation file. As I learned how to "schedule" construction along the proper route (meaning determine which season = which file gets the change) - the documentation became more clearly defined and readable (at least for me). But, another RHS principle is publish the documentation, so it is also published. It does provide an overview of what changes in both the standard series of pwhex files and the Japan Enhanced Scenario series as well. Loading a late war JES file and pressing reveal codes (R and Y) keys shows the full extent of planned work, much of it not funded because of lack of necessity in the war situation. Perhaps most interesting is the Trans Canada Alaska Railroad, ending at Tellar NW of Nome, as well as the Baikal Amur Mainline, most of which shows up in standard scenarios as a long trail in the middle of nowhere - but in JES it shows up as a railroad. To get the job (mostly) done during the war required keeping to the original design (the entire project was redesigned in a process lasting from 1945-1960), not ripping up rails laid since 1937 (some of them in the map art are not there shortly after the Pacific War begins), building from the spur to Tynda as planned (but which didn't happen - the spur was ripped up to send rails to the Western Front instead - where mostly they were not used at all - because it moved too fast), and laying on additional crews late in the war.
Somewhat related to the pwhexe work is changes in some locations in Russia. Some villages were actually moved (because I found a superb map by National Geographic - far above their usual standard - and surprisingly better than Atlas Mira - the official Russian atlas and generally tied for first place - with the Polish Army Topographical Service Atlas - as the best in the world - note the latter is available at great expense with English plates under the name Pergammon World Atlas - Pergammon being the British contractor buying the English planes). When the railroad hit a village, I was able to add undeveloped resources that could, if developed, now be exported (to a surprisingly small degree - the BAM has been a remarkable failure in terms of development of remote Siberia). In the process I made contact with some Siberians, and also some old WITP and other web searches revealed other data. I found good Russian documentation of coast defenses. I determined that RHS had inherited very good information from someone - but aside from minute changes - there was a major one: the railroad guns at Vladavostok are a much bigger deal than we had modeled - there are 7 - 3 huge 356 mm - and two pairs of smaller guns. 5 of those were present in fixed rather than mobile form. I had to change three devices -
so the device file changed -
to make them mobile. When present in a CD fort, they are fixed anyway. But when present on rail cars - they need to be able to move.
So we ended up changing both device and location files.
Note here any unit with RR or "train" in its name is restricted to rail movement as an RHS house rule. They move as armored units = fast.
Otherwise some Russian artillery was reworked, adding observers or aircraft spotters - or converting one to the other. The spotters are a poor attempt to help artillery be more likely to engage coastal or riverine targets. I found forums indicating this is an old problem never corrected by code - but we are trying to mitigate it.
A few other locations were reworked as for whatever reason they came to my attention. The reworking process is point specific, but the trend is generally a very slight decline in industry. More important than the totals is that the ability to generate supplies is more correctly modeled where it was vice where it was not. Also, some auxiliary industry is being picked up - mainly repair shipyards. As well, airfield and port builds are more correctly rated, and sometimes locations gained or lost actual starting levels. At the same time, the 1945 Downfall Scenario gets each redefined location modified for 1945 conditions - reflecting then extant industry and stocks and port and airfield levels.
I have begun to define off map locations we may add, and associated entry/exit zones, and links between them. We will add a riverine exit zone on the North map edge - seasonally permitting vessels to reach the Arctic Ocean. We will add a similar exit zone farther east for the West side of the Arctic Ocean itself. These may be able to feed ships to Murmansk - which can also have a rail link to Soviet Union (Tomsk in RHS). We should be able to activate the link to Abadan as well - but units apparently will never use it - because Allied units refuse to enter Russian territory - and vice versa. But it was a truly major supply route - and although I doubt most players will use it - it is an option in a campaign where Russia is hard pressed for supplies. Similarly - supplies can be sent via sea to Murmansk - if we get it working.
On the Eastern Map Edge, I may redefine North Midwest as simply Midwest - and link it to the sea (via New Orleans) - permitting US fleet subs to be built on Lake Michigan (where most were built). We may be able to link that via rail to Norfolk - permitting US ships that start or repair there to be better modeled. I have been thinking about Canada too. But instead of off map movement - or trying to make it work on map - I think we will use the actual (seasonal) river system - which sends supplies by rail to Waterways Alberta (on the RHS map) for river movement. Otherwise civil air cargo was used - and RHS already has given that capability to players with all Canadian and US aircraft organized for that purpose. I see no need for off map development for Canada after all. But the process of defining zones and links and locations has begun.
This is hopefully pretty much the end of the shifting sands of defining a pwhexe standard - so the next phase - generating Monsoon seasonal files - will be faster and easier.
< Message edited by el cid again -- 1/16/2015 5:27:21 PM >
|
Printable Version
RE: RHS Thread: Release 6.10 link, description and plans - 
....GP 
It worked!!!
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread