Gypsy Baron wrote:
There is a fatal flaw in the FSX logbook edit funtion that will corrupt your logbook.bin file
if you attempt to add or edit comments or other information on any record other than the very last one.
If the record length chages....a comment added or the length of the comment changes...you will
wind up with a corrupted logbook.
I have to mention a funny FSX trivia grin I get when I see that mentioned. Waaaaaay back when FSX first came out I started having issues with FSX spontaneously not wanting to start. Because it was still pretty new there wasn't a lot of help to be found in the dozen or so flight sim sites I visited on a daily basis. I didn't see anywhere that someone had mentioned having the issue, let alone having a solution for something not widely recognized yet as an FSX bugger. I ended up having to figure the problem out myself. It ended up being pretty easy for me to zero in on because of my over attention to keeping my MSFS logbook organized.
Everytime FSX would go corrupt, I would reload it at first and then after it kept happening, I started listing anything that I was doing that might cause the problem. It became obvious real quick, that the one thing in common with every flight just prior to the FSX not wanting to start, was that I had done extensive logbook editing. As a natural testing progression, I finally figured out that when FSX started freezing at the same point each time, that simply deleting the logbook.bin file cured the problem 100% of the time. As soon as I was convinced I had the answer to a problem that I didn't see anybody talking about yet, I posted the find and fix over at SimHQ. Lewis was one of the first ones to respond to my post and when I went back to check sometime later it, Lewis headed it up as a sticky over there. As far as I know that was the earliest posting about the FSX corrupt logbook problem & fix that I ever saw. There weren't any logbook editors or recovery programs back then that I knew of, so my only solution was to always keep a back up of my last good logbook as a replacement.
These days I use three logbook programs, four if you count the actual FSX default logbook.
I use the FSX default logbook strictly for keeping track of the total flight hours. It was either FS9 or FSX that I figured out keeps track of time internally over one decimal place deep. This creates "floating" flight time in programs that track at only one decimal place.
I use Lamont's logbook editor you mentioned as the only place that I ever edit an FSX logbook entry.
I use Vertigo's FSX Logbook Viewer to double check total aircraft hours and other trivia. This was the program that helped me figure out why if I totaled out the individual aircraft total hours that it sometimes didn't match the actual total logbook hours. The difference ended up being in the number of decimal points deep. It tracks at one deep and FSX is deeper.
I use my own logbook tracker to put all of the info together in the one place that I know it's sorted out as much as possible.
Here's a section showing the top ten all-times.
With this last ridiculous creation, I have every model of aircraft I've ever flown in MSFS and I can sort it by triva that's beyond trivial.
An interesting but really trivial trivia is that the very last aircraft slot that is usually on the bottom of the list, is a non-aircraft. It's the slot that belongs to the missing decimal point flight time that I mentioned above. This is the difference between what both the FSX default logbook and Vertigo's Logbook Viewer say is the total aircraft hours versus what the total time is if you add up the actual time of each individual aircraft total flight hours. Right now this is usually around .3 to .4 fight hours. It can change with each flight. It depends on those missing decimal points of flight time.
FAC
Login
Register
FAQ
Search
really sharp
