Some questions...

[Mersea]

1) Ok having to plot a course intercept for a convoy I get its speed, let's say 7 knots that is 200 Nm form the point of intercept, so I divide 200Nm by 7 knots that give me time 28 Hours~, the convoy should be there in 28 hours, but usually it apperas at 40 hours + or not at all? what is your method to calculate somewhat accuratly? an other time a slow convoy outpaced me as I was full speed? our courses was like a triangle minus the base...

2) What am I supposed to do without rudder?? (lost I presume) everything get fixed, but not the ruder, so I must terminate the career since nothing happens or solution sprovided.

3) For career there are subs to chose, what are models and differences? is it available in game?

4) Updated to latest ATI drivers (Vista 64 bits) but game is not stable as it was, my videocard is SAPPHIRE HD 4870 anyone with the same videocard?

Thanks :salute:

[WernherVonTrapp]

Your calculations for time are OK but the convoy or task force can change it's course. That leaves a lot to chance.
If your rudder is gone, you have to end your patrol in order to get it repaired.
I'll leave the sub-type explanations for somebody else. I don't have the time, at this moment, to type it out.
Regarding stability, what version of SHIV are you running?

[Slyguy3129]

The best way to follow a convoy is called shadowing. Meaning you are staying far enough away that they can't see you, but close enough that you can still barely see them.

This is my normal SOP when getting ready to attack a convoy.

#1: I have detected a large group on my hydrophones. I set my course to where the grpup is in and around 0(zero).

#2: I go to the nav map and mark the bearings in which the convoy takes. IE from 345 to 15. I put an X where my sub is, at 345 and at 15. Then I take the range tool ( the one the makes the circle) and draw out 10,000yds(5nms) as this is the range of detection give or take. Then I take the protractor and draw an angle throw the three Xs I have marked. Giving me a rough bearing and an angle. I take note of the angle.

#3: I surface and run at flank speed for 30 mins. The dive to periscope depth to take another reading. I adjust course again to keep them at 0(zero)

#4: Repeat step 2. Take note the new angle. Here I make a decision. Of the angle has gotten smaller they have moved further away and can out run me. If it is slightly larger then they are heading away but I am over taking them. If it is alot larger then they are heading towards me and I ahold prepare for contact.

Once I have visual contact I make a run at periscope depth towards the convoy to get a firing solution. Course and speed. Once I have those I mark a relative course on the map and head away from the convoy to do and end around.

Once I am far enough away I surface turn to a relative parallel course and make flank speed. All the while making sure I can still see them. Once I get to where I feel I can make an attack run, normally once it's dark. I turn 90 into them at flank. I run till a am close enough that I can dive and still get in range (this might require speed changes as the faster you go te easier you are to see as you are crossing the escorts bow), then I dive to PD and wait.

I may or may not recheck my solution, often times I do.

And that's normally what I do in a nut shell, but it's really all about what makes it easy for you. I hate math therefore I use the NAV tools given by the game. But whatever suits you.

Good luck Captain! :salute:

[I'm goin' down]

You can expect a convoy or TF to change course. This make intercepting a long distance difficult to plot. However, if you want to know where they would be and how to intercept had their courses remained constant, download aaronblood's masterpiece, Mobo, from the Mobo forum. Read the tutorial. It is a fantastic program and simulates a naval manuevering board. You can plot courses, intercept points, etc. on a Nav Map, and it is simple to access the program during a mission.

[Platapus]

#3: I surface and run at flank speed for 30 mins. The dive to periscope depth to take another reading. I adjust course again to keep them at 0(zero)




Why do you dive to PD to take an observation? If you have been successfully shadowing the convoy on the surface, why submerge?

Or are you talking about shadowing the convoy out of visual range and then darting in every 30 minutes into visual range (where it would be a good idea to submerge)

[Mersea]

Thanks guys for the quick replies, I checked plot via radar and yes sometimes there is deviation, but it is very linear; and for convoy speed they end always slower than computed by myself, but it is surely current and wind, I guess SH4 computes them since with the sub speed vary at a know rate speed eg Normal.

I shall give a check about MOBO plotting prog too.

Will check for rudder to end myself the mission and see what it does.

Graphics are ok again, I disabled "real sound" dunno what it is exactly, but it said disabled it would eat less ressources.

Found on the forum different subs specs.
:up:

[I'm goin' down]

If the rudder is gone, which you can check with the camera, you cannot steer. The mission is over.

Mobo. It involves copying the Nav Map, which is quite easy to do. For example, if you see a TF on the Nav Map at a range for 200 nm by way of example, when you transpose it to Mobo you can plot an intercept based upon your speed and course and the TF estimate speed and course. If you spot the TF near Japan when you are near Midway, Mobo will tell you that it cannot plot an intercept at any speed (you are too far away.) If you are within intercept range, Mobo will tell you the speed and course for the intercept.

You can also plot the intercept points when it is close enough that you have determined the TF's true speed and course.

That is only a portion of what Mobo does. It is really a phenomenal program and is worth learning just to fathom the mind of aaronblood, which is somewhere in outer space.