Trying to Learn Manual Targeting - Failing in the Process

[jgbishop]

I'm trying to figure out how to do manual targeting. I've watched a number of training videos, but I still can't seem to figure it out. All my testing is taking place in the Submarine School mission with the heavy cruiser (torpedo training mission, I think). I guess I'm getting confused on the order of operations. Here's what I'm doing:

1. Identify the ship (Mogami Heavy Cruiser).
2. Find the range to the ship with the stadimeter (this I can do). Send said range to the TDC.
3. Ready a few torpedoes.
4. After some time, take another range to the ship. Again, send to TDC.
5. Start position keeper.
6. Estimate speed and bearing (I'm using the estimate button on the speed dial).
7. Adjust angle on bow to match computed heading. Send to TDC.
8. Fire torpedoes.

Every time I do this, I miss the ship by a good 100 to 200 yards. What am I doing wrong? Can someone provide an order of operations guide as to what has to happen and when? I'm getting so frustrated being in the dark on this!

:damn:

[Captain von Keldunk]

Hello
i have trained manual targetin same way as you. it was some time ago
and now can not remember it all. but this one, make sure that
positonkeeper is off before you start as it can contain old data.
item 0 in your list should be turn off positionkeeper.:yep:
I now remember that my worst mistake was that i Adjusted angle on bow
to right when it shoud have been left.:nope:

[ridyard12]

im in the same boat as you so to speak.

for that mission you start off close to the cruiser in broad daylight, something you wouldnt risk in say a campaign without some confidence and skill. this results in little time to react.

anyways:

1. have your sonar man constanly update the target bearing etc with the corresponding button in the sonar panel.

2. up periscope, i.d. the target as the heavy cruiser, making sure u lock periscope to target before sending the mast height, or it wont send properly.

3. use stadmeter to get the range & bearing and send to TDC.

4. guess the speed & AOB for now, based on the sonar opperators target report (his mention of speed i.e. fast, slow or medium) make a judgement based on the target max speed from the recognition manual also.

5. down periscope. use the periscope sparingly as the longer it is up the higher the risk of being spotted; causing target evasive action, and escort attacks.

4. set up torpedoes, including speed, depth and open torpedo doors.

4. pay attention to the sonar opperators target bearing reports, and when the target approaches bearing around 340 up periscope and take another stadmeter range & bearing and send to tdc.

5. click on the speed button and on the top left you will see a watch icon, click this and your crew will work out the target speed and course in degrees from North. (0 degrees would be north, 90 degrees is east etc).

6. send the estimated speed to tdc, then rotate and change the AOB wheel till the target course estimated by your crew shows on the position keeper window upper target wheel (far left panel). the zero on the inner wheel should point to the number on the outer wheel that corresponds to the estimated target course given by your crew.

7. activate the position keeper, update the bearing and range. i usually just update the bearing on its own by just clicking on the send to tdc button, obviously while the target is locked to periscope.

8. check the AOB/target course on the position keeper target wheel has not deviated, from the crew estimate. if so resend the correct value to TDC.

9. down persicope, fire topedoes.

i play with full realism settings and no map contact update, but im still learning. i personally like to plot the target position often on the map, and work out the target course and AOB from that, followed by a comparison with the crews estimates.

comments and criticism welcome.

[Bubbles68]

I also plot the target on the nav map to check the crew estimates of course and speed, and help me set up my firing position.
Also, jgbishop, you only mention 2 observations of the target. That's enough to get a solution, but not to check it. And the crew's course/speed estimates can be off.

So, I would only add one thing to ridyard and keldunk: once the position keeper is on, you can look at it to see the bearing and range according to the solution in the TDC - it's small, but readable. Whenever you take a bearing/range observation look at how the solution in the tdc changed - I mean the bearing and the range. If the bearing is not what you expect, your course/speed are probably not right. For example: target heading east, you are heading north, target is on your left, say relative brng 320 and going to cross in front of you. After a few minutes the tdc says the target's rel. brng is now 325. If you put up the scope and the target is more to the right than expected, like at 330 instead of 325, your solution speed could be slower than target's actual speed. You could raise the speed a knot, check everything else in the tdc (reset the AOB to the course you think target is on), and check it again after a minute or two. Once your solution is such that the tdc's current bearing and the target's current bearing stay matched, it's good. (The bearing difference can also be caused by other things than speed errors, it could be that the range is off or the AOB is wrong. Use all your other data to make your best guess - observed AOB, crew's estimates, what you get on the nav map plot if you did it. But at least for me, it's usually a speed error, or combined course/speed error.)

Also, I never had much luck with the training missions. I remember SH3's torpedo training mission, with the cargo ship that suddenly started it's engines after you fired. I learned manual targetting by finding my first convoy in a career, saving the game, and trying my approach a few times until I got the torps to hit.

Keep trying. I was really frustrated at first, but when I got my first hit, I was so excited I wanted to tell everyone. But no one around me cared.:cry:

[jazman]

Keep trying. I was really frustrated at first, but when I got my first hit, I was so excited I wanted to tell everyone. But no one around me cared.
That's what subsim is for. You just need to check in the Kumbaya forum. ;)

[jgbishop]

Also, jgbishop, you only mention 2 observations of the target. That's enough to get a solution, but not to check it.
This is mostly due to the fact that in the training mission, I only have a very short amount of time to set things up. Submarine school leaves a lot to be desired, especially in this particular situation. A mission where the ship started a long ways away would be a lot better for training purposes.

I'll just start up a new campaign and see what I can do. Thanks for all the tips!

:up:

[momo55]

Don't forget to open the torpedodoors ...;)

[Joe S]

It is likely that your error is due to incorrect speed.The TDC speed estimator using the two scope observations is only accurate under ideal conditions, and then only if you have a good range estimation, which can be tricky. I suggest using the time/distance method to estimate speed and input speed manually. Another suggestion is to fire from close range which would be 400 to 750 yds, and try to set up a 90 degree shot, which means point your boat on a course 90 degrees to the target's course. That way you can set up your aob for a 90 deg shot, in which case minor discrepancies in the aob are not important. One more thing, before firing, take a quidk look at the attack map to make sure the torps (green line) are pointed at the correct tiarget. I hope this helps., JOe S

[Nisgeis]

I did initially start this as a small paragraph on what was wrong, but well, look what happened! I too had problems when I first tried manual targetting and I though it was important to not only explain how to do it properly, but to explain exactly why it wasn't working, as that's the real key to understanding the proper use of the TDC.

Hi jgbishop. I followed your instructions to the letter and I also missed about half a ship length to stern. Your TDC is just a computer that can very quickly compute all aspects of the target and yourself, but it's got no common sense. It's basically a really fast idiot.

What it belives is going on, is determined by the data you tell it and the order you tell it in. The TDC will compute target course based on all information it has, however wrong that information is. To try to explain what's going on, the following explains what you think is happening and what the TDC thinks is happening. Just remember, Captains are from Mars, TDCs are from Venus.

Anything in green is correct information that the TDC has and red is incorrect at the time of the operation given.

1. Identify the ship (Mogami Heavy Cruiser).
TDC Knows> ALL DEFAULT - Range: 547, AOB: 0, Bearing: 0, Speed: 0
TDC Thinks> Target is dead ahead with bow pointing directly at the submarine, 547 yards away and stationary.

2. Find the range to the ship with the stadimeter (this I can do). Send said range to the TDC.
TDC Knows> Range: 1600, AOB: 0, Bearing: 321, Speed: 0
TDC Thinks> Target is on bearing 321, 1600 yards away and stationary.

3. Ready a few torpedoes.
TDC Knows> Range: 1600, AOB: 0, Bearing: 321, Speed: 0
TDC Thinks> No Change. (Target data is decaying. range and bearing have become incorrect - bearing rapidly decays.)

4. After some time, take another range to the ship. Again, send to TDC.
TDC Knows> Range: 1500, AOB: 0, Bearing: 326, Speed: 0
TDC Thinks> Target is on bearing 326, 1500 yards away and stationary.

5. Start position keeper.
TDC Knows> Range: 1500, AOB: 0, Bearing: 326, Speed: 0
TDC Thinks> I'm now tracking a target that is on bearing 326, 1500 yards away and stationary. Target heading is 146 (derived from AOB, target bearing and submarine's own heading. Note that this heading is incorrect, as it is derived from data that is not correct as the AOB is wrong.)

