RHS 5 & 6.758 comprehensive update uploaded/frozen/final?

[el cid again]

ORIGINAL: Jo van der Pluym

I have find a small error.

The Soviet 13 Naval Brigade has Indian Nationality

Because it is copied from an Indian airborne brigade. The airborne code does not appear in the editor - so only by this means - or using a different tool - can one make an air borne unit. Thanks.

[Dili]

Explain the errors you see in detail.

 
Kashima Shotai converting to E13A1 Jake aboard LST-910
Hosho Atk Chutai converting to B5M/B5N Kate aboard LST-736
Nagato Shotai converting to F1M2 Pete-FF aboard LST-779
Mutsu Shotai converting to F1M2 Pete-FF aboard LST-780
Fuso Shotai converting to F1M2 Pete-FF aboard LST-798
Yamashiro Shotai converting to F1M2 Pete-FF aboard LST-799
Maya-1 Shotai converting to F1M2 Pete-FF aboard LST-806
Chokai-1 Shotai converting to F1M2 Pete-FF aboard LST-807
Ashigara-1 Shotai converting to F1M2 Pete-FF aboard LST-880
 
-------------------------------
Wasnt supposed to be impossible to convert plane without being in a port? Probably it is broken there. Some this ships change plane while at sea.
 
----------------------------------

Also test RAO to see if it has them? RAO is identical except for one file - easy to fix CVO if it works.

 
RAO 5.559 has also the error.

[keeferon01]

I have 2 Kwajalein Base forces if its of any interest , one located where it should be and another in Palau and both are prepping for Maloelap which is funny because there static [:)] SO54 5.559

[tanjman]

cid,

To make a LCU airborne, type in 13 in the symbol field. To make a LCU cavalry, type in 12 in the symbol field.

ORIGINAL: el cid again

ORIGINAL: Jo van der Pluym

I have find a small error.

The Soviet 13 Naval Brigade has Indian Nationality

Because it is copied from an Indian airborne brigade. The airborne code does not appear in the editor - so only by this means - or using a different tool - can one make an air borne unit. Thanks.

[el cid again]

All well and good - except you cannot see this field in the editor! I get at it via WITP Excel. And that is very dangerous - we believe WITP Excel messes up the location file EVERY time you use it! So we prefer to copy a record - and then modify it to the new form.

[el cid again]

ORIGINAL: Ron James

I have 2 Kwajalein Base forces if its of any interest , one located where it should be and another in Palau and both are prepping for Maloelap which is funny because there static [:)] SO54 5.559

I cannot figure this out - except both Kwajalein and Palau Base Forts were planning for Maleolap. Anyway - this is corrected. Possibly scenario 54 didn't get the updated record - new data provided by Mifune caused some island base forces to gain 6 inch guns. And static CD units do plan for their location. But we make records by copying - and the planning field is not on the default page = often not noticed.

[Dili]

This maybe just an oddity but IJA First Curved Gun REGIMENT has a TO&E like IJA First Curved Gun BATTALION  . Note that the Rgt has right now 150mm Mortars instead the TO&E 81mm.

[el cid again]

ORIGINAL: Dili

This maybe just an oddity but IJA First Curved Gun REGIMENT has a TO&E like IJA First Curved Gun BATTALION  . Note that the Rgt has right now 150mm Mortars instead the TO&E 81mm.

OK - ONLY a 81mm mortar BATTALION should point at formation 925. A 15cm mortar REGIMENT should point at formation 953. Very Heavy Mortar REGIMENTS should point at 0 (themselves).

In IJA a mortar BATTALION has 36 x 81mm mortars. But a 15 cm mortar REGIMENT has only 16 x 150 mm mortars! And the Very Heavy battalions get only 4 tubes - or a VH regiment 8! We had some pointers that should have been zero - used to be 925 when the regiments had 81s - but I converted the regiments to heavier guns when I identified which - and the pointer is not on the default page.

