Respawning of Carriers in RHS: Cured

[el cid again]

I found some of the things on your list were done. The duplicated ship was missing, for example. I have done those not found again - or for the first time - whichever applies.

On carrier respawn - I cannot tell if it is fixed? NO Allied carriers were lost in my test to find out!

So I also adopted a suggetion to move the six offending carriers - between that and moving Essex I am pretty sure it won't be an issue. Hopefully sooner or later someone will sink an Allied carrier - then we will know.

RHSCVO is a lot more historically correct - and Japan does not do nearly as well - as in RHSEOS - which was the point of EOS. But the lack of a clear edge - in this case I suspect the carrier recon planes (Kates with no bombs but more gas - called C3N1) - makes it less likely to sink Allied carriers - much less likely than one might expect. Apparently the Japanese - who went on to perfect the concept with the D4Y1-C and the C6N1 - should have mass produced the progenator - the C3N1.

[Nemo121]

Respawn definitely still happens.
 
In my testbed AI vs AI game Hornet was sunk on 21st May 42 and it looks like it showed up in the replacement queue due for arrival 480 days after being sunk. So, respawning is definitely in.
 
 
Interestingly in this game the Japanese are still stuck in Malaysia ( only took Kuala Lumpur on the 20th May 42 after a 6 month siege) and the Phillipines ( Bataan and Manilla). In addition they have been unable to take a single DEI supply sink...

[witpqs]

Okay - how did you fix the Soviet minelaying subs? I couldn't find how to make them work.

Nevermind - I found your message in the other thread.

[el cid again]

[quote]ORIGINAL: Nemo121

Respawn definitely still happens.

In my testbed AI vs AI game Hornet was sunk on 21st May 42 and it looks like it showed up in the replacement queue due for arrival 480 days after being sunk. So, respawning is definitely in.

I doubt it. I just uploaded 4.48 with the fixes in it. Since I could not confirm the first worked - I have not been able to sink a US carrier! -
I put in a second one. EITHER ONE should do the job. I am pretty confidend both must have done. I will keep running my 4.48 test until we know.

[el cid again]

ORIGINAL: Nemo121

Interestingly in this game the Japanese are still stuck in Malaysia ( only took Kuala Lumpur on the 20th May 42 after a 6 month siege) and the Phillipines ( Bataan and Manilla). In addition they have been unable to take a single DEI supply sink...

In my 4.48 test game - using CVO - which is dramatically weaker than EOS - Japan was able to take Batavia and Soerabaja pretty easily. It is on its way to attack the ones on Sumatra overland - having invaded from the South and is using the rail lines to go north - with supplies - never saw that before! Malaya has fallen - but Manila and Bataan still hold out. Manila is invested though - and so it will go first.

[el cid again]

ORIGINAL: witpqs

Okay - how did you fix the Soviet minelaying subs? I couldn't find how to make them work.

Nevermind - I found your message in the other thread.

The subs - and the Lenningrad class DLs - and one of the destroyer classes - all had nothing in the "turret" field. It is just like guns - if you have two mine racks - you need a "turret" value of 2 - to lay two at once. If you fail to do that, the code gets all messed up - as you saw - at reload time.

[Nemo121]

Well as of January 1943 the DEI in my game is still not fully cleared. The north and south are still holding out although Palembang, batavia etc have finally fallen,.
 
 
Interestingly the AI was dumb enough to leave FOUR British CVs and 2 BBs in Tjilitjap when it fell to ground assault and so all were scuttled [8|]

[Mike Scholl]

Interestingly the AI was dumb enough to leave FOUR British CVs and 2 BBs in Tjilitjap when it fell to ground assault and so all were scuttled


Proving once again that "AI" stands for "Animated Idiocy". Though to be fair, CID did say that the AI was hopeless at playing the Allies...

[Nemo121]

Aye, AI stupidity says little about RHS EOS itself... One thing I've been very gratified to see is poorly escorted Betty Daitai managing to slip a few planes through CV TF CAP and get hits on Allied CVs. Admittedly this is in mid-42 when Allied CAP isn't that great but in stock games these same strikes would return no kills.

There certainly do seem to be a lot more "leakers" in RHS and from stopping the game every 6 months and reviewing outcomes things look to be progressing along quite historical lines.

[el cid again]

ORIGINAL: Mike Scholl

