|
Post by johnthegamer on Jun 25, 2019 2:47:26 GMT -6
When did you start the game - 1900 What nation were you playing? - Germany Were there any start options that were not the default? - Ahistorical tech, Largest fleetsize, AI advantage, Custom legacy fleet. I also manually doubled the game budget of all nations in the BNat1900 file to increase fleetsizes even further (I like big battles). Describe the issue in detail. - The moment a detached ship returns to port, all my AI controlled divisions make an immediate B-line for port as well, leaving my BB's on their own. The AI divisions will not stop until you allow them into port, circling around the port eternally if you refuse. What were you doing when the bug occurred? - I was defending against a night-time fleet raid on coastal shipping in the Helgoland Bight by the vile Frenchies. One of my CA's was hit by a torpedo and had its A & B turret exploded, so I returned it to port at Helgoland. The moment it entered port and left the map, ALL my DD's, CA's and CL's dropped everything they were doing and ran straight for the nearest port. The battle took place in 1927. What did you expect to happen and how was the result you saw different than you expected. - I expected the CA to go into the port and for the rest of my fleet to continue fighting the battle. Can you describe how to reproduce the bug? - Send a single ship back to port during a battle and see what the AI divisions do after that, I suppose. What version of the game were you playing (v1.00, v1.01, etc)? - 1.04
|
|
|
Post by sloanjh on Jun 26, 2019 0:26:37 GMT -6
I just hit the same issue - here's a screenshot after a torpedoes B entered port at Nice. Also attaching zip of save of screen shot. When I restarted, all the AI divisions were independent. I was able to reset them to screen, support etc to get them to follow the flagship, EXCEPT a BB and CA division which I set to core kept going (possibly because it was night and they couldn't see the flag). I was able to use a screen command for the CA and core off a DD division in visual range of the BB to get them to change course. So I can confirm that at least all commands got wiped when my ship entered port. Didn't check if they ignored me before the save though, and they seem to be mostly responsive after the save. Attachments:Game3b.7z (153.09 KB)
|
|
|
Post by gornik on Jun 26, 2019 2:22:30 GMT -6
I saw this bug too in all versions and in RTW1 as well. Though it is hard to reproduce, as sometimes ship returns to port without it, and sometimes all fleet gone mad. Maybe, the role of division ship detached from is important as well, as bug in fact make all divisions independent and clear their lead division. After restoring sub-ordination manually, divisions often return to their duties.
|
|
|
Post by alsadius on Jun 26, 2019 7:57:47 GMT -6
How do you get the national flags on your ships like that?
|
|
|
Post by JagdFlanker on Jun 26, 2019 16:01:25 GMT -6
How do you get the national flags on your ships like that? preferences/sound and video/display options
|
|
|
Post by sloanjh on Aug 5, 2019 22:29:21 GMT -6
Just hit this bug again in 1.07... twice. I had a damage BC that I detached; when it went into port all divisions went independent and headed for port. As before, they ignored "core" commands, but responded to screen. The attached zip is from just after the first occurrence. This behavior (ignoring core and heading for port) survived a save/restore, so I suspect some sort of "Return To Base" flag (maybe the one that's supposed to be set when you detach a ship for damage) is being set by the bug. Hmmmm - that would also explain why all orders clear - if the code is looping through all divisions and setting them to "detached", that would clear all their orders. I just about had everything under control when it happened again (one of the DDs that was ignoring me, I think). The screen shot is from that. So if you run the game until the detached destroyer (with no damage) enters port you should be able to generate the bug. Note that both times this has happened to me it's been night. Also, the detached BC that started the cascade was not the division flag at the time and I'm almost positive it never was. Version was 1.07 (started at 1.05b). In addition, I hacked the save file to have aircraft experience all positive, and no experience greater than 39. Options were Very Large, Initial Build, Admiral. Playing France, 1900 start. Attachments:Game4i.7z (271.53 KB)
|
|
|
Post by sloanjh on Aug 5, 2019 22:38:26 GMT -6
More info: The BC that started the cascade is still showing up in the OOB, even though it's in port! Save file attached from screenshot. [EDIT] Apparently DD Dehorter magically teleported to Lat/Long 0/0. That might be the second ship that entered port to trigger the problems. It's now daylight, and my main BC flagship is in visual range of my main division. With Screen or Scout it follows the main division, but Core turns it for home. So there's some sort of flag set.... [EDIT2] One more data point: In the after-action results, Dunkerque is showing up twice in the statistics table. I don't see any other ships that are doing so. Attachments:Game4f.7z (317.62 KB)
|
|
|
Post by thesovietonion on Aug 8, 2019 13:31:49 GMT -6
I am having a similar issue, however the cascade starts should any ship receive the "would you like X division to enter port?" prompt. Regardless of what I select, not only are my support forces orders removed (Making them AI controlled independent units, erasing any support/scout/core formation orders) but they also hang around port, causing more and more of these prompts to fire.
|
|