|
|
Post by BathTubAdmiral on Jul 25, 2019 16:31:48 GMT -6
All nations, all times, all shiptypes, etc.
Issue____________________:
Ships lose contact to their div, and all other ships, and wander off with questionable heading. Contact can only reestablished after hours, if at all - even if their div or the flagship is right alongside. The ship can't even switched to manual control (Rear Admiral), as if it was miles away. (see screenshot below)
Sometimes, they reattach to their division hours later, either after steaming right alongside with the other ships of the div, sometime after traversing a good part of the map, and then turning around.
This happens mostly with nightfall (limited no. of observations, though).
Examples_______________:
A) I have seen the 3rd ship in a 4-ship div ("line ahead", really close formation, all ships undamaged) lose contact, veer off and proceed to rush an enemy ship.
It placed itself right between the enemy ship and the other ships, which fired at each other, so visibility must have been at least 2x the range from the defector to the div?!
B) DD Espero first loses contact with her div at 12:51, without any cause. Reattaches >1 hour later, all the while sailing right next to her div?!
She loses contact again at 17:18, after her conning tower is hit. After that, the DD Espero heads of towards the north african coast and refuses any attempt to control her. Flagship is within 500y?!
Note - she is not headed for port at that moment. But on loading the savegame, the destination/heading is changed to what might be the nearest port. DD Borea loses contact with division at 17:34, without taking any damage, and wanders of into a seemingly random direction ... .
Attachments:Game1.7z (131.54 KB)
|
|
|
|
Post by rimbecano on Jul 25, 2019 16:56:33 GMT -6
This isn't a bug. At night, without radar or radio, with ships darkened to avoid being seen by the enemy, ships could end up getting lost and not reestablishing contact with their divisions for hours.
It is something that is a bit difficult to convincingly model in a game, though, and often does look awkward when it happens.
|
|
|
|
Post by BathTubAdmiral on Jul 25, 2019 19:12:46 GMT -6
Forum ate the longer response - I'll make it short: Bullshit Stop jumping in to defend the game, there's no need. Only distracts from bugfixing. 12:51 is not "at night". Function to simulate ship2ship com is bugged. Behaviour of ships losing contact is bugged as well.
If the developer thinks the behaviour is fine, then he can surely leave a note. Then we can talk "game design", instead of "code bugs".
|
|
|
|
Post by williammiller on Jul 26, 2019 8:36:40 GMT -6
Forum ate the longer response - I'll make it short: Bullshit Stop jumping in to defend the game, there's no need. Only distracts from bugfixing. 12:51 is not "at night". Function to simulate ship2ship com is bugged. Behaviour of ships losing contact is bugged as well.
If the developer thinks the behaviour is fine, then he can surely leave a note. Then we can talk "game design", instead of "code bugs".
|
|
|
|
Post by BathTubAdmiral on Jul 27, 2019 7:47:10 GMT -6
|
|
|
|
Post by BathTubAdmiral on Aug 3, 2019 2:56:36 GMT -6
|
|
|
|
Post by williammiller on Aug 3, 2019 9:32:59 GMT -6
"Weather: Heavy Rain" = Very poor visibility is going to make losing contact much more likely. Also, what year was this, as comms are limited to flags/signal lights before radio was prevalent.
|
|
|
|
Post by aeson on Aug 3, 2019 19:55:14 GMT -6
"Weather: Heavy Rain" = Very poor visibility is going to make losing contact much more likely. Also, what year was this, as comms are limited to flags/signal lights before radio was prevalent. Says 1905 in the date at the bottom of the screenshot. |
|
|
|
Post by williammiller on Aug 3, 2019 22:04:27 GMT -6
"Weather: Heavy Rain" = Very poor visibility is going to make losing contact much more likely. Also, what year was this, as comms are limited to flags/signal lights before radio was prevalent. Says 1905 in the date at the bottom of the screenshot. Oh, wow...I need to get my eyes checked...again...lol. Thanks. |
|
|
|
Post by BathTubAdmiral on Sept 13, 2019 8:59:21 GMT -6
In 1.07, ships are still doing things: - lose contact while being the 2nd ship in a line of 3 (distance: 400y visibility: 8000y) - move through the whole fleet (several CAs, CLs, DDs around that BB line), totally blind to all the friendly ships steaming and firing around them - speed off in a (seemingly) random direction, totally ignoring all friendly ships, and the threat of enemy DDs (while still firing at spotted enemy ships?!) - (sometimes) move several miles out of sight, then turn around and "magically" find back to their division that has moved on - (more often) get torpedoed, speed off in another random direction, get progressive flooding from high speed and - sink ...
... and I have seen nothing in the patch note that this shouldnt happen in 1.08 ... |
|
|
|
Post by BathTubAdmiral on Nov 15, 2019 4:03:12 GMT -6
In 1.11, ships are still doing this.
To me the No.1 on the list of annoying bugs, that nearly made (and someday might make me) discard the game ...
|
|
|
|
Post by williammiller on Nov 15, 2019 18:30:37 GMT -6
BathTubAdmiral Do you have a save game you can post that shows this behavior?...that would help us track it down as we are not seeing this on our end.
|
|
|
|
Post by BathTubAdmiral on Nov 15, 2019 18:44:17 GMT -6
Doesn't the save from post #1 work?
I'll try to get one or more if it happens again in my current game.
Although ship behaviour changes sometimes on reload, as I described for one of the examples above...
|
|
|
|
Post by BathTubAdmiral on Nov 15, 2019 20:49:32 GMT -6
Here's another case: DD S14 loses contact at 16:38 (17:38 locally; shortly after nightfall, visibity=4000y) while within 300y of the squadron members and 1500y of the squadron leader, and proceeds on a seemingly random course. Neither S14 nor squadron leader are damaged.
See saves in the next post: Game1 1908-10 Cr Raid 17:24 autosave Game1 1908-10 Cr Raid 17:41 DDcontactlost
|
|
|
|
Post by BathTubAdmiral on Nov 15, 2019 20:50:19 GMT -6
|
|
