Well, first of all the presence of the red lines from the Ship Centered Accuracy Fix shows that there is some degree of mod soup going on here. And RFB had a problem causing all torpedoes to miss at one time during the 1.5 version. That's a LukeFF question.

If RFB 1.52 is crashing, I'd say a game reinstall is necessary. Check out the stickied thread on that and get yourself a certified clean install going. Then try 1.52. I'll bet my bippy it works perfectly.

As far as targeting, everything you do is pretty bullet proof. The observation on the double-clicking send buttons is interesting, but my testing shows it won't make any difference to the torpedoes. The single click can cause the TDC output dials on the left side of the screen to lie to you about target AoB and torpedo gyro angle but the complete lack of any reports of misses due to single clicking points to an eye candy issue on the output dial.

If you pause the Dick O'Kane video right after I click the send button for the AoB you can clearly see that the output dial shows the wrong AoB until I click the second time. Evidence shows that although the dial shows wrong it lies.

I think Luke has the answer to your problem, but that you'll fix it with reinstall and RFB 1.52. That will remove the Ship Centered Accuracy Fix and put you back to using mastheads for range. All other things being equal the accuracy of your stadimeter range finding is directly proportional to the height of whatever target feature you're utilizing. That's why mastheads are best if they can be seen clearly enough. They are about twice as accurate as a cabin top or deck height.

Capn Scurvy has also corrected the database and that's why SCAF sometimes comes up with a better range than the stock game. It is astronomically better than reality however, and is the equivalent of equipping your World War II sub with Star Trek Enterprise sensors. Scurvy put an inhuman amount of work into the thing, it works magnificently, but there's not a speck of realism to be found there. If I get the Enterprise sensor array I want the photon torpedoes that come with it.:D Hey, I made those.:har:

Just had another thought. Are you sure you are using the correct version of RSRD?

I had a quick look at the two versions of RSRD.
The RFB version has ship silhouette files containing no red line.
Guess what? The TMO version has silhouettes containing the red line.

Double check which version of RSRD you are running.
I'm putting money on this being the cause of your problem.

Ok, I blew my entire old install away and did the following:

(1) Reinstall SH4 1.4 from the DVD.
(2) Reinstall SH4 1.5 update from the exe I bought online.
(3) Install the generic mod enabler v2.3.0.128
(4) Make a snapshot with the mod enabler.
(5) Use the mod enabler to install RFB 1.52.

After *only* the above, I still get enough CTDs to make the game unplayable. I'm not sure why. For example: if I load the game, then launch the 'Hunt for Wounded Bear' scenario from the game menus, it dumps me inside the sub - fine so far. But as soon as I push F5 to go to the bridge, boom, CTD every single time. It's 100% reproduceable for me.

It also happens a lot just trying to play campaign mode. I'll have spent a long time setting up an intercept, then as soon as I go to periscope view I'll CTD. I'm pretty sure it's due to RFB 1.52, because the stock game seems rock solid, and RFB 1.5 also seems solid. But 1.52 is a no-go for me.

However, I did notice that the red bars are indeed not there in RFB 1.52. But I'm about to remove it and re-install RFB 1.5 again, and I suspect the red bars will be there that way.

Anyway thanks for the help!

I'm using this one: RSRDC_RFBv15_V421.7z
+ this patch: RSRDC_V421_Patch2.7z
It's at least the version for RFB, but I'm not sure if it's 'right'...

That's the right one.
Damn - I was sure that was the problem.

As for the CTDs, when I was running RFB I found it was pretty unstable on my rig for a while.
Then I installed the latest Vista and DirectX updates and after that it was very stable.
Dunno if this helps.

I am running Vista, so I'll see what DX updates I can find. I should be current on the OS updates; it's a pretty brand new installation. Good idea to check that.

If they made a Linux version of SH4 I'd be on that, but I don't wager there's much chance of such a thing...

Hmm, I updated everything (OS, graphics drivers, DX) and nothing changed; 1.52 still crashes while 1.5 is OK. I think I'll just go with 1.5, since it seems to work OK for me. I'm still thinking my miss problems are due to a bad range estimation, but I'll have to play with it more to know for sure. The idea below of running one scenario with auto-map-updates on for comparison is a good one...

That's just bad luck mate.
Let us know how you get on with the range problem.

Arrrrrrrrrrrr! And a Jaunty Jackelope to you too!:arrgh!: