http://www.subsim.com/radioroom/pict...pictureid=1708

CRASH! right?

Holy cow! I'm in port waiting for the new patch to be released, so in the mean time, I've been fooling around with the single missions. I tried the one where you need to engage the Japanese bombardment force that just attacked Henderson Field. I believe the boat is Flying Fish, a Gato class. It's Nov.42'.

My boat is heading East when contact is made. I spot a line of cruisers and Battleships bearing 350. A quick reference of my AOB/ course finder tells me they're heading 220. Just a note, in the mission description the Task Force is supposed to be heading towards the Shortland Isl. These ships are heading the opposite direction. Anyhow, after I id one of the targets, I calculate speed at 28knts. I set up for a DO style attack. I prepare the forward tubes keeping the torpedo depth shallow to compensate for the faulty depth keeping at this point in the war.

Everything is set, as the lead Cruiser sails into the crosshairs. I fire 3 shots, and quickly go to external to view my handiwork. Every torpedo malfunctioned! I'm not talking about being duds, I'm talking about going way off course! I ready the next 3 tubes for the next target. Same thing!! Every torpedo went wildly off course. All I could do at this point is dive and break off the attack:wah: Talk about frustrating!

Hehe! Wait until the patch is released, it will get even worse. I have been testing the latest patch with a new career and at one occasion I had 8 fishes go dud on me when I engaged a single merchant. Tonnage sunk will go down in the early years, as it should be.

Shots at less than 45° angle and slow speed settings here we come. :)

Yeah, I read what Luke wrote awhile back about that. I'll definitly be pulling out what little hair I have left!

Hmmmm actually it was the opposite (In the 45º angle)

IIRC, it was found out during trials that the problem lied in that the torpedoes went deeper than expected (Not triggering the fuse) and when set shallower they magnetic fuse made them explode way too soon before reaching the target. Then, when shooting at right angles and high speed, the contact fuse actually got such a big hit that it bent and didn't trigger the explosive. Hence the better results with angled track and slow speed.

Anyway, looks like we are going to suffer a lot of frustration :D

Maybe I got it wrong...

Quoting LukeFF here:

Yes I did. :) Near the 45° track, not less than. :damn:

Ah, now I see what you mean. Yes, we were both actually saying the same thing, only I understood 45º or less as closer to 90º, instead of a "smaller" value in absolute terms :hmmm:

Glad we understand each other. :)

Picture is worth a 1000 words, and I believe this will be direly needed for early war RFB patrols now:


http://img121.imageshack.us/img121/4...ltargeting.jpg

(Picture credit goes to Rockin Robbins IIRC)

Sorry for the double post, but this is related with the new RFB2 VISUAL SENSORS REWORK 1.0 by Hitman.

After playing with the mod on 3 or 4 patrols, I have to say it indeed does work far better in campaign mode. Every time I went on the bridge to see the contact in question I could see what my crew reported. Night spotting does seem to work on longer ranges in campaign mode compared to single missions. The crew doesn't have eagle eyes any more.

Nice work and thanks for improving the RFB experience for us. :up:

Hello

Is there any environment mod recommended to use with RFB? I want to get rid of the yellowing dirty ocean.

Thanks!
G

Yep, you got it. :) Hits at or near 90 degrees with the Mark 14 set to high speed will always result in a dud, until they are fixed at the end of September 1943.

@Fish40: you don't need to worry about depth-keeping problems with the Mark 14 after August 1942. From that point forward the Mark 14 will run to within 3 feet of its set depth.

I've got another update on that problem I was having with the aircraft before. After reinstalling and applying RFB, the March 6 patch, RSRD and its patch, I played a couple patrols, without issue (other than getting sunk while hotdogging it when I should've been slinking away quiet like).

So I slapped on the Sub Watch Sensors + Scene 1.0 patch, and took out another start of the war patrol. Five iterations of aircraft being spotted... the first four went well. I immediately ordered a crash dive. Once the sub was under, I'd order 200' or deeper. A couple times the aircraft never attacked... the other two, DCs were dropped, but they missed me by quite a bit.

That fifth time? I ordered a crash dive, and just after I jump to the control room, I hear the high pitched whine of an aircraft engine as it dives down. It dropped bombs, which must've straddled me... four center compartments taking on water, and I never recovered.

I can't say why the first four went fine, while my lookouts never gave me time on the fifth. They were at their stations... I was at the nav map... 128x TC. SH4 shouldn't be stressing my system at that TC (Core i7 860 w/ 4 GB RAM).

If I can survive to get SD radar, or if I simply start later in the war, it'd be a non-issue...

The realistic side of me wants to say "Welcome to the real world"... there had to be watch crew that missed spotting an aircraft in time. The "I have to start another career over *again*!" side of me wants to ditch the patch. *shrug*

Glad you like it, it is certainly disturbing and makes it difficult to work with, that the sensors seems to work slightly different in campaign mode. My rough guess is that it has something to do with crew experience/efficiency. Probably, since RFB modifies the crew roster and abilities in campaign mode but doesn't touch the single missions (AFAIK), this could explain the different results.

This and other mods for v. 1.5 need to be moved to the SH4 ATO mods area as v.1.5 is only for the U-boat missions pack