is it ok to compute a solution at long range then close in?

lostsm · 07-01-09, 08:06 PM

i was wondering if it's generally okay to compute a solution with (what i believe to be) accurate data that I can manually enter into the TDC while I have a target locked in my UZO/periscope, and then get in at a nice firing position

everytime I do this, I can see the TDC adjusting bearing and the gyroangle as our relative positions change, but the range always stays the same, in this case, a very long range. this always leads me to doubting my solution and then rushing at reaquiring solution data and often enough missing due to my last minute haste

so given 100% accurate TDC data, at say 8-10km away, and getting into a 90degree intercept position, keeping the target locked as often as possible, is the solution computed at 8+km still valid?

Alien1099 · 07-01-09, 08:14 PM

I'm no expert but I would think it would be valid as long as you calculated the exact time you needed to fire after taking into account the target's speed if it's moving along a very exact path (of course). I would not recommend moving ahead to close the distance yourself as that would probably throw the calculations off too much since you're not traveling at a constant speed and would require more math than it would be worth to account for it in my estimation. Get the target's vector then get into position and wait and fire when your calculations say you should. I'd just use the periscope though.

TigerShark808 · 07-01-09, 10:31 PM

I always have this problem with computing a target at long range then closing in and exspecting the same "NUMBERS" to work.
With me..I just continue to update my data.Its works better that way.

vorosgy · 07-02-09, 02:21 AM

As far as I know, only the AOB is updated automatically, but I think it's correct only if you're not moving, and the target is moving straight ahead. You've got to update the range manually.

However, skookum mentions an excellent intercept method during which you can safely ignore target range in this thread:
http://www.subsim.com/radioroom/showthread.php?t=151842
To make it short, IF the AOB and speed you enter is correct, and the gyroangle is 000, and the target's path is perpendicular to yours, then range does NOT matter.

Fincuan · 07-02-09, 04:34 AM

Quote:

Originally Posted by vorosgy

To make it short, IF the AOB and speed you enter is correct, and the gyroangle is 000 then range does NOT matter.

Fixed it for you. Regardless of your or the target's courses range does not matter if the gyroangle is zero.

vorosgy · 07-02-09, 04:51 AM

Quote:

Originally Posted by Fincuan

Fixed it for you. Regardless of your or the target's courses range does not matter if the gyroangle is zero.

Yes, you're right! I didn't think it through first... having perpendicular path is indeed not neccessary.

07-01-09, 08:06 PM	#1
lostsm Sailor man Join Date: May 2005 Posts: 47 Downloads: 2 Uploads: 0	is it ok to compute a solution at long range then close in? i was wondering if it's generally okay to compute a solution with (what i believe to be) accurate data that I can manually enter into the TDC while I have a target locked in my UZO/periscope, and then get in at a nice firing position everytime I do this, I can see the TDC adjusting bearing and the gyroangle as our relative positions change, but the range always stays the same, in this case, a very long range. this always leads me to doubting my solution and then rushing at reaquiring solution data and often enough missing due to my last minute haste so given 100% accurate TDC data, at say 8-10km away, and getting into a 90degree intercept position, keeping the target locked as often as possible, is the solution computed at 8+km still valid?

07-01-09, 10:31 PM	#3
TigerShark808 Engineer Join Date: Jun 2007 Location: 2074 nautical miles south west of San Francisco! Posts: 212 Downloads: 71 Uploads: 0	I always have this problem with computing a target at long range then closing in and exspecting the same "NUMBERS" to work. With me..I just continue to update my data.Its works better that way. __________________ GWX3GOLD OLC "Gold" MkIId SH3 Commander D.I.D 100% Realism ! SWCs-AtlanticReaper Skin <---because it is badass!

07-01-09, 08:14 PM	#2
Alien1099 Watch Join Date: Jun 2009 Posts: 23 Downloads: 16 Uploads: 0	I'm no expert but I would think it would be valid as long as you calculated the exact time you needed to fire after taking into account the target's speed if it's moving along a very exact path (of course). I would not recommend moving ahead to close the distance yourself as that would probably throw the calculations off too much since you're not traveling at a constant speed and would require more math than it would be worth to account for it in my estimation. Get the target's vector then get into position and wait and fire when your calculations say you should. I'd just use the periscope though.

07-02-09, 02:21 AM	#4
vorosgy Swabbie Join Date: Jun 2009 Location: Hungary Posts: 11 Downloads: 18 Uploads: 0	As far as I know, only the AOB is updated automatically, but I think it's correct only if you're not moving, and the target is moving straight ahead. You've got to update the range manually. However, skookum mentions an excellent intercept method during which you can safely ignore target range in this thread: http://www.subsim.com/radioroom/showthread.php?t=151842 To make it short, IF the AOB and speed you enter is correct, and the gyroangle is 000, and the target's path is perpendicular to yours, then range does NOT matter.