PDA

View Full Version : Togo's Civil War


Bullethead
23 Aug 06, 17:55
It's 0607 on 12 Feb 04. The rising sun reveals Novik is about to run head-on into Chitose's division of 4 mean PCs at 3500 yards. Fortunately, the IJN seemed confused so Novik escaped with survivable damage. The strange thing was that when she escaped and the battle ended, the AAR screen said that there had been 18 IJN ships on the map (only saw the 4 PCs) and here's the kicker: 8 of them were damaged!

This was strange, because I didn't remember leaving any cripples except for a few scattered auxCs I didn't want to waste ammo on. So I thought maybe Togo'd been caught in a storm and had a bunch of ailing DDs. Oh well. But then, at 0738, in the broad daylight of early morning, Novik again met the IJN. This time, the predicament of the IJN was evident from long range, and explained where the 8 damaged ships in the 1st battle came from.

As you can see in the 1st attachment, Togo's fleet began this 2nd battle with all BBs except Mikasa and Asahi started out paired up with an AC in the actual act of collision. So I slowed Novik, which was way safe at a distance, to "enjoy" the show. As time went by, the paired ships collided over and over again, gradually pushing out of each other's way. The unpaired BBs, meanwhile, hove to and waited on their buddies to settle their arguments.

Just when the BB/AC head-butting contest was getting over and the ships starting to sort themselves out, Chin Yen's division came storming in and reduced everything to total chaos again. See 2nd attachment. Amazingly, there were no more collisions, but everything was a total mess. Eventually, however, the IJN sorted themselves out and Togo's boys limped on after Novik while Chin Yen et al ran off in the opposite direction.

As you can see, Tokiwa and Asama took some bad propulsion damage, with speeds limited to 5 and 2 knots, respectively. The rest of Togo's lads seem unable to top 15 knots, maybe not even that.

Damn, that pretty much took the fun out of this campaign :(.

SunScream
24 Aug 06, 13:44
That pic has to be worth a caption competition.

"Who hoisted the dosie-doe manoeuvre signal?"

Daedalus
25 Aug 06, 06:54
It's 0607 on 12 Feb 04. The rising sun reveals Novik is about to run head-on into Chitose's division of 4 mean PCs at 3500 yards. Fortunately, the IJN seemed confused so Novik escaped with survivable damage. The strange thing was that when she escaped and the battle ended, the AAR screen said that there had been 18 IJN ships on the map (only saw the 4 PCs) and here's the kicker: 8 of them were damaged!

This was strange, because I didn't remember leaving any cripples except for a few scattered auxCs I didn't want to waste ammo on. So I thought maybe Togo'd been caught in a storm and had a bunch of ailing DDs. Oh well. But then, at 0738, in the broad daylight of early morning, Novik again met the IJN. This time, the predicament of the IJN was evident from long range, and explained where the 8 damaged ships in the 1st battle came from.

As you can see in the 1st attachment, Togo's fleet began this 2nd battle with all BBs except Mikasa and Asahi started out paired up with an AC in the actual act of collision. So I slowed Novik, which was way safe at a distance, to "enjoy" the show. As time went by, the paired ships collided over and over again, gradually pushing out of each other's way. The unpaired BBs, meanwhile, hove to and waited on their buddies to settle their arguments.

Just when the BB/AC head-butting contest was getting over and the ships starting to sort themselves out, Chin Yen's division came storming in and reduced everything to total chaos again. See 2nd attachment. Amazingly, there were no more collisions, but everything was a total mess. Eventually, however, the IJN sorted themselves out and Togo's boys limped on after Novik while Chin Yen et al ran off in the opposite direction.

As you can see, Tokiwa and Asama took some bad propulsion damage, with speeds limited to 5 and 2 knots, respectively. The rest of Togo's lads seem unable to top 15 knots, maybe not even that.

Damn, that pretty much took the fun out of this campaign :(.


I learned the hard way also. And after reading the manual I found that when Norm said to sort them out a little your self, but that does not work for the AI.
On the ships that came up on the file that you did not see , I had that happen to me, but in the next battle I saw why, there where a group of ships that where just out of range of site, and they came into the battle after I attacked the other ships. But that does not account for the damage to them when you did not see the ships.
I wonder if that has something to do with the upgrade and not starting another Campain? I know one thing I have been running smooth sense the last upgrade and have not seen any problems so far. Also if you are close to an Island or land or one of those Islets that are out in the bays the ships will react to them , Was the fleet that went on the dance floor close to one of them. And they do not have to be real close for them to start moving and when one does it makes for quite a show! :crosseye:
I have been playing all night so I'll check when I get up in a few hours to see what you posted. I have been writing down in a log of things like this and this way I can keep up and see patterns if they arise.

mllaneza
25 Aug 06, 12:04
You should have saved in the middle of that, the devs would love to see what trouble the AI can get itself into.

Daedalus
25 Aug 06, 12:35
You should have saved in the middle of that, the devs would love to see what trouble the AI can get itself into.

It was nothing abnormal, I had turned the ships and had them moving around setting them up. and then I had to make a move I did not plan on. That is what caused it. And when you get them all going all over you need to get some of them at least on the right track before you do anything else or let them reform automaticly. It stats that in the manual to do this as it will work faster than letting the AI sort it out. It does but it is easier if you help get the main group sorted first.

Bullethead
25 Aug 06, 19:05
This was a problem in 1.014 but seems to have been fixed in 1.015 (thanks to being reported by many folks). But don't let that stop you from entering the caption contest :).