Slitherine

quote:

ORIGINAL: DonH58

Hi El Cid
Is there going to be another update of CVO 7 or just the pwhex. Want to start a new game with my boy but thought I would check first. Thanks and I really appreciate all the hard work you and the RHS team have done!!!

quote:

ORIGINAL: el cid again

Well - pelecan is right - at least. It is a wierd vessel - and it has an "air group" of one aircraft!!! It is a former minesweeper - and most of her sisters are still minesweepers.

WITP was horribly dirty. Much of the dirt carried over into CHS and RHS. And no doubt we added erratta as well. Information theory says there must be - MUST BE - errors - in files of this size. We will NEVER get it perfect - ever. But it is very clean - relatively speaking. Yet if I go looking I can find an eratta in some sense every few minutes - if you include things I would do differently. Many fields I have NEVER seen - there are - what - I forget - 230 000 fields? Bunches and bunches.

VCT 17 is 9999ed out in CVO - so if you have it - you do not have current files. It is part of the air group of USS Reprisal - CVL - 58 - in EOS family only - and it is fictional. [The ship is a CL in CVO and BBO families]

Yes the CVO VCT-17 is 9999ed out but it is not CAIO 7.7881. It shows as "0" which I have now corrected.

Hmmm - USN 5 VCS-14 IS the USS Pelecan air group - and it has only one plane - as it should. I am confused about why you are confused?
There is no instance in which it appears as a base air group - or with 4 aircraft - although that would be a legitimate option. All scenarios have it as a 1 aircraft group for Pelican. If this isn't what you see - down load current files again.

Yes I do see the USN 5 VCS-14. I am saying that in AIO & BBO (but not in CVO) there is a "USN 4" VCS-14 at the San Francisco base, with 4 A/C.

quote:

ORIGINAL: Buck Beach

quote:

ORIGINAL: el cid again


Yes I do see the USN 5 VCS-14. I am saying that in AIO & BBO (but not in CVO) there is a "USN 4" VCS-14 at the San Francisco base, with 4 A/C.

This is correct. BBO, RPO and PPO SHOULD appear at San Francisco - instead of USS Vicksburgh - in other scenarios. There were numerous shore detachments - many not in the game - so this isn't a problem.

(in reply to Buck Beach)

quote:

ORIGINAL: Buck Beach

quote:

ORIGINAL: el cid again

Note: It appears that the AIO or EOS file was updated to create the CAIO OOB as, both of these have the VCT-17 with a zero delay and being loaded on the CVL-58 to show up later. The same as the CAIO 7.7881 I used. Please confirm for me that the wpa, wbc, wpd, wph, wpp files in CVO OOB are to be consistant througout the CVO family.

CAIO is almost entirely the same as CVO - very little different.

(in reply to Buck Beach)

quote:

ORIGINAL: el cid again

quote:

ORIGINAL: DonH58

Hi El Cid
Is there going to be another update of CVO 7 or just the pwhex. Want to start a new game with my boy but thought I would check first. Thanks and I really appreciate all the hard work you and the RHS team have done!!!

It is not my desire to update either.

If I do update either, the changes will be minor.

If we update pwhex - it backfits into existing games anyway. So it is more likely. Looks like we may change communications coding in a way that impacts supply movement mainly.

I have spotted one erattum in all Level 7 files (a tank company wants to grow into a regiment) - but it can be controlled by turning replacements off most of the time. However, I had an idea that might prevent certain locations from expanding factories automatically to rediculous values - and if it works, we might issue an update. Probably Christmas Day.

quote:

ORIGINAL: el cid again

I can move it. What is your version number?

quote:

ORIGINAL: witpqs

m10bob,

I have seen various weirdness with TF's.

1) Mostly it's with transport TF's that have a destination set in mid-ocean then a home port different from where they left (a work-around way point). Sometimes they stop at the destination and sit there until given a shove as you say. Note that this never has happened with an empty TF, only those with cargo on board. Go figure. Happened with stock, CHS, and RHS.

2) Very rarely I see a TF (any kind of TF) change it's destination, or it's home, or even teleport to a new (and usually dangerous) location. Thank goodness very rarely. Happened with stock, CHS, and RHS.

3) The only time I see a TF get really stuck (the way you describe with KB) is that a mine-laying TF fleeing Singapore will get stuck in hex near Palembang, with the '9999' range thing. This is the only one that I have seen only in RHS. Sid looked over the Pwhex and it seems okay for the hex. I have no idea what gives.

