RHS Thread: Planned Update 8.20

[el cid again]

Yes. We actually use them for ground support instead of individual bombs.

ORIGINAL: ny59giants

Have you ever looked into having "sticks" for bomb loads vs individual bombs? Back in old WITP days I heard about it. I never saw it in a mod, but thought the idea had validity.

[el cid again]

This display shows Level II map panels using Level I pwhexe.dat files. Use the files just released today.

ORIGINAL: TulliusDetritus

Hello Sid and everyone [:)]

Well, first of all, amazing job you're doing! I had already tried RHS back in 2007 or 2008. Now I will try it again.

Problem is: both in Level 1 and 2 Aden and Abadan bases are messed up I think. I used the map panels and pw files but to no avail. Look:

[el cid again]

Just to be clear, the newly added off map locations described below DO NOT YET
FUNCTION. They must be added before they can be linked. They must be defined in pwhexe.dat before they can be linked. So they have been so defined. But they are not yet linked. If they are successfully linked, the locations will become functional in ongoing games. The other way around - if they were added later - only a new game start could show them. This is an interim stage of development between the Andrew Brown Extended map system and the RHS Extended map system. Note also that we have map art in development for the new map system. My map art is simply a temporary device - to permit both playing games and to permit developers to see the area being worked on - before we have the new art. There are, in fact, two new map styles - a "pretty" one and a board game like one.

[el cid again]

RHS Level II Update Link 2.20
https://onedrive.live.com/redir?resid=3 ... file%2cmsi


This is an expansion of 1.43 adding out year Spring pwhexe.dat files. Next will come Monsoon, then Fall. Other things are worked in only because one must take a break from intensive "pwhexing" or make mistakes.

1.5x series will involve updated pwzone.dat and pwlink.dat files - probably seasonal forms of the latter but not the former. These will be simpler than pwhexe.dat files - one per season but no changes year to year (probably).

1.6x series may involve generating Japan Enhanced Scenario pwhexe.dat files.

1.7x series may involve making more interim map art - it depends on the status of the "main" map project.

Here, we have a comprehensive update in that it involves art, documentation files, scenario files and pwhexe.dat files - but most of the work is in the latter.

There are new Axis air art filmstrips. These rework Axis glider art. Integrated with that are aircraft files, also reworking Axis glider data. And there were changes in how gliders are treated. Instead of being absent in JES scenarios (105 and the future 109), they are now present - but NOT planned for production. I think gliders are a mistake - but the RHS philosophy is "power to the players" - so in JES you can decide to put them into production. And they may well be more worth having now I reworked them. While gliders generally lost a bit of load, they gained range, and they now better model the continuous improvement in capability which the Japanese achieved - never mind they never once used them in combat. What they did use them for - LOC logistics - may well be their most sensible application anyway. Gliders are too vulnerable in enemy airspace - but not so much in the rear. Players report they are finding them useful.

Never mind how Cobra Aus did the Ku-7 art - I have made the "combination" a single tug and glider - because it was most common. Even so, it carries more than a two glider and tug combination of Ku-8s does. The Ku-8 I is called the Gander. The Ku-8 II is called the Goose. The Ku-8 II has a different tug. In the case of the Ku-8s I am using "hacks" - gutted ex bombers cum transport planes - of two different kinds (derived from Ki-21s and Ki-49s, respectively). The Ku-7 uses a Ki-67 I bomber as a tug. These are typical examples and also result in a gradual increase in payload and range over time. In the next round I may add the Ku-1 - which oddly looks like the Ku-7 - because more than 100 were built. The challenge is going to be art - it is tiny and towed by the Ki-51!

AE RHS has used a standard of showing glider tops for tugs (in the case of Axis gliders - the Allies used glider tops). Now we are using old Cobra art to show the glider instead of the tug for the Axis as well. Cobra only did the Ku-7 - but the most numerous gliders were the Ku-8s - so I have improvised these.

At the same time, I added the Me-264 to JES scenarios. Not because it was ever even considered by Japan or offered by Germany. But rather because so many things were offered, including both similar and larger bombers, it is reasonable to assume it was a possibility. And because for the first time we have art. Although it was German art (by Gary Childress I believe), I modified the insignia to Japanese.
Again, as with gliders, I think it is a mistake to buy any as Japan: they are too late and too expensive, too slow, poorly armed and can not fly at high altitudes. But they certainly do have range! I also learned they did not achieve range using internal "bomb bay tanks" as US bombers did: they had very deep wings - and the wings were wet! So the problem in WITP era RHS with the type (when we briefly had it) - of needing too many supply points - is not present in this version. [Drop tanks - including RHS 'internal drop tanks' - consume supply points.]