Now - remember - "if it isn't confusing - it isn't Japanese culturally speaking" - the TONE 15 cm GUN Regiment is DIFFERENT from a "curved gun regiment" or battalion. It is ALSO different from a normal 15 cm artillery regiment - in that it has long guns - not 15 cm howitzers. This unit WILL eventually convert to 15 cm howitzers - and its 15 cm guns won't replace as they become casualties!!! [For a while it may have more than the usual number of tubes - depending on supplies and casualties to guns] But it is sort of the "Long Tom" of the IJA - a unit with a good medium field piece of some range - and more than one battalion.

[el cid again]

ORIGINAL: Dili

Explain the errors you see in detail.

Kashima Shotai converting to E13A1 Jake aboard LST-910
Hosho Atk Chutai converting to B5M/B5N Kate aboard LST-736
Nagato Shotai converting to F1M2 Pete-FF aboard LST-779
Mutsu Shotai converting to F1M2 Pete-FF aboard LST-780
Fuso Shotai converting to F1M2 Pete-FF aboard LST-798
Yamashiro Shotai converting to F1M2 Pete-FF aboard LST-799
Maya-1 Shotai converting to F1M2 Pete-FF aboard LST-806
Chokai-1 Shotai converting to F1M2 Pete-FF aboard LST-807
Ashigara-1 Shotai converting to F1M2 Pete-FF aboard LST-880

-------------------------------
Wasnt supposed to be impossible to convert plane without being in a port? Probably it is broken there. Some this ships change plane while at sea.

----------------------------------

Also test RAO to see if it has them? RAO is identical except for one file - easy to fix CVO if it works.

RAO 5.559 has also the error.

RHSEOS does not have the error. This is good news. We will be able to identify the offending file and records - and fix them. It is not universal at this level of development.

EDIT: RHSRAO does not have the error. Yet RHSRAO is IDENTICAL to RHSCVO except for the cam file. So by renaming the cam file (setting Russians to passive) we should have this one fixed. IF there were any other cause than the cam file RAO would also fail.

[Dili]

EDIT: RHSRAO does not have the error. Yet RHSRAO is IDENTICAL to RHSCVO except for the cam file. So by renaming the cam file (setting Russians to passive) we should have this one fixed. IF there were any other cause than the cam file RAO would also fail.

That's strange i have the error in RAO 5.559


But the game should not forbid changing planes at sea? If this going on i can see an A5M4 going to A6M2 at start of the battle if player have update on. Also it is a sign of not checking supply to make the update which scares me of what is going on.

[el cid again]

We have data washed leader, ship class and ship files for all scenarios. [Thanks to Alvrmartin]

We have a new cam file for CVO - because the old one caused spurrious trports. [Reported by Dili]

We have a revised location file re eratta (various reports in the Forum).

We have a revised device file (report of path error by Nemo and probably technical stuff from me)

We may need to revise the HQ file again - it needs cross checking vs EOS - but it is close to perfect.

EOS ship and class files need checking. Same for aircraft and air group files. But the big deal is the location file - of which there are three forms at each level (CVO, BBO and EOS).

This version should run well.

[Dili]

Just played 5.41 EOS came with error too, see in last line:
 