Interestingly the AI was dumb enough to leave FOUR British CVs and 2 BBs in Tjilitjap when it fell to ground assault and so all were scuttled


Proving once again that "AI" stands for "Animated Idiocy". Though to be fair, CID did say that the AI was hopeless at playing the Allies...

Actually - Joe said that - and I just quote him regularly.

But I have repors AI is getting "smarter." And if so this is for cause: I have attempted to "program" it by changing data of various kinds. However, mostly my focus has been on improving Japanese AI for initial ops and for production: since it is my understanding many players like to do Allies vs AI as Japan - and that AI as Allies is not realistic. Still- I never miss a chance to help it if I can.

I just saw AI take Palembang in AI vs AI - by a very sensible method (approach by land, supply the assault force, which was a single division - 2nd - the historical one - this fully 9 months sooner and also in CVO which is not as strong as EOS).

But yes, AI is dumb as a post. In 1943, the Japanese economy is a lot stronger - because FINALLY it has expanded all its ports, airfields, fortifications - and it cannot waste supply points on that any more! It appears to me the switch "set all facilities to expand at start" is only for human players: AI ALWAYS does that.

[el cid again]

ORIGINAL: Nemo121

Aye, AI stupidity says little about RHS EOS itself... One thing I've been very gratified to see is poorly escorted Betty Daitai managing to slip a few planes through CV TF CAP and get hits on Allied CVs. Admittedly this is in mid-42 when Allied CAP isn't that great but in stock games these same strikes would return no kills.

There certainly do seem to be a lot more "leakers" in RHS and from stopping the game every 6 months and reviewing outcomes things look to be progressing along quite historical lines.

Works for both sides too: I have had B-17s out of Pearl on Dec 7 actually score on Japanese carriers - although the attacks are small - if the CAP is not strong it isn't easy for a Zero CAP to get all the B-17s. I even saw a B-18/23 Bolo score a hit once.

[Nemo121]

Nope, it surely doesn't. In my test-game. Now mid-43 the AI has not expanded a SINGLE engine factory... It is trying to build 75 Me-264s per month requiring 300 engines but is only building the December 7th 41 number of Mansyu engines. Dumb AS A POST! [:D]   Still, the air to air combat portion of RHS is holding up well into 1943. The Tojo is a real killer.... My top Sentai has over 300 kills gained in just 9 months flying the Me-109 and Tojo.

[el cid again]

ORIGINAL: Nemo121

Nope, it surely doesn't. In my test-game. Now mid-43 the AI has not expanded a SINGLE engine factory... It is trying to build 75 Me-264s per month requiring 300 engines but is only building the December 7th 41 number of Mansyu engines. Dumb AS A POST! [:D]   Still, the air to air combat portion of RHS is holding up well into 1943. The Tojo is a real killer.... My top Sentai has over 300 kills gained in just 9 months flying the Me-109 and Tojo.

Only ONE engine factory expands in WITP - the one in the center of Japan - NW of Tokyo - Gumma Prefecture. ONLY the engine type set up for that location expands if AI is boss - and ONLY IF it is needed.

[Nemo121]

Hmm, I should clarify... they haven't repaired damage either.... No expansion, no ( or at the very least imperceptible) repair of disabled factories.

[witpqs]

ORIGINAL: el cid again

I just saw AI take Palembang ...

Nice improvement. What was the approximate date (month/year is good enough).

[Nemo121]

My AI took it in September/October 42

[el cid again]

Enterprise and Lexington got sunk in June 1942 - and neither respawned.

I did two things:

moved Essex class to a different slot

moved all six early US CVs to different slots.

one - or both - of these things - works.

[el cid again]

ORIGINAL: witpqs

ORIGINAL: el cid again

I just saw AI take Palembang ...

Nice improvement. What was the approximate date (month/year is good enough).

May 42 - from the south - by rail. The division then moved on to attack the coal fields on the West coast - but had not yet reached the site (trail movement is slow).

[timtom]

ORIGINAL: el cid again

Enterprise and Lexington got sunk in June 1942 - and neither respawned.

I did two things:

moved Essex class to a different slot

moved all six early US CVs to different slots.

one - or both - of these things - works.

Ran a quick test that seems to confirm these findings. It seems to be enough to leave the class slot empty. Works for the cruisers too.

Great news, as far as I'm concerned.

[Terminus]

Glad to hear the bit about the cruisers; that would cure the "US-Army-Cruiser" bug...