Gary also did some old types in 1940s colors - so I substituted his new art for 1930s colored forms in the case of the Ki-10 and A4M1.

There may be a bit of eratta folded in, but I cannot think of an example.

[TulliusDetritus]

Hello again Sid,

now yes it works, the Aden, Abadan problem. But in both level 1 and 2, in the AI oriented scenario, one brigade of the 6th australian division is missing. And the whole 3 brigades of the 7th are missing as well (no 7th division at all then).

Regards [:)]

[el cid again]

RHS Level II Update Link 2.20
https://onedrive.live.com/redir?resid=3 ... file%2cmsi


As advertised, this update includes all out year MONSOON seasons of the pwhexe.dat files. Unexpectedly, it also includes revisions of all other pwhexe.dat files due to eratta or omissions. I failed to remember that Andrew Brown's interpretation of the British North Borneo Railroad includes only half its length. This may be a compromise because, except for RHS, AE only has one pwhexe.dat file. And indeed, that railway was hurt by bombing of its bridges (but not before the war begins!). But that railway is famous for being used THROUGHOUT its length IN SPITE of the lack of continuous rail: It is the vital communications infrastructure of its area, and was kept in service by locals, using trucks as prime movers or independent railway vehicles on sections not serviceable by engines. Another issue was the Bridge across the Bhramaputra River. I forgot Andrew has this bridge (not built until 1944) for both road and railroad - in 1941! Before the completion of this bridge, and the upgrading of the Bengal and Assam RR (which both occur in Spring 1944), it was a six week journey from Calcutta to Upper Assam. Removing the primary road bridge as well as the rail bridge (until they are built) makes river traffic assume more of its historic role as well as impose major logistical constraints on the Allies in Assam early in the war. As well, two vital primary roads - to Imphal and to Akyab - do not yet exist in 1941. Support for Allied air bases and ground operations in the area depends a great deal on riverborne logistics, and that is vulnerable to enemy air power. The Bhramaputra River is a major barrier to land movement of supplies and troops - road and rail links require moving far up the Ganges - and then back down the other side - on fairly limited networks. There were also a few bad hexsides - mainly ocean or both instead of land - needing correction. I am quite pleased with the "final" set of files (absent the Fall season except for 1942, and absent Japan Enhanced Scenario versions). They use the Matrix system (primary or secondary roads or trails in all directions when and where appropriate) as well as the RHS system (primary and secondary roads or trails where they really run in rural areas - which is much of the map - to channel movement along the lines it almost had to move along).



Another major effort went into working on air art. Both sides get full sets of new air art filmstrips. Some of these rework the very worst cases in the collection of art. And for the first time I made proper alpha's myself (instead of copy and paste or modification and paste of pre-existing alpha's). Both these were cases where I had black and white art - lending itself to making an alpha by a one step process instead of the more usual, complicated one involving several steps.