MSW Robin scuttled at Johnston I [USA] to prevent capture!
31st Sentai [BMR] converting to Ki-48-I Lily at Siem Reap [CMB]
51 Ind. Chutai [BMR] converting to Ki-21-II Sally at Phnom Penh [CMB]
52 Ind. Chutai [BMR] converting to Ki-21-II Sally at Taichu [Formosa]
6th Sentai [BMR] converting to Ki-48-I Lily at Kiamusze [Manchukuo]
32nd Sentai [BMR] converting to Ki-48-I Lily at Mukden [Manchukuo]
65th Sentai [BMR] converting to B5M/B5N/Ki-47 Kate at Mukden [Manchukuo]
IMAF 3 Chutai [BMR] converting to Ki-32/30 Mary/Ann at Tsitsihar [MNCHKO]
MKKK Unit [CIVIL] converting to Ki-56/LO Thalia at Harbin [Manchukuo]
67th Sentai [BMR] converting to B5M/B5N/Ki-47 Kate at Tientsin [N China]
66 Ind. Chutai [BMR] converting to B5M/B5N/Ki-47 Kate at Hankow/Wuhan
R2 Shotai/61 Sentai converting to G4M1/Ki-50 Betty at Kalgan [Cent China]
DNKKK I Unit [CIVIL] converting to Ki-34/59/L1N1 Thora at Osaka/Kobe [Honshu]
Katori Shotai converting to E13A1 Jake aboard LST-889

[el cid again]

This is parallel to the other scenarios. However, some specific data washing is required because there are so many unique records. This is a release to get eratta spotted during the data washing process. Also - I expect devices, aircraft, pilots and locations for all scenarios to be washed soon. We are in the wrap up phase. UNLESS there is interest in expanding Allied aircraft - using a unified art scheme - we are done with development.

[el cid again]

ORIGINAL: Dili

Just played 5.41 EOS came with error too, see in last line:

MSW Robin scuttled at Johnston I [USA] to prevent capture!

REPLY: This is not an error: Johnston I was just captured - always happens - and the message means what it says.

31st Sentai [BMR] converting to Ki-48-I Lily at Siem Reap [CMB]
51 Ind. Chutai [BMR] converting to Ki-21-II Sally at Phnom Penh [CMB]
52 Ind. Chutai [BMR] converting to Ki-21-II Sally at Taichu [Formosa]
6th Sentai [BMR] converting to Ki-48-I Lily at Kiamusze [Manchukuo]
32nd Sentai [BMR] converting to Ki-48-I Lily at Mukden [Manchukuo]
65th Sentai [BMR] converting to B5M/B5N/Ki-47 Kate at Mukden [Manchukuo]
IMAF 3 Chutai [BMR] converting to Ki-32/30 Mary/Ann at Tsitsihar [MNCHKO]
MKKK Unit [CIVIL] converting to Ki-56/LO Thalia at Harbin [Manchukuo]
67th Sentai [BMR] converting to B5M/B5N/Ki-47 Kate at Tientsin [N China]
66 Ind. Chutai [BMR] converting to B5M/B5N/Ki-47 Kate at Hankow/Wuhan
R2 Shotai/61 Sentai converting to G4M1/Ki-50 Betty at Kalgan [Cent China]
DNKKK I Unit [CIVIL] converting to Ki-34/59/L1N1 Thora at Osaka/Kobe [Honshu]
Katori Shotai converting to E13A1 Jake aboard LST-889

Except for the last line - NONE of these are errors. AI can upgrade what it wants to when it runs things.
And will upgrade the values programmed if the pools and supplies permit.

Now as for LST-889 - which is not even in play - it is spurrious. The air unit is OK.
The ship is OK. I will do what I can - but this is just a junk message - probably.
There are others - in all mods/scenarios - if you pay close attention.

[tanjman]

cid,

Which editor or you using? The one that came with WitP or War in the Pacific Editor X if you are using the later the symbol field is here:

ORIGINAL: el cid again

All well and good - except you cannot see this field in the editor! I get at it via WITP Excel. And that is very dangerous - we believe WITP Excel messes up the location file EVERY time you use it! So we prefer to copy a record - and then modify it to the new form.

[drw61]

