February 2, 201412 yr I am having problems with the Logbook in the Pilot Records of FSX. Originally the Task Manager would show FSX not responding when I tried to start it. So on a guess I deleted the logbook.bin file. That started in April 2013 and happened two or three times since then. What is happening now is a problem with what is written to the logbook.bin. and what I not written to the logbook.bin. Several examples: (1) EDDF-KLAX fight of 12.5 hours showed 12.1 hours of instrument flight. KSRQ-KTPA flight of .5 hours showed instrument time of .4 hours (these are obviously wrong). (2) Flight times do not write to the logbook.bin. When I finish a flight, I press the Esc key and the Free Flight screen comes up and then I click on Pilot Records to look at the Logbook. Sometimes when I press the Esc key FSX just disappears with nothing written to the Logbook. (3) The Logbook will hold no more than seven flights at a time. After that it can no longer be written too. After each of these occurrences I delete the logbook.bin file and let FSX build a new one. I have even deleted GrantedRewards.bin. These steps make no difference. I am beginning to think that FSX creates a corrupted logbook.bin file when it build a new one. Or what ever writes to the logbook.bin file is sending incorrect information to the file. Any ideas? Thank you Michael Cubine Michael Cubine
February 2, 201412 yr Have you tried the FSX Logbook Recovery v1.1 program in the AVSIM Library? It will analyze the logbook for corruption and fix it. Better than deleting it. My logbook goes back to April 2006. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
February 2, 201412 yr Author Have you tried the FSX Logbook Recovery v1.1 program in the AVSIM Library? It will analyze the logbook for corruption and fix it. Better than deleting it. My logbook goes back to April 2006.Jim Young Attached is a screenshot of the results of running FSXLog.exe. It indicates that logbook.bin is not corrupted. Since I made the original post last night, I did a flight KMEM-KOAK which it recorded as a 77LR of 4.3 hrs of which 4.0 hrs were instrument flight. This is simply not right. The plane was a 777 Freighter and I was in the clouds for maybe the first 10-15000 feet. Maybe what records and writes to the logbook.bin is messed up. Thank you Michael Cubine Michael Cubine
February 3, 201412 yr I am having problems with the Logbook in the Pilot Records of FSX. Originally the Task Manager would show FSX not responding when I tried to start it. So on a guess I deleted the logbook.bin file. That started in April 2013 and happened two or three times since then. What is happening now is a problem with what is written to the logbook.bin. and what I not written to the logbook.bin. Several examples: (1) EDDF-KLAX fight of 12.5 hours showed 12.1 hours of instrument flight. KSRQ-KTPA flight of .5 hours showed instrument time of .4 hours (these are obviously wrong). (2) Flight times do not write to the logbook.bin. When I finish a flight, I press the Esc key and the Free Flight screen comes up and then I click on Pilot Records to look at the Logbook. Sometimes when I press the Esc key FSX just disappears with nothing written to the Logbook. (3) The Logbook will hold no more than seven flights at a time. After that it can no longer be written too. After each of these occurrences I delete the logbook.bin file and let FSX build a new one. I have even deleted GrantedRewards.bin. These steps make no difference. I am beginning to think that FSX creates a corrupted logbook.bin file when it build a new one. Or what ever writes to the logbook.bin file is sending incorrect information to the file. Any ideas? Thank you Michael Cubine Hi Michael, I found that I had issues with flights not being recorded in the logbook when I pressed the ESC key as well. I now click on "end flight" in the menu tab, and then just click on the X on the main screen to exit out. I no longer have flight times not being recorded in the logbook by using this method. Bill
February 3, 201412 yr Author Hi Michael, I found that I had issues with flights not being recorded in the logbook when I pressed the ESC key as well. I now click on "end flight" in the menu tab, and then just click on the X on the main screen to exit out. I no longer have flight times not being recorded in the logbook by using this method. Bill Bill A couple of days ago I started right clicking on the screen and left clicking on menu bar and then clicking on end flight rather than pressing the Esc key. This cover of last three flights and they were recorded in the Logbook. However, I still have the issue where the flights are not recorded properly. The last flight I did was KTPA-KATL. Logbook shows flight time of 1.5 hours and instrument flight time of 1.2 hours. The sky was essentiallly clear with some scatter clouds at 10000 feet. Certainly not instrument conditions. Anyway, I deleted logbook.bin again and now I am doing EDDF-KIAH. I will see how that turns out. Thank you Michael Cubine Michael Cubine
February 3, 201412 yr Author Still writing the wrong data to the Logbook. EDDF-KIAH flight time was 11.9 and instrument time was 11.6, It seems as if instrument and non-instrument time are reversed. 11.9 and .3 would make a lot more sense than what was written to the Logbook. Michael Cubine Michael Cubine
February 4, 201412 yr Author The problem with the wrong data being written to logbook.bin appears to have been caused by a ASN beta release I had installed. The instrument and non-instrument time is being recorded correctly now. Michael Cubine Michael Cubine
February 11, 201412 yr Author I thought this problem was solved but not so. Right now, no more than four consective flights can be written to logbook.bin. Flight five onward disappear into thin air when I end the flight and exit FSX per Bill's suggestion above. Thank you Michael Cubine Michael Cubine
February 14, 201412 yr I thought this problem was solved but not so. Right now, no more than four consective flights can be written to logbook.bin. Flight five onward disappear into thin air when I end the flight and exit FSX per Bill's suggestion above. Thank you Michael Cubine Hi Michael, Sorry for taking so long to reply back to your earlier post. I fly the A2A B17 all the time, and I always seem to have instrument time recorded in the logbook after each flight. No idea why it does that. I don't have any issues with the flights being written to the logbook though. I have been using the same logbook file for a long time copying it into new installs etc.. Do you do any manual editing of the logbook? I seem to recall reading somewhere that it can screw up the logbook if you add or delete entries. Bill
February 14, 201412 yr Author Do you do any manual editing of the logbook? I seem to recall reading somewhere that it can screw up the logbook if you add or delete entries. Thanks for the reply. No, I have never edited the Logbook. I fly the A2A B17 all the time, and I always seem to have instrument time recorded in the logbook after each flight. No idea why it does that. I did a KJFK-KLAX flight last night and the Logbook showed 5.5 hours of flight time and 5.2 hours of instrument time. Looks like it some how reversed the time. It was certainly 5.2 non-instrument and .3 hours instrument. Michael Cubine Michael Cubine
Create an account or sign in to comment