I began to work on air art so I could add the Ku-1 light transport/training glider for Japan. It is assigned to the Raiding Training Regiment - in keeping with the doctrine that says an airborne unit should own its own transports. [JAAF was the only service in history to do this, following German advice even the German's themselves never implemented.] The Raiding Training Regiment is also unique in another respect - it conducted operational combat jumps as training! [This in China, until midwar, when it was dissolved in favor of more line units.] So the Raiding Training Sentai, in spite of being a training organization, also may conduct operational jumps - if a player wants to. It disbands on the same day the Raiding Training Regiment does, mid war. The unit also could upgrade to Ku-8's or other gliders - or to transport planes - when these become available. The Ku-1 is a very small, slow glider of limited capacity towed by a Ki-51! This required an entirely new set of art be created. In the process, I became concerned about RHS glider data. Gliders are unusual - they have no power per se - so how did I calculate maneuverability (using the RHS formulas)? We fly "combinations" of glider and tug - how does that affect durability and range? I decided to add written notes to the normal plane definitions and rework all glider units to insure consistency.



FYI gliders work precisely the same as air transports do. This is because gliders can “take off” by being “snatched” from the ground – particularly in Asian operations. However, they have peculiar characteristics. The primary trade-off is payload for range: a glider unit “combination” will always have less range than the tug has, and will also always carry more payload than the tug can (if it carries any at all – the Ki-51 as tug for a Ku-1 has no useful load. Also, it is so small a plane, it tows only one glider.

Most other glider combinations in the game involve transport (or bomber-transport) aircraft which may tow two medium sized gliders. But the one large glider in the game – the Ku-7 (which was a scaled up

Ku-1 – complete with its twin booms0 – is towed by a Ki-67 I bomber. In spite of only one glider per tug, and no cargo on the tug, it still has the greatest capacity of any combination in the game – 16,000 pounds

(= 1 8 ton tank). Normally, air transports in RHS are rated by troop capacity on the basis of 100 kg (220 pounds) per troop. However, gliders (and a few dedicated air cargo aircraft) are rated for their capacity in pounds - because they are used to lift vehicles, guns and other heavy cargo – and must be so rated in order to actually lift them.



Reviewing Allied gliders, I found only one type used in PTO – although by multiple nations. The Waco CG-4 (sometimes with other names) – was used by RAF, RAAF, USAAF and maybe the USMC. The art is fully reworked – we lost the D-Day invasion stripes for example. We went over to glider art rather than tug art for tops (previously used in AE RHS – a reversion to WITP era RHS – using Cobra’s art for WITP as a foundation). The insignia cannot be recognized (it is present) due to small size. So I use the same art for three different plane types: RAF, RAAF and USAAF – permitting proper control of upgrades and rates of production. [RAF and RAAF were added.] These three all are three aircraft “combinations” involving a C-47 and two CG-4s – but the RAAF type is called Hadrian instead of CG-4 – while the RAAF uses the CG-4 as such because they came direct from the US (with US paint scheme). The US form comes early – mid 1942 – and stays in production. The RAAF from is limited in number and all appear in February 1943 (when they were transferred). The RAF form is late war (for operations out of India) – but stays in production once they start to arrive.



This led me to wonder how the RAF functioned – late war it gets a real “airborne” division. [This is a composite unit – a real airborne brigade, an airlanding brigade, and a heavy brigade. IF these three ever combine – they become a ground unit unable to conduct airborne assault – but are better able to fight heavy ground units.] How was the airmobile unit to fly – with so few RAF air transport assets? Review led to discovery that 48 Squadron – about double the size of PTO RAF units – transferred to India in 1945. Also that six squadrons formed in India in late 1944 and early 1945 – these latter all glider units. So all these have been added.



Another addition is pure chrome. There was one specialized USMC glider unit – VML-711 (and nominally Marine Glider Group 41, but with no other squadrons formed, for a brief period). Along with most other Marine special forces, it was disbanded in 1943 (in favor of more, large assault divisions). It also was

never sent anywhere. As chrome, an in keeping with “power to the players” RHS design philosophy, if a player ever finds an (early war) job for the unit, it may be transferred from the East Coast to PTO. It gets 12 (of the 13) gliders actually transferred by the Army to the Navy (for Marine use). I did not create a separate type for this unit – it must use Army gliders or convert to USN/USMC air transports. I also added its commander – and he will transfer to the pools when the unit disbands – a highly rated air transport pilot as well as a unit leader.



I tried to add Russian and Canadian gliders, but failed. The Canadians didn’t use the Hadrian, but an earlier training glider – and apparently never in operations (just as part of the Empire Air Training Scheme). The Russians made few gliders, and the only type that might have been able to share art (using a Russian LI-2 version of the C-47 as tug) was not mass produced. The Russians only built about 100 small gliders for operations, and abandoned their use after the Dnieper River crossing (which was a success) – probably not having enough to lift a significant force after that.



Stuck with down communications, I also reviewed locations, finding 10-12 cases with eratta and 1 base force assigned to the wrong base in one scenario (detected because that location had two instead of one base forces as in other scenarios). There were a few other aircraft and air group eratta detected and worked in.



The next update will include all the post 1942 FALL pwhexe.dat files. Then I will tackle the pwzone.dat and pwlink.dat files. There will apparently be one RHS pwzone.dat file and four (seasonal) pwlink.dat files.

[el cid again]

UPDATED: I loaded a new game. 6th and 7th divisions appear at Aden in their component parts.
However, not all are yet at Aden when the game starts. Be patient. They will arrive when they
really did get there. Look at the ground reinforcements list - they are present.

8th division is sub divided into two brigades and three battalions.
The three battalions MUST combine into a brigade before the division may assemble into a whole.
But it can and I do recommend it be so formed.

Something isn't right. We have all three divisions in test games. Try the new link

RHS Level II Update Link 2.20
https://onedrive.live.com/redir?resid=3 ... file%2cmsi

ORIGINAL: TulliusDetritus

Hello again Sid,

now yes it works, the Aden, Abadan problem. But in both level 1 and 2, in the AI oriented scenario, one brigade of the 6th australian division is missing. And the whole 3 brigades of the 7th are missing as well (no 7th division at all then).

Regards [:)]

[TulliusDetritus]

Hello Sid, [:)]

well, all I can tell is what I'm saying is indeed true, unless I am missing something [&:] See:

[TulliusDetritus]

Look at the reinforcement list:

[TulliusDetritus]

On the other hand, the 6th and 7th divisions indeed appear at least in the Russian passive scenario aka scenario number 123.

[el cid again]

I did not realize you were using 102. Turns out, all even numbered scenarios, in both level I and II,
have problems with AIF. In simplified, all the sub units are supposed to be gone - but the PARENTS
should appear. I will address this in today's work.

ORIGINAL: TulliusDetritus

Hello Sid, [:)]