6. Estimate speed and bearing (I'm using the estimate button on the speed dial).
NOTE: The only way to send new bearing information with the periscope is to use the 'send range and bearing to TDC' button. You're not clear whether you are just sending the speed information (which does not send new bearing data) or whether you are sending the speed and then sending the bearing by sending the range again (which will give the wrong range, unless you retake it with the stadimeter). I'll assume for the sake of this explanation, that you have just sent speed.

TDC Knows> Range: 1500, AOB: 0, Bearing: 326, Speed: 9
TDC Thinks> I'm tracking a target that is on bearing 326, 1500 yards away and is steaming directly towards me at 9 knots on a southeasterly course of 146. NOTE: This makes the TDC rapidly decrease the range between you and the target at a rate of 100 yards every 20 seconds, as it thinks it is steaming towards you, instead of accross your bow. This error is compounded by the bearing also being incorrect, when the proper bearing of the target is changing, as it is steaming accross your bow. All target data decays, but this is now a solution for a problem that does not match reality, so all target data (except speed) is being actively corrupted. What is actually happening is the range is changing fairly steadily (it should reduce a bit and then increase as the Mogami crosses your bow) and the bearing should be changing quite fast. The TDC however has the bearing as static and the range changng quite fast.

If you had sent range and bearing to get a new bearing to the TDC, the bearing and speed would be correct, but the AOB and Range would be incorrect and the TDC would still think the target was steaming directly towards you at 9 knots, on the correct bearing but but further away that it actually was. The calculated course would also be incorrect. This would also cause the data to rapidly become corrupted (except of course speed). The bearing would also still be static and the range rapidly changing, which as we know should be the other way round.

7. Adjust angle on bow to match computed heading. Send to TDC.
TDC Knows> (Depending on how long you take to do it) Range: 1100, AOB: 70, Bearing: 326, Speed: 9.
TDC Thinks> Now tracking a target steaming NE accross submarine's bows, range is 1100 and steaming at 9 knots. This solution is wrong, the TDC believes the ship to be on the wrong bearing, so it will interpret the AOB you give it as incorrect and derive a course that is 076 (instead of 090 as it should be). This point may be a bit confusing, so let me explain further:

In the Torpedo Training exercise, the Mogami is steaming on a course that is roughly 090, or due East. You are pointed 000 due North. Imagine you take a range and bearing when the Mogami cruiser is at bearing 326. With the AOB incorrecty set at 0 degrees, TDC calculates that the Mogami's course is 146 (approximately SE). Then, things get even worse.

To illustrate the point I will exaggerate things and let's say we wait between range and bearing taken at bearing 326 and taking the AOB measurement. The cruiser will steam across your bow and will end up dead ahead at a bearing of 0 degrees, so let's say that you use this opportunity to get a really accurate measurement of the AOB and as it dead ahead and at a right angle to you, the AOB is 90 degrees to starboard. If you send this AOB to the TDC, the TDC will calulate the Mogami's new course based on the bearing it previously had and will track the target from this point. Unfortunately, as the TDC still thinks the Mogami is on bearing 326 and not bearing 000 as it actually is, it will think you are now telling it that the Mogami has suddenly turned from steaming directly towards you, through 90 degrees to port and that you are now abead of the Mogami. The TDC calulates the new course, based on bearing, AOB and submarine's heding. A 90 degree turn to port on a ship travelling SE would now mean that the ship is travelling NE on a course of 056 and this is the value that the TDC gets from the wrong bearing, correct AOB and correct submarine's heading. The course is incorrect by 34 degrees (056 compared to 090) and this matches the difference between the correct bearing to target and the incorrect bearing the TDC has (326 compared to 000).

The rate of error between actual course and TDC generated course depends on how long you wait between sending range and bearing and the AOB to the TDC. The timing of this is particularly important on targets that are at extremely close range, as both their bearing and AOB change rapidly the closer to you they are.

As you can see, your current soluton now has the target too close, on the wrong bearing and on the wrong course, but the speed is good. The solution, as inaccurate as it is will get rapidly worse the longer you wait to fire and any topredoes fired will be aimed by the TDC aft of the ship.

8. Fire torpedoes.
TDC Thinks> This one's in the bag!
Result: Miss. Miss. Miss. Captain... Report to the SS Garbage Scow.

It doesn't really matter when you start the Position Keeper, the key is to send it data regularly and to be aware of what affects what. You should try to make sure that ALL data is as up to date as possible. It is best to estimate the AOB and speed first, send them to the TDC and then send the range and bearing. The reason for this is that the bearing is the MOST accurate reading you can obtain, so sending this last will reduce the amount of error creeping into the solution, by resetting the aiming point. Errors in the AOB, range and speed will introduce errors over time, at a rate depending on how inaccurate your estimates are. As long as you are attacking your target from a position from which the target's length is optimal, or near optimal (as long a target as possible) then 10 degree errors in the AOB and a few hundred yards error in range don't matter that much as long as you use a reasonable spread.

Experiment with different spreads. I try to use an 80% spread, which means that if I aim at the centre of the hull with 4 torpedoes, then all four should hit, with tropedo no. 1 hitting near the stern, no. 2 hitting aft of the centre of the hull, no. 3 hitting forward of the centre of the hull and no. 4 hitting near the bow. A 150% spread would mean that if all torpedoes were aimed correctly, the torpedoes would spread out to a distance of 150% of the length of the ship aimed at, so not all would hit, but you would have more chance of hitting, albeit with less torpedoes. This is good for when your target data is poor or hard to obtain (can't see waterline due to rough weather, for example).

The key to using the TDC is to give it the best data you can, with as short an interval between the speed, AOB and range estimates as possible and to check it and re-enter is necessary. You can put in your first reading and then a short while later, check the generated target data from the TDC generated when the Position Keeper is switched on and compare it to the data you can observe. The TDC will calculate where the target will be, based on the information it has been gven. If you have given it 100% correct data, the generated bearing, range and AOB will all match what you can observe. If the generated data doesn't match, then the solution is not correct. It's important to note that if your solution isn't correct, then simply resending a new range and bearing won't correct it. Assuming you have identified the target correctly and the range is fairly reliable, then you either have the target speed or the AOB wrong.

Incorrect speed will mean that the target's generated bearing advances too fast if you have estimated the speed to high, or doesn't advance as fast as observed if you have estimated the speed to low. In the torpedo training exercise, if you estimated the Mogami at bearing 326, range 1500, speed 12 knots and ran PK for a while, the TDC would generate a solution for where it should be if the data is correct. If the generated bearing after 1 minute says it should be 346, but it is actually observed at bearing 336 then it's likely you have the speed estimated wrongly. Reset the target speed to 6 knots (as the bearing was 20 degrees advanced instead of 10 degrees), send to TDC then resend AOB and Range and bearing. Run PK for another minute and match the generated bearing to the observed bearing.

If the bearings match and you have identified the target correctly, then you probably have the correct speed. It's possible of course that you got the AOB wrong and the target is steaming towards you or away from you at a steeper angle. If this is the case, then you will find that the generated range does not match the observed range. If you find the range is consistenly observed as being closer than the generated solution says, then the target is closing on you faster than you thoguht and the AOB is too high and needs to be reduced (ship turned so that the bow points more towards you), to give you a course that is closing faster. If the range is increasing, the AOB is too small and needs to be increased (bow turned to point further away) as the target is steaming away from you.

If the target is steaming away or toward you on a different course, once you have the correct course, you will need to increase the target's speed and send it to the TDC, or the generated bearing will lag behind the observed bearing.

Small errors on the AOB and speed don't matter that much, just experiment and see what happens.

Make your TDC do the work and make it tell you what data is correct. Compare generated data to observed data and you'll soon get the hang of what the TDC is all about. I've made shots on tankers at 8,000 yards using the TDC to correct itself like this and that's very satisfying.

You should also look into the O'Kane method, as that may suit you better.

Sorry this is so long, but I hope it helps.

Nisgeis.

[DS]

Great post!

I get good accuracy with the TDC, including one hit out of a narrow spread of three torpedoes on a tanker from over 5000 yards last night.

My simplistic method that is working for me is:

1. Set torpedo speeds and depths as I expect to need. Open outer doors.

2. Select and identify ships I wish to attack.

3. Aproximate angle on the bow based on convoy course, but do NOT enter the data.

4. Target the first ship to be attack and range it, entering the data.

5. Quickly fine tune angle on the bow for this target and enter it.

6. Repeat steps 4 and 5.

7. Get TDC generate speed estimate. If it makes sense, enter it. If it seems off, repeat steps 4-7 until I get a reasonable speed generated (I only have to repeat the procedure 1 time out of three on average, and usually only in rough seas or at longer ranges where by AOB estimation was off.

8. Launch torpeodes and watch the fireworks.

[SeaQueen]

I don't know if these helps, because I've only got maybe 50/50 odds (on a good day) of scoring a hit right now, but I manually calculate the target's speed sometimes in order to check what was going on. I use the stopwatch to count the rate his bearing his changing in degrees per minute, B. From there here's what I do:

B * 60 = b (Bearing rate in degrees per hour)
b * pi / 180 = w (Bearing rate in radians per hour)
R = Stadiametric range
w * R = V (Target speed in yards per hour)
V / 2000 = v (Target speed in knots)

Usually, if I'm going slow, that works out to be pretty close to the target's speed. In fact, when I do it this way, I often do better hitting than when I use the sim's automated tools.

[Joe S]

Just about any method of calculating speed is better than the speed calc button. Using the speed calc button depends on an accurate range estimation , which can be difficult to do in rough weather and if the mast is not always consistently visible. Keep in mind that speed is the most critical component of a good firing solution. JOe S

[SeaQueen]

Just about any method of calculating speed is better than the speed calc button. Using the speed calc button depends on an accurate range estimation , which can be difficult to do in rough weather and if the mast is not always consistently visible. Keep in mind that speed is the most critical component of a good firing solution. JOe S

My calculation depends on having an accurate range. I suspect the computer does the same thing I do. The thing I've noticed is that I'm a lot faster. With 30 seconds of data I can get a reasonably accurate range. The computer requires more.

[Caltone]

I agree the speed estimate is a likely problem here. Try the nomograph (available in several mods or stand alone) and see if that helps your results.

The Mogami sub school mission starts off right in the action and you'll have very little time to react. You might consider setting up you own mission with a known ship type and speed so you can judge your calculated results.

[ridyard12]

one good tip that ive learned is that sometimes its easier not to think of AOB but of target course relative to north. (north = 0, east = 90, south = 180 etc)

the AOB can constantly change as your submarine and the target moves, but the target sometimes remains on a constant course.

for example, say you worked out that the target is heading East, which is a course of 90 degrees, the AOB at any one time is simply the value that puts the target heading on the TDC panel to 90 degrees.

sometimes when you update the range and bearing with the stadmeter, the AOB value gets corrupted, so in the above example you would re-enter an AOB value that would set the target course to 90 degrees in the tdc.

through plotting you can workout a target course, and use this value over again, rather than keep re-calculating the AOB.

AOB confused me a bit when i started manual TDC but learning this, helped me out a lot, hope this helps you too.

[Rockin Robbins]

Here's a complete breakdown of the procedure I did for another person with a similar situation. I find that the problem is that remembering all the steps is not enough. You always have to know their relationship with each other and what step order works and what order results in a stale solution. The only thing that fixes it is repetition and adherance to a fixed collection of actions. Once you get that working automatically without having to rack your brain, then you can work on varying the procedure to fit different circumstances.

In other words, while you are learning, be very rigid. Once you see the forest, not merely a collection of trees that don't seem to fit together, branch out to expand your bag of tricks. The link (http://www.subsim.com/radioroom/showpost.php?p=774607&postcount=5).

Then you might want to check Aaronblood, gutted and my Dick O'Kane targeting technique (http://www.subsim.com/radioroom/showpost.php?p=652326&postcount=67). You can set up the whole attack in the TDC 15 or 30 minutes ahead of your actual approach and firing! Then you can tell your exec, "I'm going to take a nap. Wake me when the target bears 340º." Real captains did that (probably couldn't really sleep) to show the crew that he respected them as professionals who didn't need to be micromanaged. It really built up crew confidence if the captain didn't have a heart attack while he pretended to sleep!

You can do it, and it doesn't have to be too technical to understand.:up:

[SeaQueen]

Here's a couple other suggestions I've found help:

Set your torpedoes to high speed. It makes the results less sensitive to the inherent uncertainty in your measurements.

Shoot at WELL under 1kyd. Ideally less than 0.5kyd even.

[Bubbles68]

Just to second ridyard's last post: when you update the bearing and range in the tdc, the tdc just rotates the given AoB and speed to the new bearing and moves it in or out to the new range. So, you always need to adjust the AoB after updating the bearing, unless the actual bearing and predicted bearing from the tdc are the same.

Another thing I did to figure this stuff out was to just play around with the tdc and see how it works. For example, on the surface, dead in the water, just point the periscope dead ahead, and send the bearing and range to the tdc (no target, just point at empty sea). then enter in a random speed, like 5 knots, and an AoB like S90. Then start the PK and watch the target's predicted position move on the tdc and the attack map. Then change something and see what it does. For example, turn the periscope 90 degrees and send the bearing/range to tdc again, and you'll see that the target's course on the attack map will be changed 90 degrees from what it was before. WernerSobe's videos are good to watch too.

As far as calculating speed, I think SeaQueen's method, which is like the old speed button in SH3, is cool. I usually use the nav map - every 2 minutes or something, plot lines of bearing and put a mark at the range. then extend the line of bearing a bit and leave them there. that way if your ranges are off, you'll be able to see the fan of bearing lines and estimate a good course that goes between all the range marks and cuts the bearing lines in equal intervals. This is just like using speed strips in TMA, such as in DW. Works well if you've got time and in bad weather if you can't get good ranges.

[walrusbomb]

I stopped using the position keeper all together.

I like to use sonar to find bearing and estimated range. I plot the target's est. course and make the minute marks for est. speed.

All I have is my initial solution scribbled on the map in pencil; actual bearing, est. range, est. AOB, est. speed.

I've entered nothing in TDC at this point.

I get closer, improve my angle of attack (slice the pie). raise scope to ID target. is it even an enemy? (long story.) Scope goes immediately back down.

Ready my torpedos. I like a high-low spread: 15", 8", 16", 10". Deeper for battleships and carriers.

Repeat sonar targeting: actual bearing, est. range, est. AOB, est. speed. Compare to my original pencil marks. If it looks good, start entering the data into the TDC. If it looks off, repeat sonar. Be careful not to ping DD's and Subchasers too much as they will hear you. Ping em' twice and estimate range.

actual bearing, est. range, est. AOB, est. speed.

looks good. enter the data into TDC... FIRE 75% spread.

[ridyard12]

I like to use sonar to find bearing and estimated range. I plot the target's est. course and make the minute marks for est. speed.


if its a warship that your pinging, its going have a lock on you and drop lots of presents in the water, wether its your birthday or not.

but for merchants, its a great way to plot target course whilst remaining unseen.

[walrusbomb]

I like to use sonar to find bearing and estimated range. I plot the target's est. course and make the minute marks for est. speed.

if its a warship that your pinging, its going have a lock on you and drop lots of presents in the water, wether its your birthday or not.

but for merchants, its a great way to plot target course whilst remaining unseen.

IDK, I ping warships without detection. It's all about moderation. I go on to warn about this but you didn't quote that part.

"You dont go berserk in front of a dragon." --Sven the Berserk's Dad

[ridyard12]

[quote=ridyard12][quote=walrusbomb]
Be careful not to ping DD's and Subchasers too much as they will hear you. Ping em' twice and estimate range.

ah so you did :), i must have been too eager to use the "drop lots of presents in the water, wether its your birthday or not" line.

[walrusbomb]

1. I like presents.

2. I like to machine-gun ping their subchaser right as I fire off a fatal burst from 800y. And then not change heading.

See #1.

[Rockin Robbins]

What are you calling a 75% spread? Your prescription is going to miss astern, by the way. Only a lucky spread angle ahead of your "solution" is going to save your attack. No PK plus wrong order of entering parameters equals lotsa misses.

I know you can sink ships that way, but half your torpedoes end up wasted. I just hate to miss (although I'll be the first to admit that I sometimes do). It's a character defect, I'm sure.:rotfl:

And finally, why would you enter a surface action against a warship with two big guns to your one and with more machine guns as well? It has been said that if you find yourself in a fair fight it's because you screwed up your planning. Well, here you are with 2 to 1 odds against. Not smart. You took a situation where you held the winning hand, discarded three Aces and picked up deuce, five, seven and then raised. Hope you brought lots of cash to the table because it's all mine!:up:

[walrusbomb]

What are you calling a 75% spread? Your prescription is going to miss astern, by the way. Only a lucky spread angle ahead of your "solution" is going to save your attack. No PK plus wrong order of entering parameters equals lotsa misses.

I know you can sink ships that way, but half your torpedoes end up wasted. I just hate to miss (although I'll be the first to admit that I sometimes do). It's a character defect, I'm sure.:rotfl:

And finally, why would you enter a surface action against a warship with two big guns to your one and with more machine guns as well? It has been said that if you find yourself in a fair fight it's because you screwed up your planning. Well, here you are with 2 to 1 odds against. Not smart. You took a situation where you held the winning hand, discarded three Aces and picked up deuce, five, seven and then raised. Hope you brought lots of cash to the table because it's all mine!:up:

I'm not going to lie, I miss a lot. :lol: And they'll never find the bourbon I hide on my Norwhal!!1

I mean't 75% of the ship's length... the cone of my spread.

Surface Action? That wasn't me or you're misreading... I *never* fire my deck guns at anything not made of WOOD! And even then I've very very nervous.

I was joking about hyper-pinging a subchaser... and I know a DD can hear even 1 ping. But since I'm often detected without a ping and often NOT-detected with ping, I lack this "fear of pinging a DD" altogether.

I feel so naked with my scope up. :huh:

[Rockin Robbins]

I'm not going to lie, I miss a lot. :lol: And they'll never find the bourbon I hide on my Norwhal!!1

I mean't 75% of the ship's length... the cone of my spread.

Surface Action? That wasn't me or you're misreading... I *never* fire my deck guns at anything not made of WOOD! And even then I've very very nervous.

I was joking about hyper-pinging a subchaser... and I know a DD can hear even 1 ping. But since I'm often detected without a ping and often NOT-detected with ping, I lack this "fear of pinging a DD" altogether.

I feel so naked with my scope up. :huh:[/quote]

Yup the 75% of the ship's length makes sense. I'd recommend that you never spread behind the TDC solution, only ahead. And wood makes the preferrable target to be sure.

Where you really hit the nail on the head is in deciding when stealthy is not healthy. If they already know where you are, ping away. If they already have detected you forget about ahead 1/3 and make some tracks. Reload torpedoes. Get that damage control party working. Make some distance, then secure all, go to silent running, change depths and heading and try to hide. One sonar range is worth three stadimeter ranges. I have a healthy hatred of the stadimeter. I'm good at it but I'll never trust it before a sonar range or a Dick O'Kane attack. Sometimes it is and sometimes it isn't the sharpest knife in the pack. Always pick the sharpest knife in a fight. Always think, "Is this a good time to attack?" If they're all over you, it probably is.:arrgh!: