Matrix Games Forums

And they were built in the USA by, of all people, Kaiser!

Sid,

Here's the deal with the Victory ships (as of EOS 6.15).

Slot 6738 - Ames Victory - Delay 999 (actually arrives 07-12-41)

Slot 6754 - Ames Victory - Delay 49999 (actually arrives 07-12-41)



There are many, many Victory and other ships with Delay 9999. I presume that is the code for 'do not arrive' and that you have purposely coded those for off-map SLOC use. If not, there are many, many ships to correct the Delay value.

When of course the delay should be 9999 = never code. And they might come back in Level 7 - for SLOC work.

In order to distribute a version with a number of eratta fixed

and to get players used to new air groups on USN CVEs (to use as "change" if a CV unit resizes)

and to fold in British and Australian army updates to RHS Commonwealth standards

versions 5 and 6 are released at sub version x.19

I will continue this process for the time being -
and attempt to expand Level 7. Level 7 is being kept in parallel with these changes.
Next: pwhex

El Cid,
 
I am playing RHSCVO Scen 60 with 6.19 update.
 
Near New Zealand the Flag Icon for Hamilton (NZ) is located in the ocean at hex 50,138 instead of at land hex 62,126.
 
Is this unique to me?
 
DavidR

El Cid,
 
Apologies , correct land hex for Hamilton is 62,136.
 
DavidR

ORIGINAL: DavidR

El Cid,

I am playing RHSCVO Scen 60 with 6.19 update.

Near New Zealand the Flag Icon for Hamilton (NZ) is located in the ocean at hex 50,138 instead of at land hex 62,126.

Is this unique to me?

DavidR

Nope. It is a record from Level 7 in all Level 6 and Level 5 files! It should not be that way. Hamilton is busted until x.20 release.

ORIGINAL: witpqs

Sid,

Here's the deal with the Victory ships (as of EOS 6.15).

Slot 6738 - Ames Victory - Delay 999 (actually arrives 07-12-41)

Slot 6754 - Ames Victory - Delay 49999 (actually arrives 07-12-41)



There are many, many Victory and other ships with Delay 9999. I presume that is the code for 'do not arrive' and that you have purposely coded those for off-map SLOC use. If not, there are many, many ships to correct the Delay value.

You are correct - this is "never appear" code. 999 is a typo for 9999. So is 49999. However, UNLESS the letters LOC are in the ship name field - your assumption is incorrect. These ships do not appear for one of two reasons (LOC ships excepted):

1) The particular ship never entered PTO;

2) The ship is one of the 50% of ships which haul resources and supplies which are not modeled because of the way the code uses resources relative to oil. [Not enough resources are consumed - so we give you half - and half the ships to move them - and take away the other half that must be there moving the resources that must be moved - but which would not be eaten by industry. We let the half you have model them all.]

Much of the eratta and suggestions of the past few days are incorporated into 5 and 6 versions 20.

I will work for two days - then attempt to take the next two days to whip out Level 7.

I will do the pwhex files - which are almost done - for 5 and 6 - to get the RR right in Russia/Manchuria/China -
tonight.

There is a good deal of unplanned Russian work - due to feedback - and what it led me to. Additional land and naval units. Fixed naval units.

We may have eliminated duplicated leaders entirely (except where intended for supply sinks). Went through a report on them.

Minor tweeks to air units and aircraft - and a couple of increases in Allied replacement levels. The Ki-45 gained drop tanks in all marks.

PP changed in EOS and PPO - to reflect the generally larger size of divisions. The rationale remains as it was -

Japan initial: 3 divisions
Allied initial: 1 division
Japan daily: 1 division
Allied daily: 2 divisions

A division is approximately 1500 pp. [A really tiny division is less than 1000. And a USMC division is exactly 2000.]

"I will work for two days - then attempt to take the next two days to whip out Level 7." Thank you for the update, it is appreciated. Though with my schedule I was hoping a bit sooner.

A fairly air oriented update is uploaded.

This affects the pilot training table, the new EOS carriers for USN, the assignment of air groups for
RN carriers that were aviation transports, and changes to Japanese bombers.

The Australian Army had its brigades brought up to RHS standard as well.

Unless you NEVER need to transfer units between commands, do NOT use x.30.

Will figure it out and update at .31 level.

We will then check for eratta, and freeze the scenarios, so I can do Level 7.

ETA Level 7 One week.

Any changes not requested now won't get in.

RHS Level 6 files were uploaded at 6.31 level

A 6.32 aircraft file set was then issued.

The problem with pp is fixed

Some Soviet MS added - and a couple other things folded in.

5.32 set to upload plus 9 hours.

"We will then check for eratta, and freeze the scenarios, so I can do Level 7." Alright time to turn on the data microscopes and see what can lurking about. It is good to hear that level 7 is being worked on.

Level scenarios uploaded as a combined .31 and .32 package

databese error
jap DE Hashidate type has 5 durability
its 6/44 upgrade has 10 durability

This revises Allied pilot numbers (non US)
adds a shipyard to Vladivostok (repair)
and changes some EOS ships for USN/RN per request (well - the RN one is a gift).


Otherwise some eratta folded in.

Will be at least one more version with eratta - working on some things.

And 5 level uploads plus 10 hours.

5.33 file set uploaded

Sid,

In EOS 6.33 the port size for Salt lake City (main USA base) got set back to 0. This means that the damaged industry and resources there will possibly not repair (certainly not consistently). I checked the other places you had made that change before and they are still fine. With the large daily supply compliment at Salt Lake City I am not certain it will matter, just pointing it out in case it does.

thanks