I have seen other strange behavior that goes away when the program is closed down and then started again, so I know there's bugs in them there hills.

quote:

ORIGINAL: m10bob

Upgrading RHS over the past year has been a lot of fun and given us a chance to push the envelope in different areas. We have (collectively) been able to sometimes bump that envelope.
Soon after upgrading to the most recent RHSCVO ver 7, I noticed something strange which I cannot guarantee related to the change in Pwhex file, but it did happen at the same time.
Several of my allied convoys stopped in mid ocean, in no areas affected by the new Pwhex file.
Each of these TF's retained their orders, (they still remembered their destination, home port, etc. Nonetheless, I had to manually give them each a shove,(as I found them) to get them going again.
Some were transport convoys but warships were affected as well.
Unfortunately, it affected both sides because the "death star" with a few Japanese CV's is also locked up in a single hex, and for at least 14 game days has been in the hex between the Celebes and Borneo, the hex on Cobra's map with the label "Palu"(sp?).

My internet carrier is AOhell, and every half hour or so I get that blasted "virus protection upgrade" message which interrupts the game. It is possible that may have thrown the monkey wrench into the works. I don't know, but in the past year, I have never had this problem before.
My Pwhex file is not corrupted, I have re-downloaded it 3 times and have the same results.
(I remember in past game trials getting ships stuck when we first began experimenting with those convoy "snaketrails" so I know the present problems are similar, but these ships stopped in mid ocean,(for the most part), with no reason to stop.

I am still having VERY serious problems with SBD 3/4 production which in the editor is marked for 11 monthly. This may be hard-coded. This has forced me to have 5 American flat-tops sitting around waiting for new SBD's, or sending them out with a complement of maybe 47/72 possible planes.
Yeah, I understand we have to wait for planes to be built, but with the PTO getting most of them, I KNOW the U.S. turned out more than one plane every 2 days.
This is just plain wrong.

Exchanging them for the Vultee is wrong (historically)..Besides, I don't know how I might do this.(Help?)

quote:

ORIGINAL: m10bob

quote:

ORIGINAL: witpqs

m10bob,

I have seen various weirdness with TF's.

1) Mostly it's with transport TF's that have a destination set in mid-ocean then a home port different from where they left (a work-around way point). Sometimes they stop at the destination and sit there until given a shove as you say. Note that this never has happened with an empty TF, only those with cargo on board. Go figure. Happened with stock, CHS, and RHS.

2) Very rarely I see a TF (any kind of TF) change it's destination, or it's home, or even teleport to a new (and usually dangerous) location. Thank goodness very rarely. Happened with stock, CHS, and RHS.

3) The only time I see a TF get really stuck (the way you describe with KB) is that a mine-laying TF fleeing Singapore will get stuck in hex near Palembang, with the '9999' range thing. This is the only one that I have seen only in RHS. Sid looked over the Pwhex and it seems okay for the hex. I have no idea what gives.

I have seen other strange behavior that goes away when the program is closed down and then started again, so I know there's bugs in them there hills.

Thank you Witpqs......BTW, you are correct in assuming I use artificial waypoints, and for some of them that may be the answer, but not more than half..
Again, it might be that whole AOhell thing too, it messes up the game and I have to hit the button at the bottom to start the game graphics all over again ..
Still would appreciate if someone might tell me how I can use those Vultees in lieu of the "missing"() SBD's..

quote:

ORIGINAL: mlees

I am playing CVO version 5, and I too see the (AI Japan) full KB death star "stuck" in a (shallow) sea hex 1 hex SE of Balikpapan. I can't sink it with LBA due to the Uber-CAP. It's been there for about a week now, while I regather more LBA to throw at it.

I may have to kick it loose under head-2-head mode, just to be fair. (I bet it's out of gas by now. Maybe getting low on sorties by now.)

By the way, three Illustrious class CV's teamed up with the Hermes are no match for the PH veterans. (I did score two torp hits on Shokaku though. )

quote:

ORIGINAL: el cid again

What was their destination? AI may have said "go there" - they did - and until it says "go somewhere else" - they are just obeying orders (so to speak). A HUMAN may say "go there" and mean it - for some reason. AI might do so for less reason - but it may have something in mind we don't understand. Maybe it is waiting for something don't know it is going to be coordinating with?

quote:

ORIGINAL: el cid again

quote:

ORIGINAL: m10bob

quote:

ORIGINAL: witpqs

m10bob,

I have seen various weirdness with TF's.

1) Mostly it's with transport TF's that have a destination set in mid-ocean then a home port different from where they left (a work-around way point). Sometimes they stop at the destination and sit there until given a shove as you say. Note that this never has happened with an empty TF, only those with cargo on board. Go figure. Happened with stock, CHS, and RHS.

