Torpedo Missing Long Consistently

embraceentropy · 12-15-20, 01:05 PM

I'm in a campaign and have had an acceptable amount of hits/misses given my experience level with manual targeting, especially sonar only.

I came across a Hakusika Maru about 10nm out. After plotting enough positions to come up with a target course I set myself up 90 deg off so I would be at ~3000yds when the target was in position. I continuously plotted for course and speed and everything was consistent with speed at 9kts (confirmed via 2:58 rule and longer/shorter time spans). At periscope depth with scope down, I confirmed the target was not alarmed. I prepared my solution, tripled checked everything on the PK after confirming range/bearing. After opening the tubes, PK looked perfect, I fired a two shot spread (~2.5 degrees) and both missed way long (~700yds ahead of the target). I checked everything again, refreshed my solution, fired a single shot, missed ~700yds long.

Fortunately I saved during the hunt, so out of curiosity I loaded back in. This time I used the scope, confirming speed with the chrono and scope (still 9kts), distance between omnimeter, stadimeter & sonar surprisingly close to each other. Double/triple checked, open tubes, fired, missed ~700yds long.

I then continued to re-load the scenario about 10 times, trying different parameters, contacts, PK on/off, taking extra measurements, etc. Still consistently missing ~700 yards long. At one point I went along parallel and matched speed, 9kts, entered solution, fired, ~700 yds long.

I then tried setting the speed slower & slower in the PK until I got a hit. Finally, I found that setting target speed to 5kts in the PK (actual target speed still measured at 9kts) yielded a dead center hit 3/3 attempts.

Confused, I tried the subs school torpedo mission, slapped a quick, dirty solution together (using actual measured speed) and landed a hit at the tip of the stern, but a hit nonetheless.

Thinking it was mod soup, I completely uninstalled, cleaned registry, reinstalled, and applied the minimum mods. Exact same result!

The only torpedoes in my tubes in that save are MK18s, so I can't narrow it down to that being an issue.

Mod List (in order):
1_TriggerMaru_Overhaul_2-5
RSRDC_TMO_V502
RSRDC_V5XX_Patch1
1.5_Optical Targeting Correction 031312 for RSRDCv502
1.5_OTC_Realistic Scopes for 16 to 9 RSRDCv502
Webster's Eliminate Floating Plankton
Bigger Better Protractors

What could this be?

Edit/Update: In the same campaign I went on with my patrol and came across a merchant of a different class. Did the work-up with 7kts calculated & confirmed, missed long ~700 yards. I set the PK speed down to 3kts, refreshed my solution, hit midship. I re-loaded, emptied a tube, and loaded a MK14. Same work-up, missed long ~700 yards.

propbeanie · 12-16-20, 11:00 AM

You appear to have a good mod list, but since OTC is "targeting", I would put it in last, just to be certain. Either that, or temporarily remove the plankton & protractors for testing purposes. You don't happen to have any ships you added to your set-up, that aren't in mod form? Any additions would not be in OTC's "database", of course...

embraceentropy · 12-16-20, 11:53 AM

I removed the plankton & protractor mods. Re-loaded, same parameters, missed at PK set to 9kts, dead center hit with PK set to 5kts.

Besides the mod list the only other modification is the 4GB patch. I haven't added or changed anything except for the few lines with unittype, eqp line duplciates, or minor defside date changes as identified by SH validator. None of the configs edited applied to the two merchants encountered during this testing.

With me simply dropping this savegame from my old install into my new install, could it be carrying around a bug from my last install that could cause this? Is there something I could look for?

propbeanie · 12-16-20, 12:03 PM

Ah-HA!!! ding ding ding... we have a potential ~winner~!!! Even with as near of a match to a previous mod-set as is humanly possible, the game for whatever reason, finds it very difficult to run again off of an old install's Save folder, especially if on a new computer. So "yes", that would be my primary suspect now. Try copying and / or moving the Save folder to keep it away from an experiment, so that you can pull it back in later, if this test fails. Once you have the Save data "safe", delete the current Save folder, re-do all of your in-game settings etc., and try again.

