SUBSIM Radio Room Forums - Call it luck or karma, or random computer coding, but don't call it skill

SUBSIM Radio Room Forums (https://www.subsim.com/radioroom/index.php)

- Silent Hunter 4: Wolves of the Pacific (https://www.subsim.com/radioroom/forumdisplay.php?f=202)

- - Call it luck or karma, or random computer coding, but don't call it skill (https://www.subsim.com/radioroom/showthread.php?t=167919)

Quote:

Originally Posted by Keelbuster (Post 1364293)

There is a weird thing where you have to click the send button twice - I saw this in a manual TDC video by Rockin Robbins. I'm not sure why you have to press it twice, or what the first send effect is, but for the computer to update the gyro, you need to press it twice.

:cool: Watch the arrows on the TDC dials. The first click sets the arrow indicating your topedo's gyro angle (in should match the "torpedo path" line on your attack map) ... the second click sets the impact point (and angle) on the target. (Or vice versa.)

The other issue mentioned about ships not sinking in shallow water is simple, they hit bottom before the deck crosses the waterline, so you won't sink them by flooding. However, you can sink them with damage points, just takes more torps or DG shells. The bad thing about harbor raping if water is too shallow you can waste a lot of torps making ships sink.

Again, if you have contacts on you can check your attack map and see the track of your torp directly to the target. If your target is stopped and your torp line isn't going through the target, you know you're off.

CAUTION:

If You Use The Estimation Tool For Target Course And Speed On The Speed Data Input Dial The Second Click Of The Range Input Will Goof That Up

Quote:

Originally Posted by Munchausen (Post 1364365)

Hm... ok - I think I know what you mean. But why would I ever want to do those two things separately? For a given solution, the gyro angle and the impact angle would mutually constrained, no? Why have them in separate steps? Would you ever _not_ press the button twice? I think maybe it has something to do with the issue mentioned by poster above - that if you are using the speed estimator, you need to take two ranges, a certain distance in time apart, and update with only one click, then press the timer button to estimate speed. Anyway, I never use this tool because a) I don't really understand under which circumstances it works and b) I've never received a speed estimate from it that was even close to correct.

Quote:

Originally Posted by Keelbuster (Post 1365480)

But why would I ever want to do those two things separately?

I don't know. Poorly written algorithm, perhaps.

Quote:

For a given solution, the gyro angle and the impact angle would mutually constrained, no?

Not exactly. It depends on your target's AOB and bearing. But the computer should be able to calculate both (gyro and impact) at the same time. What always frustrated me was, when sending data to the TDC, it also changed the target's AOB (as indicated above) ... messing up its course (if already set). I think the AOB mod fixed that ... but I can't guarantee it (I'm waiting for Duci to finish up 2.0 before going back to SH4).

for me in RFB2.0, I can drag the outer ring of the top right instrument in stadimeter mode (the mast height input) manually, which allows
a)manual mast height input and if the engine "can't see" the target
b)manual range estimate
into the tdc without using the actual stadimeter. no lock required.