well, all I can tell is what I'm saying is indeed true, unless I am missing something [&:] See:

[el cid again]

Level II Update Link 2.72
https://1drv.ms/u/s!Ap7XOIkiBuUwhYgdhnbHRnhTAFX2OQ

While this update includes all out year Fall pwhexe.dat files - it also includes every
other pwhexe.dat file reworked! This is the complete set of pwhexe.dat files for standard RHS (strictly historical) scenarios.

It also includes a major review of location files because of problems reported with
units not appearing in Scenarios 102, 104 and 106. These are "simplified RHS" scenarios and some sub units do not appear. But if the sub unit had a pointer at a parent, the parent also could never form. It turns out a small number of units on both sides in all scenarios were affected, although mainly it was even numbered ones. It affected Aussie 7th and 8th Divisions, the ROC First Marine Regiment, and about three IJN Combined SNLFs.

In addition to the above, about three Soviet Outpost base forces, and one location,
were added. We now can see how aircraft could fly from Alaska to the middle of the USSR? These bases may matter if Russia is drawn into a war in the Far East. The last one turns out to be on the Road of Bones and probably explains why it was built (when numbers of other projects were suspended). Except for map related developments - some units will change bases when we are sure the three new off map locations and the one new entry zone to be added all work - file development is complete except for correcting eratta. From now on work is going to focus on the map: linking locations and zones (some new combinations) and creating interim map art to better show the new material.

[TulliusDetritus]

ORIGINAL: el cid again

Level II update link 1.44
https://onedrive.live.com/redir?resid=3 ... file%2cmsi

Hello again Sid,

You fixed the Aussie divisions problem [:)]

Many thanks for your patience and effort [&o]

[el cid again]

Be SURE to put the pwhexe.dat file in the top level AE folder - it is NEW a
and IMPORTANT.

Level II Update Link 2.52
https://1drv.ms/u/s!Ap7XOIkiBuUwhN0ESrPbLJB7u3ZwXQ


I forgot I needed to review aircraft devices, particularly for late war aircraft which are virtually never tested in games. In particular, I was worried about atomic bombs (RHS has its own devices) and missiles.

I found numbers of issues, large and small, affecting devices, aircraft, groups, and leaders. In the process I reworked RHS atomic bomb devices, aircraft and groups - and leaders for them - extensively. In particular, I assigned about 8-10 command pilots to the 393rd Bomb Squadron. This "unit" is presented as four sub units which may NOT combine. Three are one plane detachments which may either fly with B-29 Silverplate PB (pumpkin bombers) or (eventually) with either B-29 Silverplate IB (implosion bombers for Fat Man type implosion bombs) or B-29 Slverplate UB (uranium bombers for Little Boy gun type bombs). These units now all appear at Tinian (or, if it is not Allied controlled, San Francisco) on 30 May, 1945 - the date they really arrived. NO atomic bomb armed aircraft are available. Instead, all four units have the B-29 Silverplate PB - a gigantic conventional bomb the same size as an atom bomb. This was done to permit training of crews in operational conditions. The detachments that bombed Hiroshima and Nagasaki have their historical commanders. Since the squadron commander was also the Hiroshima command pilot, the XO is the commander of the "main body" of the squadron. The Ops officer and other pilots who flew the primary or secondary aircraft on each historical mission, or who where scheduled to fly but could not due to illness, are also included.

