![]() |
I pretty much follow the excellent example in RR video tutorial "Dick O'kane" attack, which is an attack from 90 degrees of target course with a lead of 10 to 15 degrees. So I shoot BEFORE the target crosses 0 degrees relative this gives the warhead a slight angle on impact, duds are few.
I never switch on the PK and never look at the attack map, I shoot, lower scope and get the heck out of dodge, while listening for impact explosions of course. I never worry about my solution. Its always right on. The only variable and the biggest problem is if the target maneuvers once it sees your fish. But if you loosed a nice salvo your spread will probably make up for that anyway. Another great aspect with this method is that you can put fish on target where you want them. Take most IJN cruisers for example, if you hit them just aft of the deck gun(just forward of the bridge) she will light up like a Roman candle, I think this is where powder bags were stored probably. |
Well, the point was really what would happen if you tried those attacks with RFB. I tried those attacks with stock, and you're right; they work like a charm. With RFB however, I can guarantee, from my own experience, at least a 75% dud rate. Fire 4 fish and expect 3 to go dud, sometimes all 4.
To avoid the issue, I'd advise a 75deg angle. Usually a good way to accomplish this is firing as the target is at bearing 0 / 180 (assuming you steered the sub on a 90deg angle to target course). Take you're final readings at that point and fire. |
I rarely if ever shoot 90 AOB at impact.
in RL it was discovered about the firing pin as some or most of you know. According to Lockwood the order went out almost immediately to stop shooting perpendicular shots. further though a longtitudinal shot causes greater damage in a magnetic shot. I play RFB + RSRDC most days. *note; when playing full up I enjoy relatively few duds. M |
I am totally onboard with what you are saying.
Please let me clarify. I am currently running the lastest 1.5 with RFB and RSRDC, which I did not state before. If you have seen RR's tutorial you would understand what I am saying and doing with the Dick O Kane method. Either that or I do not fully understand what you are trying to explain to me. Here is my attack process: Target: Course: North Speed: 12 Knots I am approaching the target track from the east (relative to target) heading 270 at 2000 yards off the target Starboard Bow, I am at PD using my sonarmen to mark bearing of target. Through the scope I line up my bearing to 350 degrees, on the TDC I enter the target speed, bring up range and minimize with the outer circle range setting and double click, this sets bearing to target in the TDC to 350 degrees. I then bring up the AOB tool on the TDC. I set AOB to 80 degrees STBD and double click to input the data. This is due to the fact that when I fire at 350 ( the ship crosses my vertical line in the scope reticle ) the AOB to target will be 80 STBD. This is because I know that my heading is exactly 90 degrees to target track. The zero bearing relative is 270 true nort. If I fired at 0 bearing relative I would set AOB to 90. Firing at 0 would probably also result in an angled strike but I prefer to lead the target minimizing gyro resolver error and still giving a slight angle on impact. This angle may change due to the range and speed of target. You can use the data disaplyed by the TDC after you have entered your solution data to view this angle and adjust as needed. Set AOB, double click, adjust your scope bearing, go to the range tool and double click. If you change any data remember to update bearing by double clicking the range tool. Using this method I have very few dud strikes, from hundreds of shots. This is by no means my method. I simply watched and learned. It has enabled me to truly immerse myself in the game at 100% realsim and still get some good tonnage. |
Seems like text book O'Kane to me, I imagine everyone using the method executes it like that.
Thing is you're leading the target by 10deg; by the time the torpedoes reach the target it will be crossing at bearing 0 / 90 AOB, meaning the fish will strike the target at near 90deg (give or take a couple of degrees). That is exactly what is causing the issue. Yet you don't experience much duds, where I would be lucky to get a detonation, even at slightly more glancing angles. :hmm: Maybe it's down to the combination of mods? [NSM + PE + RFB + RSRD] @100% realism (http://i268.photobucket.com/albums/j...untitled-1.jpg) |
Hi there! Sure has been fun reading all this. I've been off learning RFB. One thing I noticed is that on the attack screen your estimated torpedo track line is missing. That's bad, because I always look at the angle it strikes the track. If it is close to 90º, I'll increase my lead angle to shoot 10º earlier. That way I hit the target from 10º forward of the beam instead of at right angles.
In my Dick O'Kane tutorial I calculated to hit the target on almost a perfect right angle, guaranteed dud heaven if you are in the middle of 1943 or before playing RFB. Instead of shooting at 350º I'd back up to 340º to have that 10º difference from a 90º hit. Now, why wouldn't I go forward 10º and shoot at the zero bearing with an AoB of 90º? It has to do with the duration of the torpedo run. While the target is approaching, his speed subtracts from the time of torpedo run, giving him less time to maneuver. If you shoot from behind, his speed adds time to the torpedo run, making it easier for him to avoid. Hate to sound like an encyclopedia, but I have spent an altogether unhealthy time working all this stuff out with practice runs, stop watches and everything. Both ways work pretty well, but I'd rather shoot earlier than later.:arrgh!: |
Agreed, better sooner then later. ;)
Unfortunately, all this got me thinking. :lol: If you don't fire your fish at 0deg gyro angle, you lose some accuracy with the O'Kane attack, correct? Could this be corrected by taking a quick range reading just before firing? This leads me to the first targeting method I developed before I "mastered" (cough) using the position keeper; I would observe the target over a lengthy period of time, allowing to draw / plot an accurate prediction of his course on the map. Based on that I would predict the targets position at a certain point, and use the map tools to gather the data. Drawback is that the sub has to be stationary for this to work. 1. speed; easy enough: mark, time 3 minutes, mark again and measure distance traveled, calculate speed. 2. AOB; mark a position along the predicted targets course, use protractor to measure bearing to that point. Say the predicted point is 15deg starboard, then AOB would be 75deg port (assuming you steered a perpendicular course to target's course). 3. bearing and range; using the measurement in step 2, you know the bearing is 15deg. Range can be measured by taking a ruler and measuring the distance from the sub to the "predicted position" mark. Point the scope at 15deg and use the dial to input the measured range. Then wait for the target to pass in view and fire as the desired point is in the crosshair. Basically all that is, is an O'Kane attack + a range reading. The range reading allows greater freedom when it comes to firing at a specific bearing and controlling at what angle the torpedo strikes the target, without sacrificing accuracy. Also, for the bearing and range you can use the sonar. Point it at desired bearing, send bearing, take range with ping as target moves onto that bearing, send range and fire. Another possibility is to activate the position keeper as the desired target point is in the crosshair. Now you're locked on to that specific point and you can delay firing as long as you want (given that data was accurate). I think even just a quick ping for range when using the O'Kane attack can increase accuracy, especially when firing at anything but 0deg gyro angle.:hmm: (sorry for the long version, like I said, I started thinking. :-? ) |
All times are GMT -5. The time now is 09:44 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.