1.3 /

[rdhiggins]

Per the patch it states that the player can now request a speed estimate on a target as long as he has recently sent at least two range+bearing data sets. Keep in mind that the estimate needs to be sent to the TDC to be taken into account for the shot.

I performed this within the Torpedo Attack training exercise. (#4) I raised the scope, determined everything except for speed and clicked on the TDC. I did this twice and then clicked on the ID Target button.

Afterwhich I receive cannot compute speed for the target.

Also I noticed when I try to click on the Radar (using my mouse to click the button on) that it does nothing.

Is the Training Excercises still broke? Does the patch not affect those?

Thanks!

[rdhiggins]

I noticed that the Radar did not work (or does nothing) when I click on the ON switch...... within a quick mission.

Is this possibly because of the year or sub?

[Anvart]

I noticed that the Radar did not work (or does nothing) when I click on the ON switch...... within a quick mission.

Is this possibly because of the year or sub?
:lol:

[minsc_tdp]

Regarding speed estimate, I heard someone say you might have to unlock/re-lock the periscope when sending the 2nd range/bearing data to TDC, then maybe the speed estimate will work? Please let us know

[AVGWarhawk]

I believe you need to have some time between each range and bearing reading.

[tedhealy]

Regarding speed estimate, I heard someone say you might have to unlock/re-lock the periscope when sending the 2nd range/bearing data to TDC, then maybe the speed estimate will work? Please let us know

You do not need to unlock/relock. Just send the bearing/range twice, then you can esitmate the speed. That estimate will vary wildly with how accurate your range and aob are, and the time between when you update the bearing/range it would seem. I've had speed estimates be off by over 30 knots.

Set up the target info and send bearing/range. Wait a good amount time, the more the better, send bearing/range again. Now you can use the speed estimate.

[John Channing]

And as long as your PK is running you do not even have to have the scope up.

This is a giant leap over the Sh3 system, or, as I like to think of it, the "HEY...HEY... I"M OVER HERE...SHOOT ME NOW" system of speed estimation.

JCC

[Inside686]

It works even if you keep the target locked BUT I noticed that when you lose contact with the target with the scope (you go under water) the measurements you did before are not kept in memory… strange since we send it to the tdc.
Anyway, those estimations help a lot when calculating a firing solution and you can check if the data (target's direction) you personally estimated are credible.

[Inside686]

That estimate will vary wildly with how accurate your range and aob are
Are you sure the AOB is taken into account for the speed calculation? IMO it's not.

[LukeFF]

Are you sure the AOB is taken into account for the speed calculation? IMO it's not.

It's not. AOB really only comes into play when setting the final gyro angle needed for the torpedoes. The speed estimation is simply plotting two marks on a map, calculating the distance between the two and how much time has elapsed between making those two marks.

[elanaiba]

It works even if you keep the target locked BUT I noticed that when you lose contact with the target with the scope (you go under water) the measurements you did before are not kept in memory… strange since we send it to the tdc.


The measurements are sent to the firing party, not the TDC. And they are not lost in the case you described.

[azn_132]

This is a giant leap over the Sh3 system, or, as I like to think of it, the "HEY...HEY... I"M OVER HERE...SHOOT ME NOW" system of speed estimation.

JCC

Ha I lik dat.

[LukeFF]

And as long as your PK is running you do not even have to have the scope up.

This is a giant leap over the Sh3 system, or, as I like to think of it, the "HEY...HEY... I"M OVER HERE...SHOOT ME NOW" system of speed estimation.

Yep, it's a lot better now. Now we no longer need to take the ship's length, divide by the square root of 5 (during daylight hours only), add 6, and then round off to the nearest whole number in order to get a proper speed estimate. :rotfl:

[Inside686]

It works even if you keep the target locked BUT I noticed that when you lose contact with the target with the scope (you go under water) the measurements you did before are not kept in memory… strange since we send it to the tdc.

The measurements are sent to the firing party, not the TDC. And they are not lost in the case you described.

Off course, but in the game to send the data to the firing party you have to send them to the TDC at the same time (with the red button)


I tried this two times:
-I took the range and sent it to the TDC
-Dropped the periscope for 20 seconds then rose it
-Took another range measurement and sent it again to the TDC.
So, I asked a speed estimation and the officer told me he hadn't enough data (such as if I did only ONE measurement and not TWO)

When I make the same procedure WITHOUT dropping the periscope, it works without any problem even unlocking the target between the two measurements.

[John Channing]

It works even if you keep the target locked BUT I noticed that when you lose contact with the target with the scope (you go under water) the measurements you did before are not kept in memory… strange since we send it to the tdc.

The measurements are sent to the firing party, not the TDC. And they are not lost in the case you described.

Off course, but in the game to send the data to the firing party you have to send them to the TDC at the same time (with the red button)


I tried this two times:
-I took the range and sent it to the TDC
-Dropped the periscope for 20 seconds then rose it
-Took another range measurement and sent it again to the TDC.
So, I asked a speed estimation and the officer told me he hadn't enough data (such as if I did only ONE measurement and not TWO)

When I make the same procedure WITHOUT dropping the periscope, it works without any problem even unlocking the target between the two measurements.

Do you have the PK running on the target?

JCC

[Inside686]

What do you mean by "PK" ?

[maerean_m]

I tried this two times:
-I took the range and sent it to the TDC
-Dropped the periscope for 20 seconds then rose it
-Took another range measurement and sent it again to the TDC.
So, I asked a speed estimation and the officer told me he hadn't enough data (such as if I did only ONE measurement and not TWO)

This is the way it's supposed to work. If it didn't, then it's a bug. I suspect/hope you didn't press the Send button correctly and the data was not actually sent.

PK means Position Keeper.

PS:PK should NOT be enabled, because it tracks the target (changing its known position) based on the last known speed. And the speed is unknown since that's what you're trying to determine.

PPS: 10 seconds is enough between the 2 range measurements in order to get an accurate speed estimation. 20 seconds is too much and the target may get away if it has enough speed.

[Inside686]

I had the position keeper disabled. what I understand about the position keeper is that it updates the AOB relatively to the speed, the initial range, the initial AOB and the initial position of the target in our scope. I've never used it yet but it could be useful (unless the target changes course or speed)




This is the way it's supposed to work. If it didn't, then it's a bug. I suspect/hope you didn't press the Send button correctly and the data was not actually sent.



It's what I thought initially and that's why I carefully tried a second time but I experienced the same behavior, I will try again this evening.