Deck Guns Kills Not Registering

[ShaggyMurphy]

So my campaign is in late 1943 and I just upgraded from the Gato class to the Balao class submarine, and suddenly my deck gun kills aren't counting. Torpedo kills are working just fine, no bad weather at all to steal my kills. The only thing unusual is that usually I have to edit my save game file when upgrading the submarine to restore the crew slots, because of the glitch from replacing the aft deck gun with a bow mounted deck gun. I didn't have to do that this time because the Balao class came with a bow deck gun already. I'm running a stock 1.5 version of the game, no mods. Any ideas on how to fix it? Thanks!

[Aktungbby]

ShaggyMurphy! Missed yer 1st post in 2017!

[propbeanie]

Hey, ShaggyMurphy! My only question about the "kills" being registered, is since you are using the deck gun, are you waiting until the ship "sink-sinks" before motoring off? What I mean is, when you torpedo a ship, it sinks relatively fast, and gets to its "crush" depth and is registered sooner than if you use a 3" or 4" deck gun, where it might take a while for the ship to reach the same "crush" depth and register for you. If you leave the area too soon, then the ship respawns, and you never sank it.

As to the Stock game and losing the deck gun and / or crew positions, are you doing the "fix" the Coletrains way? or the wolfeinsamer way? I was looking for a link to the two threads, but haven't located them yet. Try this posting in the FotRSU thread though:

https://www.subsim.com/radioroom/sho...64#post2701664

Be aware though, that we have four gunner positions in FotRSU, and not the two of Stock, so govern yourself accordingly. I'll search for the old posts for the two ways to do it...

Hah! found one already:
https://www.subsim.com/radioroom/sho...43#post2358643

... and I had forgotten that the other was "buried" in a thread as a reply to someone else:
https://www.subsim.com/radioroom/sho...652#post639652

[KaleunMarco]

Originally Posted by ShaggyMurphy

So my campaign is in late 1943 and I just upgraded from the Gato class to the Balao class submarine, and suddenly my deck gun kills aren't counting. Torpedo kills are working just fine, no bad weather at all to steal my kills. The only thing unusual is that usually I have to edit my save game file when upgrading the submarine to restore the crew slots, because of the glitch from replacing the aft deck gun with a bow mounted deck gun. I didn't have to do that this time because the Balao class came with a bow deck gun already. I'm running a stock 1.5 version of the game, no mods. Any ideas on how to fix it? Thanks!

i've experienced the same thing in the past although i cannot remember which mod-set i was playing and i could not determine the root cause.

my apologies....i can only commiserate with you.

[propbeanie]

That's just it KaleunMarco, it strikes Stock just as much as TMO, as much as RFB, etc. It is a Silent Hunter: Wolves of the Pacific issue that has been around since day 1, unfortunately... it is worse in some versions of the game, better in others, but that might just be my imagination, and reminiscing about v1.4 - where a transfer was a transfer, not a teleportation with the same mission assignment...

For fighting the symptoms, a Save every time before entering the spawning range of Home Port, or roughly 50nm out, will help with a possible recovery. The best thing to attempt to avoid the issue is to not shell-out to Windows, accidentally or otherwise, which is next to impossible with the way Win10 / 11 interrupts the OS user with advertisements, or "notifications" in the systray, rather often. Moving a deck gun from fore to aft or vice versa can also complicate the issue, but I don't think the problem has ever been "fixed" by anyone, least of all Ubisoft or their associates, but not for lack of trying by just about every modder out there...

[KaleunMarco]

Originally Posted by propbeanie

That's just it KaleunMarco, it strikes Stock just as much as TMO, as much as RFB, etc. It is a Silent Hunter: Wolves of the Pacific issue that has been around since day 1, unfortunately... it is worse in some versions of the game, better in others, but that might just be my imagination, and reminiscing about v1.4 - where a transfer was a transfer, not a teleportation with the same mission assignment...

For fighting the symptoms, a Save every time before entering the spawning range of Home Port, or roughly 50nm out, will help with a possible recovery. The best thing to attempt to avoid the issue is to not shell-out to Windows, accidentally or otherwise, which is next to impossible with the way Win10 / 11 interrupts the OS user with advertisements, or "notifications" in the systray, rather often. Moving a deck gun from fore to aft or vice versa can also complicate the issue, but I don't think the problem has ever been "fixed" by anyone, least of all Ubisoft or their associates, but not for lack of trying by just about every modder out there...

Hey, PB, i was not assigning blame in my post....i was commiserating with the post-er.

[propbeanie]

Well, we can blame Ubisoft - again...