ORIGINAL: Don Bowen
ORIGINAL: Grognerd
Playing scenario 2 Japanses AI - unpatched. Watched for several weeks ships appearing to be going in and out of Baker Is. Always heading NW. Kept getting intel about attack at Canton (from around march to April 42).
Finally changed sides to see what was going on as I knew some CV's were there. Several TF including a bombard group (the lead) CV group and AK invasion group) were set to move to Canton but appeared stuck in the NE hex above Baker Island. Judging from the fuel they were stuck there about a month. I did not want to change sides to spoil the suprise but eventually knew something was amiss.
Is this related to a fix in the patch? Or something else.
I patched the game, Played both sides and reset the stuck Japanese fleets (went back to early April as far as I could go) to go to truk for re-fueling and such. Now it's May 18 '42 and the fleet just re-appeared stuck in the same place (one hex N-E of Baker Is.) Now I change side to redirect the fleets around the "bad hex" and the game won't let me select any of the fleets as Japanese player! Now I can't re-direct them. Three fleet carriers are in the stuck along with several major ampib units. Went back to April 27th as far back as I can and still can't select! Any body out there have any ideas? or which save games should/could I post?
Post a current save in the tech support forum.
OK, there is actually no (current) bug here. If you look in your Japanese operations report you will see "
TF 304 slows down to allow following TF 20 to catch up". TF 20 is at Guam, loading. It actually should complete loading but does not due to a disrelated bug, now solved.
TF 304 is oscillating 9 hexes away from it's destination (Canton Island). This is because the slow following TF 20 has forced TF 304 to slow down to 1 hex per phase
and the need for a bombardment TF to stand off 12-hours max speed steaming from the target until night. It moves one hex toward Canton each night, one hex back each day. That will continue until TF 20 catches up. And all the other following TFs are linked to TF 304 in lock step.
Cancel load on TF 20 and wait for it to catch up.