Hi Howard,
Many thanks for your work on the Journal, it is very much appreciated.
I've done a little testing with the new live beta, and very much like what you've and your team have done. The status updates contain everything I
was hoping for when you broached the subject in our little discussion at the Expo. I would, however, still council that these be available via a a network
interface as writing this data to an SSD might life the device rather quickly.
However, this post is to point out that there is a little bug/feature of the current implementation that I would like to bring to your attention. I have
raised a
bug report, but the format for those doesn't really lend itself to what I getting the information over that I want.
The current implementation where the status update is only written when there is something worth reporting works very well (as I said above) and is
very much better than the heartbeat update cycle we talked over at the Expo (IIRC). However, the status is not being update if there is only a change
to the location. I found it quite easy to maintain a constant heading in the SRV which results in no status updates as I drive for kilometres.
I wouldn't want to see changes with very minor location deltas as this would flood the journal output, and I noted that the altitude does have some kind
of delta limiter. Something similar for the lat and long values would be appropriate. While driving around in an SRV I felt an update on a change to 3
decimal places was about right. In a fighter or ship that should be lower as the ground speed will be higher, and my guess would be some function of
altitude and/or speed would work best.
Hope this helps, and once again many thanks
Steve