CHS Scenario update now available - version 2.07
Moderators: Joel Billings, wdolson, Don Bowen, mogami
RE: CHS Scenario update now available - version 2.03
A question for jwilkerson......
If experienced regiments were pulled from the 13th, 116th and 110th divisions to create the 31st and 71st divisions shouldnt the 13th, 116th and 110th divisions be reduced in regards to assault value and experience to reflect this?
If experienced regiments were pulled from the 13th, 116th and 110th divisions to create the 31st and 71st divisions shouldnt the 13th, 116th and 110th divisions be reduced in regards to assault value and experience to reflect this?
- Andrew Brown
- Posts: 4083
- Joined: Tue Sep 05, 2000 8:00 am
- Location: Hex 82,170
- Contact:
RE: CHS Scenario update now available - version 2.03
I have now updated the CHS scenario(s) to version 2.04.
Here is the list of changes:
Changes in CHS Revision 2.04
[ol]
[*]Daily fuel, oil and supply levels of Aden adjusted to more correct levels.
[*]Luganville, Efate, Davao and several bases on the US mainland had some errors in their base or SPS values. Fixed.
[*]The "Mongolian Cavalry Division" is now assigned to Kwantung Army, as the numbered Mongolian Cavalry divisions already are.
[*]The Japanese Mongol Army HQ, arriving 440701, is now also assigned to Kwantung Army.
[*]All LCUs assigned to ABDA command, and all LCUs in Malaya, have had their starting morale values reduced by 5.
[*]The Philippine 93rd Reserve Regiment had Changsha as its planning target. Fixed.
[*]The availability date of the Spitfire Vb is now 1/43 instead of 6/42, and its build rate has been decreased from 40 to 30.
[*]The production rate of the Spitfire VIII has been increased from 40 to 50.
[*]The G4M2 Betty aircraft is now using the correct bitmap number (28 instead of 76).
[*]The 431st, 432nd and 433rd US Army fighter squadrons now appear as reinforcements in Brisbane on 430701, and with only 2 aircraft (P-38G) per squadron. The starting experience of these squadrons has also been increased from 55 to 65.
[*]No.607 Squadron RAF added, arriving at Aden on 420615, equpped with Hurricane IIb aircraft.
[*]The availability date of the SB2C Helldiver is now 8/43 instead of 1/43. Although it was first assigned to squadrons in early 1943 there were problems with thei aircraft and delays in their deployment. The production rate has been increased from 200 to 240 to compensate for this later availability.
[*]HMAS Kanimbla (6640) was mis-spelled "Kanimba". Fixed.
[/ol]
CHS is available for download from the CHS Download page at my WitP website.
As always, many thanks to those who have picked up errors in the scenario, and to those who are helping to host the various files.
Andrew
Here is the list of changes:
Changes in CHS Revision 2.04
[ol]
[*]Daily fuel, oil and supply levels of Aden adjusted to more correct levels.
[*]Luganville, Efate, Davao and several bases on the US mainland had some errors in their base or SPS values. Fixed.
[*]The "Mongolian Cavalry Division" is now assigned to Kwantung Army, as the numbered Mongolian Cavalry divisions already are.
[*]The Japanese Mongol Army HQ, arriving 440701, is now also assigned to Kwantung Army.
[*]All LCUs assigned to ABDA command, and all LCUs in Malaya, have had their starting morale values reduced by 5.
[*]The Philippine 93rd Reserve Regiment had Changsha as its planning target. Fixed.
[*]The availability date of the Spitfire Vb is now 1/43 instead of 6/42, and its build rate has been decreased from 40 to 30.
[*]The production rate of the Spitfire VIII has been increased from 40 to 50.
[*]The G4M2 Betty aircraft is now using the correct bitmap number (28 instead of 76).
[*]The 431st, 432nd and 433rd US Army fighter squadrons now appear as reinforcements in Brisbane on 430701, and with only 2 aircraft (P-38G) per squadron. The starting experience of these squadrons has also been increased from 55 to 65.
[*]No.607 Squadron RAF added, arriving at Aden on 420615, equpped with Hurricane IIb aircraft.
[*]The availability date of the SB2C Helldiver is now 8/43 instead of 1/43. Although it was first assigned to squadrons in early 1943 there were problems with thei aircraft and delays in their deployment. The production rate has been increased from 200 to 240 to compensate for this later availability.
[*]HMAS Kanimbla (6640) was mis-spelled "Kanimba". Fixed.
[/ol]
CHS is available for download from the CHS Download page at my WitP website.
As always, many thanks to those who have picked up errors in the scenario, and to those who are helping to host the various files.
Andrew
- jwilkerson
- Posts: 8250
- Joined: Sun Sep 15, 2002 4:02 am
- Location: Kansas
- Contact:
RE: CHS Scenario update now available - version 2.03
ORIGINAL: AdmSpruance
A question for jwilkerson......
If experienced regiments were pulled from the 13th, 116th and 110th divisions to create the 31st and 71st divisions shouldnt the 13th, 116th and 110th divisions be reduced in regards to assault value and experience to reflect this?
They were each reduced by losing their 4th regiment to the triangularization process.
WITP Admiral's Edition - Project Lead
War In Spain - Project Lead
War In Spain - Project Lead
RE: CHS Scenario update now available - version 2.03
ORIGINAL: Andrew Brown
[*]The 431st, 432nd and 433rd US Army fighter squadrons now appear as reinforcements in Brisbane on 430701, and with only 2 aircraft (P-38G) per squadron. The starting experience of these squadrons has also been increased from 55 to 65.
Is that increase just for the two pilots? The rest will draw from the pool?
- ny59giants
- Posts: 9902
- Joined: Mon Jan 10, 2005 12:02 pm
RE: CHS Scenario update now available - version 2.03
I think they get all the pilots, but only two planes.
Talk about some serious games of "rock, paper, and scissors" to see who gets to fly daily. [:D]
Talk about some serious games of "rock, paper, and scissors" to see who gets to fly daily. [:D]
[center]
[/center]
[/center]RE: CHS Scenario update now available - version 2.03
It appears as if all the Allied LCUs outside of China have had all their "future objective " points removed.
- Andrew Brown
- Posts: 4083
- Joined: Tue Sep 05, 2000 8:00 am
- Location: Hex 82,170
- Contact:
RE: CHS Scenario update now available - version 2.03
ORIGINAL: AdmSpruance
It appears as if all the Allied LCUs outside of China have had all their "future objective " points removed.
Well, I have found that in my enthusiasm to clean up the planning targets I removed the planning for two Australia Independent companies, but everything else looks OK so far. The Chinese, Soviets and fixed CD units all look OK. If you think there is another problem with the planning for the Allied LCUs please let me know.
Andrew
RE: CHS Scenario update now available - version 2.03
Will there be a v2.05 with any major corrections? I will start a game against the AI soon but I don't want to start over and over again. [:D]
RE: CHS Scenario update now available - version 2.03
Why not wait until 3.0? 
-
rockmedic109
- Posts: 2441
- Joined: Tue May 17, 2005 11:02 am
- Location: Citrus Heights, CA
RE: CHS Scenario update now available - version 2.03
I started a capaign with 2.0 and dropped it due to the very low levels of daily supply at Aden. I retarted one at 2.02. I think I will maintain this one unless someone finds a game-breaking error. AB said the 10,000 HI at United States shouldn't be a problem. The changes in 2.04 are nice, but don't seem worth it to dump my current campaign.
So far, so good {againts the Japanese AI}. Singapore stringbags have torped an impressive number of transports, but the AI has been aggressive in beating Singapore down and I've moved them out. The Dutch put a 250 pounder into Zuikaku, KXII a torp into Haruna, Fuso hit a mine and Tarpon put a torp {that actually exploded!!!} into Mutsu. Lots of {player} morale raises if little actual damage done.
So far, so good {againts the Japanese AI}. Singapore stringbags have torped an impressive number of transports, but the AI has been aggressive in beating Singapore down and I've moved them out. The Dutch put a 250 pounder into Zuikaku, KXII a torp into Haruna, Fuso hit a mine and Tarpon put a torp {that actually exploded!!!} into Mutsu. Lots of {player} morale raises if little actual damage done.
- Andrew Brown
- Posts: 4083
- Joined: Tue Sep 05, 2000 8:00 am
- Location: Hex 82,170
- Contact:
RE: CHS Scenario update now available - version 2.03
ORIGINAL: Seeadler
Will there be a v2.05 with any major corrections? I will start a game against the AI soon but I don't want to start over and over again. [:D]
There will be a 2.05 very soon, as I did make an error whan I "cleaned" up the LCU planning target mess back in 2.00-2.01. A number of Allied LCUs in the Philippines, Malaya and the DEI accidentally had their planning points removed, and I have now had to reinstate them. I would class this as "annoying" rather than game-breaking, but it does provide an advantage to the Japanese in the early stages of the war.
Andrew
- Andrew Brown
- Posts: 4083
- Joined: Tue Sep 05, 2000 8:00 am
- Location: Hex 82,170
- Contact:
RE: CHS Scenario update now available - version 2.05
The CHS scenarios are now updated to 2.05. I am hoping that I have finally managed to clean up the problems with the planning targets. All of which came about, I think, when I used the editor to move some LCUs around. Don't do that!
Here are the changes added to 2.05:
Changes in CHS Revision 2.05
[ol]
[*]In the LCU target cleanup done for CHS 2.02, Allied LCUs that had planning values greater than 0, but had no target set, had their planning values set to 0. This was mistaken, however, as the program defaults to "own base" if the planning target for an LCU is not set. This meant that some Allied mobile LCUs in the Philippines, Malaya and the DEI did not have their proper planning values and targets set. This has now been corrected.
[*]All Dutch coastal gun regiments and garrison units in the DEI now have planning targets set to their own base, and planning values of 25. Previously, some of these LCUs had 50 planning points for their own base, and the others had 0.
[*]33rd Japanese Division planning target changed from Rahaeng (already Japanese controlled) to Rangoon.
[*]The Tribal class DD HMAS Bataan added to the scenario in CHS 2.00 has been removed, as it is already in the CHS database (ship 3714).
[/ol]
The scenarios are available from my CHS Download web page.
As always, please let me know if you find further problems.
Andrew
Here are the changes added to 2.05:
Changes in CHS Revision 2.05
[ol]
[*]In the LCU target cleanup done for CHS 2.02, Allied LCUs that had planning values greater than 0, but had no target set, had their planning values set to 0. This was mistaken, however, as the program defaults to "own base" if the planning target for an LCU is not set. This meant that some Allied mobile LCUs in the Philippines, Malaya and the DEI did not have their proper planning values and targets set. This has now been corrected.
[*]All Dutch coastal gun regiments and garrison units in the DEI now have planning targets set to their own base, and planning values of 25. Previously, some of these LCUs had 50 planning points for their own base, and the others had 0.
[*]33rd Japanese Division planning target changed from Rahaeng (already Japanese controlled) to Rangoon.
[*]The Tribal class DD HMAS Bataan added to the scenario in CHS 2.00 has been removed, as it is already in the CHS database (ship 3714).
[/ol]
The scenarios are available from my CHS Download web page.
As always, please let me know if you find further problems.
Andrew
RE: CHS Scenario update now available - version 2.05
Getting ready to start a team PBEM with 2.05 and scenario 157. Will keep you updated
jw
jw
RE: CHS Scenario update now available - version 2.05
Played 2.04 experimental version against IJ AI until Feb 42 now and I must say looks good. Somehow I think AI is bit better organized in it's attack, even though I have been able to slow it down about a month from historical dates here and there. Is it because of returning to original slots with units ? I take there were lot of hard-coded scripting to allow historical attacks for Japanese AI ?
"To meaningless French Idealism, Liberty, Fraternity and Equality...we answer with German Realism, Infantry, Cavalry and Artillery" -Prince von Bülov, 1870-


