|
|
Post by dougphresh on May 16, 2019 8:08:19 GMT -6
I cannot make heads or tails of air spotting for the life of me. I'm receiving reports at different times simultaneously! Geographically, I end up looking at a blue cloud of reports even during a short exercise in good weather.   |
|
|
|
Post by akosjaccik on May 16, 2019 8:12:48 GMT -6
Problem is, the timestamps are "somewhat" problematic. I wanted to make a proposal for an option of "decaying" or making flags more and more opaque (and finally deleting maybe) once the elapsed time reaches a certain threshold from a given sighting time; but I have yet to write a correct post all about this.
Maybe it would be also lovely if the player would be able to place very basic markers on the map on his own.
|
|
|
|
Post by noshurviverse on May 16, 2019 8:35:53 GMT -6
I'm almost certain that's intentional and in fact alot more accurate than most commanders had access to. Remember that a pilot relaying a spotting report would be looking at something from miles away, while also most likely not being certain of his exact location and distance from his own forces. It looks that those spots are relatively consistent, the largest difference being 18 miles.
A real life example of this was at Midway. The floatplane scout that spotted the American carrier fleet reported it, but failed to specify what the ships actually were. About half an hour later that scout reported the presence of a single American carrier. But in actually, there were three. Even worse, his reporting of the position of the carriers was off by 60 miles! As a result, the Japanese fleet was under the impression they were out of range of the Americans, when the opposite was true.
|
|
|
|
Post by dougphresh on May 16, 2019 9:01:55 GMT -6
I understand variation in space, but variation in time is baffling. It's hard to track the data in my imaginary CIC if I can't plot out when ships were spotted to predict any kind of movement through space.
|
|
|
|
Post by akosjaccik on May 16, 2019 9:03:02 GMT -6
I'm almost certain that's intentional and in fact alot more accurate than most commanders had access to. Remember that a pilot relaying a spotting report would be looking at something from miles away, while also most likely not being certain of his exact location and distance from his own forces. It looks that those spots are relatively consistent, the largest difference being 18 miles. A real life example of this was at Midway. The floatplane scout that spotted the American carrier fleet reported it, but failed to specify what the ships actually were. About half an hour later that scout reported the presence of a single American carrier. But in actually, there were three. Even worse, his reporting of the position of the carriers was off by 60 miles! As a result, the Japanese fleet was under the impression they were out of range of the Americans, when the opposite was true. I am not addressing the inaccuracy of reports which is, of course, most welcome. I am thinking about the most possibly bugged timestamps (unless all recon planes took off without a battery in their alarm clock:) ) and the fact that a player most likely wouldn-t care about a report from six hours earlier, regardless of accuracy, so irrelevant information does not build up a forest of little flags. |
|
|
|
Post by noshurviverse on May 16, 2019 9:22:14 GMT -6
I am not addressing the inaccuracy of reports which is, of course, most welcome. I am thinking about the most possibly bugged timestamps (unless all recon planes took off without a battery in their alarm clock:) ) and the fact that a player most likely wouldn-t care about a report from six hours earlier, regardless of accuracy, so irrelevant information does not build up a forest of little flags. Removing old contacts would of course be welcome. Iffy timestamps could possibly be justified as representing the delay in a report being sent, received by the fleet's radio operators before finally being passed up to the "commander", the player. To go back to Midway, supposedly it took 20 minutes from the time the scout reported his findings for the information to reach the Japanese commander. |
|
|
|
Post by williammiller on May 16, 2019 9:26:09 GMT -6
I am not addressing the inaccuracy of reports which is, of course, most welcome. I am thinking about the most possibly bugged timestamps (unless all recon planes took off without a battery in their alarm clock:) ) and the fact that a player most likely wouldn-t care about a report from six hours earlier, regardless of accuracy, so irrelevant information does not build up a forest of little flags. Removing old contacts would of course be welcome. Iffy timestamps could possibly be justified as representing the delay in a report being sent, received by the fleet's radio operators before finally being passed up to the "commander", the player. To go back to Midway, supposedly it took 20 minutes from the time the scout reported his findings for the information to reach the Japanese commander. Hummm...I had thought we had an option included to "Do not show spotting reports older than [X] hours", but it might not have made it in yet...I will check just in case that is a bug. |
|
|
|
Post by tortugapower on May 16, 2019 11:33:27 GMT -6
Problem is, the timestamps are "somewhat" problematic. I wanted to make a proposal for an option of "decaying" or making flags more and more opaque (and finally deleting maybe) once the elapsed time reaches a certain threshold from a given sighting time; but I have yet to write a correct post all about this. Maybe it would be also lovely if the player would be able to place very basic markers on the map on his own. I like everything about the suggestions here. - a possibility to fade older report flags, something like 40% transparency for reports over an hour old - the ability to place player markers on the map |
|
