New just uploaded to AVSIM Library yesterday and is available now (filename logeditv1-0.zip). LogEdit is a logbook editor (P3D only) reads and displays the Logbook.bin file in your LM appData area and allows editing of the data, as well as a tool I created to combine two records into one: Just the time for those trips that get saved and reloaded mid-flight to manage VAS memory.  I composed this application in c# with Visual Studio so the code is "managed," NET 4.0 or later is targeted but I think it should work in the old NET 3.5 framework (feedback on this is appreciated).

Congrats and thanks on your gift to the community, but I have to ask the following:

 

Having come from a Novell network environment, we had TTS; Transaction Tracking Service, where if there was a crash during a "write to a record", the transaction was "wholly backed out" to the data state that existed prior to the crash, else if no crash, transactions were "wholly written". https://www.novell.com/documentation/nw65/stor_nss_lx_nw/data/bqq4w4r.html

 

 

To my knowledge, Logbook.log and logbook.bin had no such protections, and therefore if there was a crash, which y'all know was all too frequent, the logbook would, just as frequently get corrupted. While I can only find log records that date back 10 years, I've been using FS/P3d for over 30. That makes for one hell of a big log and shows, like real logs, a commitment to flying. It would be nice to not only recover that old data, but even more warm and fuzzy feeling to know that we could depend on our logs even if there was a crash.

 

Does your program handle transaction recovery?

 

Thanks again,

 

Chas

 

 

Does your program handle transaction recovery?

 

That is a very good suggestion.  Error correction is in my TODO list, as well as imports from FSX. As you point out, I should include error correction in the import methods.  Thanks.