embraceentropy · 12-16-20, 09:03 PM

I backed-up the My Docs folder right after I re-installed. I was able to bring it back to, basically, a fresh install with mods.

I launched a new campaign, stalked my first contact, set up at ~3000 yards, same results as before. I then re-loaded and tried the O'Kane method. The first torpedo was aimed at the front mast and it missed long. The second torpedo was aimed at the aft mast and it hit at the forward mast. While I was excited to hit something again, I was bummed that it didn't workout as planned. Especially considering the videos with folks nailing dead nuts at 8000 yards with a Mk14.

Would there be something else that could be affected by me using a savegame from my old install?

Unless there is a parameter out there that could be screwing me, I think something is messed up in my method. However, what would be the likely culprit to have such consistent misses (20X+) and being able to reduce speed by ~5kts to nail the target every time? How off would AOB have to be cause a miss like that?

The only other thing that has changed was my use of a streamdeck XL as a button box including torpedo door, cycle, & fire buttons. Nothing complicated, just emulating keystrokes with no noticeable lag.

I'm at the end of my rope with this and it is really sucked the fun out of it for me.

embraceentropy · 12-17-20, 08:49 PM

I did some more testing. I was able to figure out that my periscope shots were off because I wasn't clicking the buttons twice each time I made an adjustment.

This is still happening when I try to only use sonar for range and bearing into the PK. I confirmed the information being input by the sonar operator were correct by viewing through the scope and confirming AOB/Distance with the stadimeter. Just before firing I have the operator ping the target twice and I update the bearing & range by clicking each twice on the HUD just before hitting the button. Is there a trick/quirk/best practice when shooting only with sonar inputs?

12-15-20, 01:05 PM	#1
embraceentropy Seaman Join Date: Dec 2020 Location: Georgia, USA Posts: 34 Downloads: 71 Uploads: 0	Torpedo Missing Long Consistently I'm in a campaign and have had an acceptable amount of hits/misses given my experience level with manual targeting, especially sonar only. I came across a Hakusika Maru about 10nm out. After plotting enough positions to come up with a target course I set myself up 90 deg off so I would be at ~3000yds when the target was in position. I continuously plotted for course and speed and everything was consistent with speed at 9kts (confirmed via 2:58 rule and longer/shorter time spans). At periscope depth with scope down, I confirmed the target was not alarmed. I prepared my solution, tripled checked everything on the PK after confirming range/bearing. After opening the tubes, PK looked perfect, I fired a two shot spread (~2.5 degrees) and both missed way long (~700yds ahead of the target). I checked everything again, refreshed my solution, fired a single shot, missed ~700yds long. Fortunately I saved during the hunt, so out of curiosity I loaded back in. This time I used the scope, confirming speed with the chrono and scope (still 9kts), distance between omnimeter, stadimeter & sonar surprisingly close to each other. Double/triple checked, open tubes, fired, missed ~700yds long. I then continued to re-load the scenario about 10 times, trying different parameters, contacts, PK on/off, taking extra measurements, etc. Still consistently missing ~700 yards long. At one point I went along parallel and matched speed, 9kts, entered solution, fired, ~700 yds long. I then tried setting the speed slower & slower in the PK until I got a hit. Finally, I found that setting target speed to 5kts in the PK (actual target speed still measured at 9kts) yielded a dead center hit 3/3 attempts. Confused, I tried the subs school torpedo mission, slapped a quick, dirty solution together (using actual measured speed) and landed a hit at the tip of the stern, but a hit nonetheless. Thinking it was mod soup, I completely uninstalled, cleaned registry, reinstalled, and applied the minimum mods. Exact same result! The only torpedoes in my tubes in that save are MK18s, so I can't narrow it down to that being an issue. Mod List (in order): 1_TriggerMaru_Overhaul_2-5 RSRDC_TMO_V502 RSRDC_V5XX_Patch1 1.5_Optical Targeting Correction 031312 for RSRDCv502 1.5_OTC_Realistic Scopes for 16 to 9 RSRDCv502 Webster's Eliminate Floating Plankton Bigger Better Protractors What could this be? Edit/Update: In the same campaign I went on with my patrol and came across a merchant of a different class. Did the work-up with 7kts calculated & confirmed, missed long ~700 yards. I set the PK speed down to 3kts, refreshed my solution, hit midship. I re-loaded, emptied a tube, and loaded a MK14. Same work-up, missed long ~700 yards. Last edited by embraceentropy; 12-15-20 at 06:23 PM.