The atomic bomb devices had to be moved to different slots, and altered somewhat, to both display and work. RHS uses a combination of 24 different bomb devices for each atom bomb, statistically modeled to result in the UB (gun type uranium fueld bomb) being slightly more reliable, with a realistic potential variation in yield, and with different weight for the different bomb types. While a "dud" bomb is possible, it is very unlikely, and still will cause damage. Much more likely is a variation in yield, with only about a 20% chance of a larger than expected explosion (as actually occurred at Nagasaki). It hardly matters: even dud events are nasty, big bombs, and there will be between 20 and 24 non-dud sub-bomb devices per attack.

Alarmingly, not one missile (Allied or Axis) appeared at all! But that turned out to be because of a code glitch and I found a workaround. They both appear and work, somewhat to my surprise. [I was prepared to simulate missiles with other devices, but missile code appears to work fine.] A similar problem existed for "smart" (i.e. guided) bombs - but again it was a weird glitch in code preventing them from appearing - and one can defeat it by setting them to a game start date and letting the availability of the aircraft determine when you can use them?

There were problems with integration of devices and aircraft in terms of dates. I reworked the blimps as well, permitting 18 cancelled M type (longer range) to appear in addition to the 4 completed in Japan Enhanced Scenarios. Note that RHS blimps are NOT stock AE blimps. Although they only have base forces on the West Coast (all three historical ones), they can probably work with ships or other groups capable of being assigned ASW aircraft. USN experimented with support by ships, and one such ship (with its gigantic mast) is in the game. There are four "classes" of blimps, essentially differing in the quality of their radar and their depth bombs over time.

There was a problem with the only operational AAM used operationally during WW2. This is a German product only found in Japan Enhanced Scenarios on a Ju-88 variant late in the war. It too didn't want to appear - for the same reason as atomic bomb and missile devices which were previously invisible. This glitch only seems to matter for devices appearing in 1945 (or, if there were any, almost certainly in 1946), and only for aircraft weapons - not sensors or non aircraft devices. The "fix" is to lie about date - which does not matter if the aircraft do not appear before 1945.

It is possible there is some location file eratta worked in - I am not clear if any have occurred since the last update.

Supplimental:

I failed to mention there is a new set of Axis air art filmstrips.

Discovering a source with dozens of potentially useful images, I surprisingly
rejected all of them because none was better than we have already. But I
became inspired and reworked two sets of are images (there are three
elements for every aircraft).

I decided to get rid of the Ku-7 large glider in the side art for the Ku-8. This side
art was created by Cobra in WITP days, and apparently he got the numbers mixed
up. I took a Ku-7 black and white photograph, colored it, and reduced it - putting
it into the image for the "combination" behind the tug. This is more like the Allied CG-4 combination - which also was created by Cobra long ago. At the same time, I reworked the top and alpha slightly. These are not really glider art at all, but modified transport art, and if the removal of the engines worked, the front end had the wrong shape. It is slightly better now.

I also decided to make the Ku-1 art similar to the other gliders (three variations of the CG-4, the Ku-7 and Ku-8) - showing the combination rather than just one glider. That side is not very great to begin with - based on a drawing with little detail. It looks better if reduced anyway. So I reduced it and put it on top of the former Ku-7 in the single glider and tug combination art I made a few days ago. I then took a Ki-51 side and replaced the tug in that same art. Now we have proper combination art for the Ku-1 - and it looks better I think - as well as being more consistent with how we present other combinations.

[el cid again]

RHS Level II Update Link 2.20
https://onedrive.live.com/redir?resid=3 ... file%2cmsi


This is a copy of email sent to the RHS distribution list. It lacks
attachments - but the critical new product has a link here below.

In my study of the pwlink.dat and pwzone.dat files has led to some
new products.

Ranges between off map ports were generally incorrect. This file
ONLY fixes that issue for EXTENDED MAP SYSTEM games.

My review of the original files produced for the extended map system
discovered a number of range eratta. For that reason I have
created a new version of the pwlink.dat file, which is here attached
with the prefix RANGEMODIFIED. This is also tested and works well.
Changes are fully documented in the attached spreadsheet.

This new pwlink.dat file is IDENTICAL to Andrew's EXCEPT for the range between ports. These ranges are now derived from the Distance Between Ports navigation
publication.

