SUBSIM Radio Room Forums - View Single Post

Pisces · 01-19-24, 11:01 AM

Here is a bit of irony in your videos though. In this SH5 video about dead reckoning:

You use a table to get distance moved for 5 knots over 5 minutes. And say that you trust 'your dead reckoning' over that of the AI navigator. If you do the numbers in that table according to your 1.852 routine then you are clearly off from what the table gives you. So which method is right for the conversion?

771 meters divided by 5 minutes (300s) = 2.57 meters per second. Times 1.852 = 4.76 'knots'. Not 5 knots, which it should be!

Or for the larger value:
44415 meters over 45 minutes (2700 seconds)= 16.45 meters per second. Times 1.852 = 30.47 'knots'. Not 32 knots, which it should be!

See the contradiction?

In regards to the video itself. Yes, the plot of your boat on the map after the 5 minutes is off. But you also didn't move by exactly 5 knots. It shows you had 5.1 knots speed in the end. So naturally you are beyond your expectation. Also you eye-balled the time to be 12:16 when you stopped the time compression of 32x. So your reaction-time made you off by some part of a minute. With 32x time compression 1 minute zipps by in 2 seconds real time. Asside from the fact that you also let the game running at 1x speed while you explained what you were doing before showing the position. It may very well have a position error built in after you ask the navigator for a location. But there are other causes of error here too to explain it.

No, it's not due to the game itself, Silent Hunter 3, or 5 or Wolfpack. And it is NOT magic, or imaginary!. (referencing your latest car video) They are all calibrated to meters and seconds. It's operator error, that may or may not get lucky in circumstances. (Wolfpack did have a bit of time-slew with the stopwatch in the past. But that has been bugfixed years ago.

01-19-24, 11:01 AM	#21
Pisces Silent Hunter Join Date: Dec 2004 Location: AN9771 Posts: 4,892 Downloads: 302 Uploads: 0	Here is a bit of irony in your videos though. In this SH5 video about dead reckoning: You use a table to get distance moved for 5 knots over 5 minutes. And say that you trust 'your dead reckoning' over that of the AI navigator. If you do the numbers in that table according to your 1.852 routine then you are clearly off from what the table gives you. So which method is right for the conversion? 771 meters divided by 5 minutes (300s) = 2.57 meters per second. Times 1.852 = 4.76 'knots'. Not 5 knots, which it should be! Or for the larger value: 44415 meters over 45 minutes (2700 seconds)= 16.45 meters per second. Times 1.852 = 30.47 'knots'. Not 32 knots, which it should be! See the contradiction? In regards to the video itself. Yes, the plot of your boat on the map after the 5 minutes is off. But you also didn't move by exactly 5 knots. It shows you had 5.1 knots speed in the end. So naturally you are beyond your expectation. Also you eye-balled the time to be 12:16 when you stopped the time compression of 32x. So your reaction-time made you off by some part of a minute. With 32x time compression 1 minute zipps by in 2 seconds real time. Asside from the fact that you also let the game running at 1x speed while you explained what you were doing before showing the position. It may very well have a position error built in after you ask the navigator for a location. But there are other causes of error here too to explain it. No, it's not due to the game itself, Silent Hunter 3, or 5 or Wolfpack. And it is NOT magic, or imaginary!. (referencing your latest car video) They are all calibrated to meters and seconds. It's operator error, that may or may not get lucky in circumstances. (Wolfpack did have a bit of time-slew with the stopwatch in the past. But that has been bugfixed years ago. __________________ My site downloads: https://ricojansen.nl/downloads Last edited by Pisces; 01-19-24 at 11:39 AM.