- Andrew Brown
- Posts: 4083
- Joined: Tue Sep 05, 2000 8:00 am
- Location: Hex 82,170
- Contact:
RE: CHS Scenario update now available - version 2.05
ORIGINAL: Sardaukar
Played 2.04 experimental version against IJ AI until Feb 42 now and I must say looks good. Somehow I think AI is bit better organized in it's attack, even though I have been able to slow it down about a month from historical dates here and there. Is it because of returning to original slots with units ? I take there were lot of hard-coded scripting to allow historical attacks for Japanese AI ?
I definitely think that is a factor. I don't think the slot numbers of LCUs were taken into consideration in the old CHS scenarios, but I have tried to restore as many as possible to their original positions this time around.
Andrew
RE: CHS Scenario update now available - version 2.05
V2.05:
Ship Class 1356 (AVD Ballard, 4/43) upgrades to 1325 (APD Manley, 3/44). [&:]
Ship Class 1327 (PG Taney, 2/44) upgrades to 1328 (Treasury AGC, 11/44). Not sure about this one.
Pontianak (BaseID 500) has ABDA as Command HQ, but "Commonwealth" as nationality?
Bagui (BaseID 322) and Lucena (BaseID 323) are the only bases with "Philipines" (sic!) as nationality.
--------
I started messing around with the Datase Editor and have a question: there are 20 wpn-slots for each entry in "Ships" and "Classes". I assume that the wpn-entries in "Ships" override the entries in "Classes" in case a ship has a different equipment than the class default. But what happens after the first upgrade? Do all ships revert to the standard equipment of their class? Is there no room for variation left after the first upgrade?
Ship Class 1356 (AVD Ballard, 4/43) upgrades to 1325 (APD Manley, 3/44). [&:]
Ship Class 1327 (PG Taney, 2/44) upgrades to 1328 (Treasury AGC, 11/44). Not sure about this one.
Pontianak (BaseID 500) has ABDA as Command HQ, but "Commonwealth" as nationality?
Bagui (BaseID 322) and Lucena (BaseID 323) are the only bases with "Philipines" (sic!) as nationality.
--------
I started messing around with the Datase Editor and have a question: there are 20 wpn-slots for each entry in "Ships" and "Classes". I assume that the wpn-entries in "Ships" override the entries in "Classes" in case a ship has a different equipment than the class default. But what happens after the first upgrade? Do all ships revert to the standard equipment of their class? Is there no room for variation left after the first upgrade?