2) Very rarely I see a TF (any kind of TF) change it's destination, or it's home, or even teleport to a new (and usually dangerous) location. Thank goodness very rarely. Happened with stock, CHS, and RHS.

3) The only time I see a TF get really stuck (the way you describe with KB) is that a mine-laying TF fleeing Singapore will get stuck in hex near Palembang, with the '9999' range thing. This is the only one that I have seen only in RHS. Sid looked over the Pwhex and it seems okay for the hex. I have no idea what gives.

I have seen other strange behavior that goes away when the program is closed down and then started again, so I know there's bugs in them there hills.

Thank you Witpqs......BTW, you are correct in assuming I use artificial waypoints, and for some of them that may be the answer, but not more than half..
Again, it might be that whole AOhell thing too, it messes up the game and I have to hit the button at the bottom to start the game graphics all over again ..
Still would appreciate if someone might tell me how I can use those Vultees in lieu of the "missing"() SBD's..

Go to the unit. Click on the upgrade type. Select ANY type with enough planes. Make sure allow upgrades is set.
Go back to the unit screen and hit upgrade now. Except for a carrier unit - either it must be ashore - or it must be in a suitable port.

quote:

ORIGINAL: Mistmatz

In stock the US Army pilot pool experience from '41 to '46 evolves like this: 55-55-60-65-70-70.

In CVO they start with experience level 40 in '41. Does the experience develop like in stock from that number (+0,+5,+,5,+5,+0) or is there a different algorithm? If so where can I get the data, seems I lack the skill or the possibility to extract it from the scenario editor.

quote:

ORIGINAL: m10bob

quote:

ORIGINAL: el cid again

What was their destination? AI may have said "go there" - they did - and until it says "go somewhere else" - they are just obeying orders (so to speak). A HUMAN may say "go there" and mean it - for some reason. AI might do so for less reason - but it may have something in mind we don't understand. Maybe it is waiting for something don't know it is going to be coordinating with?

There was no commonality to the orders/destinations of the affected convoys. Some were from Aden, others from Frisco. Not all convoys were affected and none were out of fuel.

REPLY: Confusing - I thought you said KB was stuck. Now we have convoys to Aden and SF.

I suspect that blasted AOhell virus update program interrupting power from the game every half hour may have something to do with, but of course, am not sure, not geek enough.
I had a logjam in the snaketrail coming out of Aden, right at an elbow, but got them all on their way manually.
Affected units were all over the map, all areas of the game, so I suspect this is also what messed up the "deathstar" as well..?

quote:

ORIGINAL: m10bob

quote:

ORIGINAL: el cid again

quote:

ORIGINAL: m10bob

quote:

ORIGINAL: witpqs

m10bob,

I have seen various weirdness with TF's.

1) Mostly it's with transport TF's that have a destination set in mid-ocean then a home port different from where they left (a work-around way point). Sometimes they stop at the destination and sit there until given a shove as you say. Note that this never has happened with an empty TF, only those with cargo on board. Go figure. Happened with stock, CHS, and RHS.

2) Very rarely I see a TF (any kind of TF) change it's destination, or it's home, or even teleport to a new (and usually dangerous) location. Thank goodness very rarely. Happened with stock, CHS, and RHS.

3) The only time I see a TF get really stuck (the way you describe with KB) is that a mine-laying TF fleeing Singapore will get stuck in hex near Palembang, with the '9999' range thing. This is the only one that I have seen only in RHS. Sid looked over the Pwhex and it seems okay for the hex. I have no idea what gives.

I have seen other strange behavior that goes away when the program is closed down and then started again, so I know there's bugs in them there hills.

Thank you Witpqs......BTW, you are correct in assuming I use artificial waypoints, and for some of them that may be the answer, but not more than half..
Again, it might be that whole AOhell thing too, it messes up the game and I have to hit the button at the bottom to start the game graphics all over again ..
Still would appreciate if someone might tell me how I can use those Vultees in lieu of the "missing"() SBD's..

Go to the unit. Click on the upgrade type. Select ANY type with enough planes. Make sure allow upgrades is set.
Go back to the unit screen and hit upgrade now. Except for a carrier unit - either it must be ashore - or it must be in a suitable port.

I followed these directions to a t, and they do not work. Is there a step that is missing? Thank you