There are 28 pairs of entries. Each pair was and remains complimentary -
the distance one way = the distance the opposite way between any pair of ports.
Four pairs had perfect ranges (to the nearest hex). 12 pairs over stated the
ranges (up to 13.3%). 12 pairs understated the ranges, up to 65.2% - with
a couple of other huge errors.

This new file is suitable for use with ANY scenario designed to use Andrew Brown's Extended Map System. At this time, that INCLUDES RHS Level II. It DOES NOT
include RHS Level I - which uses the stock map system.

My next product - today or tomorrow - will be the same file for the standard map system.

AFTER that I will modify the extended map system to become the RHS Extended Map System. Essentially it will be an expanded version of Andrew's original.

The effect of using this file is that it will correct ship transit times for Allied task forces using off map movement.

A link to the new pwlink.dat file is here below

Revised link

Full Update link

[m10bob]

Hello Sid..Still very interested in RHS. I was able to download one of the links you provided, allowing me to create one RHS game, but when trying to obtain updated files, I get an error message stating I cannot get further updates as I already have a file with same name.(?).
I suspect it will allow me to upload your most recent links only if I delete the entire prior files, (which is not how you did things with the original RHS, (which I helped you on, along with Peter...aka CobraAus).

I am not able to get any e mails to you...all marked undeliverable.

I use AOL for e mail.

None of my comments were answered on your other topics...and I recall you are a busy person.

NOTE: In the main WITP AE forum...I just started a new quiz asking folks to identify a plane.
Here is the Chinese version of that plane.

[el cid again]

Aol had some problems in the last 48 hours - and again this morning. I had to reset my AOL altogether.
I am sending you my email address. [Correction - the problem was local. My ISP had a fibre optic cable
cut! Couldn't get to or from AOL.]

Normally old files should overwrite new ones using the Advanced Installer.

Your plane appears to be one of the Lockheed transports - maybe an L-18.
It is just a bit larger than an L-14.

ORIGINAL: m10bob

Hello Sid..Still very interested in RHS. I was able to download one of the links you provided, allowing me to create one RHS game, but when trying to obtain updated files, I get an error message stating I cannot get further updates as I already have a file with same name.(?).
I suspect it will allow me to upload your most recent links only if I delete the entire prior files, (which is not how you did things with the original RHS, (which I helped you on, along with Peter...aka CobraAus).

I am not able to get any e mails to you...all marked undeliverable.

I use AOL for e mail.

None of my comments were answered on your other topics...and I recall you are a busy person.

NOTE: In the main WITP AE forum...I just started a new quiz asking folks to identify a plane.
Here is the Chinese version of that plane.

[m10bob]

This is a Boeing 247...very common passenger plane in CONUS in the thirties and early forties.
The USAAF took over approx 30 examples and of course China had a few, one flown by the Generalissimo's son.
USAAF called it the C-73





Does this newest file allow the off map ports to work?..Really like the Gulf of Mexico port idea, especially since all the theater LST's and P 47's came from Evansville on the Ohio.

[el cid again]

Most of the emails came back rejected. So here is a link instead.

generic pwzone.dat file for all extended map mods
https://onedrive.live.com/redir?resid=3 ... file%2cdat

This file is another building block toward getting new off map locations to work.
In fact, just as the pwhexe.dat files and location files must define them, so
must the pwzone.dat file. Now to get a matching pwlink file to compliment
them.

This development required a new editor be written - in fact it was rewritten twice.
Similar new pwzone.dat and pwhexe.dat editors will be written soon - now we have
clearly established that the new pwzone.dat editor works on the new, wider monitors
and laptops of this era. These new editors only are for wide screen displays -
they work fine on high resolution and less wide displays already.

In fact, there already are new pwzlink.dat files for both standard and extended map systems. These correct range errors between off map ports. Now I will add links to specifically RHS off map ports, which are defined in this file for the first time.

[TulliusDetritus]

Hello again Sid,

well, in scenario # 122 ie Level II AI oriented scenario, the Russians are active. The sneaky and treacherous Japanese hordes attacked targets on Russian soil the 7 december itself - the poor things. Plenty of Soviet ships arrived on the next turn -supposed to arrive historically by august 1945. The Red Army is at the ready that is. I mean, this should not be happening. The Japanese should not be attacking the Russian bear (Hitler is happy though, that might stop the Moscow Counteroffensive initiated the 5 december) [:)]

Regards