TWoS Backwards Destroyers?

[Rwearjr]

Hello Fellow Kaleuns,

I am currently in the Arctic campaign, and after returning to the patrol area around Bear island post Narvik refit, I am experiencing an unusual bug.
I have now attempted to attack two separate convoys, and experienced the same problem.
When I attack a convoy, the escorts (some of them) begin running in reverse, sometimes moving many kilometers away from the search area. The convoy itself does not "move off" to the opposite side post attack, but only sits there, and once the post attack search phase is complete, the convoy does not resume course, but only sits there. This causes my "save" to be corrupted, initiating CTD, no matter how long post attack, or how far away I go after the convoy attack.
I will post my mod-soup list, but must mention that this same mod soup has been running on my machine with no issues for over a year. Corrupted save somewhere perhaps? Open to ideas from the smart folks in this community.

I run TWoS 2.2.23 with Real Navigation on a Dell G3 with NVidia 1660 Ti GPU

Only additional mods on top of TWoS are :
Dark Interior V1
Stormys DBSM 1.3

I recently added/ Changed to SH3 GUI, and used Vecko's Glass covered dials.
I have since changed back, but cannot imagine any way these could be causing this behavior.

Fingers crossed someone here has experienced this, and has an answer to where my issue is coming from. Truly dont wanna lose my campaign, or spend 4 hours wiping everything, and reinstalling the works (which I just did a couple of months ago) One thing of note, I used to NEVER go beyond 128 TC, but have read several posts here from fellow Kaleuns (including Vecko) that 256 TC is ok in newer TWoS iterations. Could I have corrupted a GS with 256?

Thank you in advance, and Happy Hunting!
-Wayne

[fitzcarraldo]

Hello Fellow Kaleuns,

I am currently in the Arctic campaign, and after returning to the patrol area around Bear island post Narvik refit, I am experiencing an unusual bug.
I have now attempted to attack two separate convoys, and experienced the same problem.
When I attack a convoy, the escorts (some of them) begin running in reverse, sometimes moving many kilometers away from the search area. The convoy itself does not "move off" to the opposite side post attack, but only sits there, and once the post attack search phase is complete, the convoy does not resume course, but only sits there. This causes my "save" to be corrupted, initiating CTD, no matter how long post attack, or how far away I go after the convoy attack.
I will post my mod-soup list, but must mention that this same mod soup has been running on my machine with no issues for over a year. Corrupted save somewhere perhaps? Open to ideas from the smart folks in this community.

I run TWoS 2.2.23 with Real Navigation on a Dell G3 with NVidia 1660 Ti GPU

Only additional mods on top of TWoS are :
Dark Interior V1
Stormys DBSM 1.3

I recently added/ Changed to SH3 GUI, and used Vecko's Glass covered dials.
I have since changed back, but cannot imagine any way these could be causing this behavior.

Fingers crossed someone here has experienced this, and has an answer to where my issue is coming from. Truly dont wanna lose my campaign, or spend 4 hours wiping everything, and reinstalling the works (which I just did a couple of months ago) One thing of note, I used to NEVER go beyond 128 TC, but have read several posts here from fellow Kaleuns (including Vecko) that 256 TC is ok in newer TWoS iterations. Could I have corrupted a GS with 256?

Thank you in advance, and Happy Hunting!
-Wayne

I don´t have these problems, could be a corrupted savegame (?). Also, I play with 2.2.24, the latest version. You have 2.2.23.

Best regards and good luck.

Fitzcarraldo :Kaleun_Salute:

[Rwearjr]

Thank you Fitz, This community is like none other for those of us bitten with the Sub simulation bug. I have no doubt that others would chime in to help, if the problem remained unsolved.
However, I think I may have resolved it. I removed the SH3 GUI, and the Glass dials, and voila' my convoy attack went normally and without a hitch. Let me be clear, I DO NOT think the the SH3 GUI OR Vecko's Glass dial mod CAUSED this issue, I am much more inclined at this point to think it would have been prudent on my part to enable these wonderful mods IN BUNKER, rather than out on patrol.

While we have this thread open, I would like to mention one other occasional bug I see (I have even re-installed the game due to this once) which still occurs ever so often in my new installation. Occasionally, I encounter a bug where my WO will not "see" a ship, or sometimes even an entire convoy. I cannot lock on to the target, hell, I can even join the convoy and sail along side them, due to the feature of the game in which if "you" cant see the target, it cannot see you. The few times I have had this occur, either diving and then resurfacing "causes" WO to "see" the enemy, or any type of firing on them which hits will cause WO to suddenly become aware of the enemy presence. It's not a huge issue, but has happened enough to find worthy of mention. I have had at least two occurences where NOTHING I did would cause my WO to "see" the target, yet I still gained the tonnage for sinking it.
Has any fellow skipper had this occur tp you?

Happy Hunting!
-Wayne

[les green01]

Thank you Fitz, This community is like none other for those of us bitten with the Sub simulation bug. I have no doubt that others would chime in to help, if the problem remained unsolved.
However, I think I may have resolved it. I removed the SH3 GUI, and the Glass dials, and voila' my convoy attack went normally and without a hitch. Let me be clear, I DO NOT think the the SH3 GUI OR Vecko's Glass dial mod CAUSED this issue, I am much more inclined at this point to think it would have been prudent on my part to enable these wonderful mods IN BUNKER, rather than out on patrol.

While we have this thread open, I would like to mention one other occasional bug I see (I have even re-installed the game due to this once) which still occurs ever so often in my new installation. Occasionally, I encounter a bug where my WO will not "see" a ship, or sometimes even an entire convoy. I cannot lock on to the target, hell, I can even join the convoy and sail along side them, due to the feature of the game in which if "you" cant see the target, it cannot see you. The few times I have had this occur, either diving and then resurfacing "causes" WO to "see" the enemy, or any type of firing on them which hits will cause WO to suddenly become aware of the enemy presence. It's not a huge issue, but has happened enough to find worthy of mention. I have had at least two occurences where NOTHING I did would cause my WO to "see" the target, yet I still gained the tonnage for sinking it.
Has any fellow skipper had this occur tp you?

Happy Hunting!
-Wayne
glad you got your problem fix far as wo not seeing might be a corrupt game what it sounds like so what i do is save every 72 game hours or if i see a convoy or hunting in a area that should be traffic i save then restart the game

[Rwearjr]

Thank you Les,

I appreciate your sharing these important tips, tips which Vecko includes in the TWoS Documentation, but aren't always followed, as I have seen even YT gamers not following these recommendations.
I do follow these, strictly, in fa ct, the only time I ever go over 48 hours is when a patrol zone requires 72 hours, or some other oddball situation. Please forgive me if incorrect, but I think Vecko says 48 hours, to 72 hours save and restart. I haven't reviewed the doc, so I might be wrong here. Things such as not saving near convoys, or land bases, etc.... I've been playing TWoS nightly for about the past 4 years, like so many, I tossed this game when it came out, and came back with TWoS, and find now that this somewhat dated sim may be IMHO the best SubSim out there right now.
The situation I am referring to tends to only happen at night, dusk, or dawn.
I theorize this may be due to altering the visual ranges to attempt replicating real world conditions during these times, and somehow it occasionally causes this problem, but since I am not a modder, I am not certain of this.
WHen this happens, I have tried everything within my power, including removing every "extra" mod I have other than TWoS, activating battle stations, etc... Nothing seems to help. Thinking this was a bug within my game, i deleted all files, and did a clean install again about a month ago. This still happens occasionally.
Thank you again for sharing advice, and helping out a fellow skipper!

Happy Hunting!
-Wayne