10-28-15, 10:35 PM
|
#5
|
Silent Hunter 
Join Date: Sep 2010
Posts: 3,975
Downloads: 153
Uploads: 11
|
Quote:
Originally Posted by Rockin Robbins
[/INDENT]The ideal way to fix the problem would be to have a scalable error envelope for each observation method ....
Too bad we can't do anything about the first part, data acquisition and measurement errors.
|
Yes, this would be very desirable.
The errors could be incorporated before the contacts were plotted. We could have the choice as to whether to accept the plot at face value, or adjust it ourselves according to our own judgment.
Quote:
Originally Posted by Barkerov
It would not be a difficult calculation to have random errors different for each mode of detection. All you need is the variance of each method and a random number generator.
What I would like to see over and above what you said is the error reduce as the target is observed for longer. So if you shadow it from a distance for a few hours even with visuals only you can get a much better idea of the course and speed.
|
The problem is less one of mathematics, than software design. We can do the math, but lack any way to fix the code. I was also thinking about the number of observations, and such. Believe me, if I had a way to put this in the game, I would.
I think the best we can do, with the game as it is, would be to craft a house rule, using a table to factor in the most important factors affecting our approach. These being RADAR, no. of observations, visibility (day or night), skill level (skipper or crew).
|
|
|