12-16-20, 11:00 AM	#2
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 9,749 Downloads: 439 Uploads: 2	You appear to have a good mod list, but since OTC is "targeting", I would put it in last, just to be certain. Either that, or temporarily remove the plankton & protractors for testing purposes. You don't happen to have any ships you added to your set-up, that aren't in mod form? Any additions would not be in OTC's "database", of course... __________________ "...and bollocks to the naysayer/s" - Jimbuna

12-16-20, 12:03 PM	#4
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 9,749 Downloads: 439 Uploads: 2	Ah-HA!!! ding ding ding... we have a potential ~winner~!!! Even with as near of a match to a previous mod-set as is humanly possible, the game for whatever reason, finds it very difficult to run again off of an old install's Save folder, especially if on a new computer. So "yes", that would be my primary suspect now. Try copying and / or moving the Save folder to keep it away from an experiment, so that you can pull it back in later, if this test fails. Once you have the Save data "safe", delete the current Save folder, re-do all of your in-game settings etc., and try again. __________________ "...and bollocks to the naysayer/s" - Jimbuna

12-16-20, 11:53 AM	#3
embraceentropy Seaman Join Date: Dec 2020 Location: Georgia, USA Posts: 34 Downloads: 71 Uploads: 0	I removed the plankton & protractor mods. Re-loaded, same parameters, missed at PK set to 9kts, dead center hit with PK set to 5kts. Besides the mod list the only other modification is the 4GB patch. I haven't added or changed anything except for the few lines with unittype, eqp line duplciates, or minor defside date changes as identified by SH validator. None of the configs edited applied to the two merchants encountered during this testing. With me simply dropping this savegame from my old install into my new install, could it be carrying around a bug from my last install that could cause this? Is there something I could look for?

12-16-20, 09:03 PM	#5
embraceentropy Seaman Join Date: Dec 2020 Location: Georgia, USA Posts: 34 Downloads: 71 Uploads: 0	I backed-up the My Docs folder right after I re-installed. I was able to bring it back to, basically, a fresh install with mods. I launched a new campaign, stalked my first contact, set up at ~3000 yards, same results as before. I then re-loaded and tried the O'Kane method. The first torpedo was aimed at the front mast and it missed long. The second torpedo was aimed at the aft mast and it hit at the forward mast. While I was excited to hit something again, I was bummed that it didn't workout as planned. Especially considering the videos with folks nailing dead nuts at 8000 yards with a Mk14. Would there be something else that could be affected by me using a savegame from my old install? Unless there is a parameter out there that could be screwing me, I think something is messed up in my method. However, what would be the likely culprit to have such consistent misses (20X+) and being able to reduce speed by ~5kts to nail the target every time? How off would AOB have to be cause a miss like that? The only other thing that has changed was my use of a streamdeck XL as a button box including torpedo door, cycle, & fire buttons. Nothing complicated, just emulating keystrokes with no noticeable lag. I'm at the end of my rope with this and it is really sucked the fun out of it for me.

12-17-20, 08:49 PM	#6
embraceentropy Seaman Join Date: Dec 2020 Location: Georgia, USA Posts: 34 Downloads: 71 Uploads: 0	I did some more testing. I was able to figure out that my periscope shots were off because I wasn't clicking the buttons twice each time I made an adjustment. This is still happening when I try to only use sonar for range and bearing into the PK. I confirmed the information being input by the sonar operator were correct by viewing through the scope and confirming AOB/Distance with the stadimeter. Just before firing I have the operator ping the target twice and I update the bearing & range by clicking each twice on the HUD just before hitting the button. Is there a trick/quirk/best practice when shooting only with sonar inputs?