RE: CHS Scenario update now available - version 2.05
The following ship classes have duplicate radar devices (not sure if this is correct, just pointing it out):
ID Type Name Available Radar Devices
1219 BB Colorado 1942.04 SC Radar, SC Radar
1214 BB New Mexico 1942.10 SC Radar, SC Radar
1217 BB Tennessee 1942.04 SC Radar, SC Radar
1552 SS Tench 1945.01 SJ Radar, SJ Radar
158 SS Type STS 1945.05 Type 22 Radar, Snorkel, Type 13 Radar, Type 22 Radar
571 DD Hatsuharu 1943.09 Type 22 Radar, Type 22 Radar
ID Type Name Available Radar Devices
1219 BB Colorado 1942.04 SC Radar, SC Radar
1214 BB New Mexico 1942.10 SC Radar, SC Radar
1217 BB Tennessee 1942.04 SC Radar, SC Radar
1552 SS Tench 1945.01 SJ Radar, SJ Radar
158 SS Type STS 1945.05 Type 22 Radar, Snorkel, Type 13 Radar, Type 22 Radar
571 DD Hatsuharu 1943.09 Type 22 Radar, Type 22 Radar

- DuckofTindalos
- Posts: 39781
- Joined: Fri Apr 22, 2005 11:53 pm
- Location: Denmark
RE: CHS Scenario update now available - version 2.05
They're meant to have that. The ships had more than one radar set in real life, and the two separate mounts prevent both being knocked out by a single hit.
We are all dreams of the Giant Space Butterfly.
- Andrew Brown
- Posts: 4083
- Joined: Tue Sep 05, 2000 8:00 am
- Location: Hex 82,170
- Contact:
RE: CHS Scenario update now available - version 2.05
ORIGINAL: Terminus
They're meant to have that. The ships had more than one radar set in real life, and the two separate mounts prevent both being knocked out by a single hit.
That may be the case for the BBs (and for the Japanese DD? not sure), but I think in the case of the subs this is an error, and the duplicate sets should be removed.
Andrew
RE: CHS Scenario update now available - version 2.05
ORIGINAL: Andrew Brown
ORIGINAL: Terminus
They're meant to have that. The ships had more than one radar set in real life, and the two separate mounts prevent both being knocked out by a single hit.
That may be the case for the BBs (and for the Japanese DD? not sure), but I think in the case of the subs this is an error, and the duplicate sets should be removed.
Andrew
Tench class came with "SD/SK air search radar, SJ surface search, ST periscope radar"