[font="times new roman"]Playing EOS v6.6[/font]
[font="times new roman"] [/font]
[font="times new roman"]We are having the unit upgrade problem again.  (Don't you just love the editor! )[/font]
[font="times new roman"]2381 – IA Assam Rifles upgrade to (2005) USA Lt Tank Bat.[/font]
[font="times new roman"]2715- USA 56th Cst Art reg …… (2047) ANZAC Lt AA Rgt[/font]
[font="times new roman"]2714 -  San Francisco Fort …….(2002) USA 1942 Div[/font]
[font="times new roman"]2651 - Pp Provisional AintTank ……….(2005) USA Lt Tank Bat.[/font]
[font="times new roman"]2667 - USMC Samoan Marine…….. (2009) USA Eng Rgt[/font]
[font="times new roman"] [/font]
[font="times new roman"]All the forts I looked at were upgrading wrong. [/font]
[font="times new roman"]T[/font]here are more that these, if you need a more complete list let me know.

[el cid again]

Editor X didn't exist when we began - so it was not an option. For a while the professionals said "don't use it until it is confirmed safe" - so that slowed its adoption by me. But now the big problem is the number of scenarios I manage (18) - and the way one switches between them in Editor X makes keeping the same record in so many scenarios cumbersome. I have also a couple of technical problems - but today Editor X is one of the tools I use - and I didn't know about that field. That is an easier way and safer way to monitor and modify the symbol than using WITPExcel - which requires a slow import of data and which seems to mess up the location file when it is exported. Thanks.

[el cid again]

ALL: I have 60 pages of ship field error reports to work in. I have a couple of behaviors that may imply cam file corruption - so I am searching for older versions to use to get around them. I have the pointer issues above - and when data washing does location files I am sure many others. We will be issuing x.61 and probably later updates as this material is folded in. This process should take a few days - and possibly last until Tuesday. When it ends Mifune and I will create the Tag Team first turn - and I will start working on Level 7 (with Cobra and Mifune - the RHS Level 7 committee).

[el cid again]

I am uploading 6.61 comprehensive and
a few files at the same level for 5. The difference is I need to do the ships for 5 - and will issue
a 5.51 comprehensive tomorrow.

Other than MASSIVE data corrections in 6,

this includes a handful of eratta in leader, air group and location files.

We are data washing now - and will be for a few more days.

We WILL do new plane art - and apparently ship art will be revised in some sense -
and we WILL add some Allied plane slots. We MIGHT add some Allied planes in the course of this -
or leave empty slots. Plane art slots will now generally = the plane slot - just like the original stock!
But this is FUTURE tense - not at this level. Cobra writes work in progress.

[shawn118aw]

As far as USMC Aviation records go ...

On 31 Aug 1939 there were 323 Pilots (aircrew), On 2 Sept 1945, there were 10,049 Pilots

During that time 1,527 (Officers and Enlisted) Pilots were either killed or listed as missing. So a stright line average of 33 (33.2) per month (7 Dec 41 to 7 Sept 45, 46 months)

So that makes 11,576 Pilots Trained and Reached Operational Status. Again a stight line average of 251 per month, but the chart below shows the build up and level off of the USMC "Pilots" during the war.

Under the Personnel records it lists: date--Pilots, Officer and Enlisted (Operational--not Students in the pipe line)

31 Aug 39--232 Pilots
30 Jun 40--245, 13 new / 6 months (2 per month)
31 Dec 40--425, 180 new (30 per m)
30 Jun 41--505, 80 new (13 per m)
31 Dec 41--659, 154 new (25 per m)
30 Jun 42--1369, 710 new (118 per m)
31 Dec 42--2371, 1002 new (167 per m)
30 Jun 43--5030, 2659 new (443 per m)
31 Dec 43--8359, 3329 new (554 per m) *High mark for the number Trained per month
30 Jun 44--10457, 2098 new (350 per m) **High mark for the war for Total Pilots
31 Dec 44--10441, -16 new ***Here it flat lines so assume about 350 per month
30 Jun 45--10041, -400 new **** Drops from 350 to 283 per month
31 Aug 45--10121, 80 new (13 per m) *****Increase from 283 to 296 (or about 300)

I hope this helps,

Shawn
LtCol, USAF, C130 Pilot