Darn, Not even 10 hours logged and already FSX's logbook has messed up the file. Unfortunately, (unlike FS9's 'simpler' logbook)it no longer asks on exit if you would like the entry saved into the logbook or just discarded. Now you have to go in and hand delete any entry you don't want in there. Thanks to tweaking, have taken at least 4-5 short flights to see tweak results and would delete the logbook entry before leaving FSX.However it seems as 1 of those times FSX did something bad to the file as now any flights get saved into log, but aren't shown in the logbook when inside of FSX. :( (ie file is now corrupt)If started after one such tweak flight when an entry wouldn't delete after clicking on the button several times. I left FSX and came back in and it was gone, so I assumed(oppps) that everything was fine. Now next tweak flight it came up with a corrupted description. Granted it was only 1 character was bad, but certainly could throw the rest of the file off. I can delete this bad entry, but even after it gone Logbook won't show the next entry in the file even though it appears to be there. My guess is it missing some beginning data that the logbook is looking for.Anyone else have this happen yet?Haven't looked at the SDK's, but I don't imagine there is a different logbook editor in there? All the fields can't be edited inside FSX.I guess this is fodder for "[email protected]", but wanted to check and see if anyone else had run across this too.

I have made at least three posts about the logbook and also written to tell MS email about it.The logbook is really bad, Its not editable, I have several flights where it did not fill in the departure airport, and as you say if you start FSX to slew around or run tests the log book gets updated with hours that do not belong there, and I have to go back and delete them. The actual logbook file is also in binary format and cannot be edited.I would also like a way to import my other logbook as I have kept a running log ever since the beginning, or if not be able to export the FSX log.A fix before the FSX DX10 update would be nice. Wishful thinking I know but its worth a try . :-)Bill

Hmm, Missed your earlier posts. Though with the forum shuffles and how busy its been, its been tough keeping up on threads.On my 3rd flight it did that too me too, it left out depature airport. Since there is no way to edit it back in, I just put it in the comments. I'm guessing not everything is editable so 'we' can't edit our way to rewards and certifcates.So if this is a wider spread problem, looks like I will have to backup logbook before every flight and rename it so that its out of the way for tweaking. Its a shame its so messed up as it has more abilities this time around.There is a KDLH to KDTW flight in file that is not being displayed. Last flight shown was a Tweak session. Even if I delete it, newest flight wont show. So going to have to start over with a new file. Sigh.

Don't know how long it's been messed up but my logbook is way wrong. I have entries from 2005!I had several hangs of FSX (old video driver) when I first started it up. Now there are duplicate entries, etc. Do not have half of the flights listed either. The rewards stuff looks ok.

>I have made at least three posts about the logbook and also>written to tell MS email about it.>>The logbook is really bad, Its not editable, I have several>flights where it did not fill in the departure airport, and as>you say if you start FSX to slew around or run tests the log>book gets updated with hours that do not belong there, and I>have to go back and delete them. The actual logbook file is>also in binary format and cannot be edited.>>I would also like a way to import my other logbook as I have>kept a running log ever since the beginning, or if not be able>to export the FSX log.>>A fix before the FSX DX10 update would be nice. Wishful>thinking I know but its worth a try . :-)>>Bill> Bill, you can edit the file with a HEX editor, as I have done. I've started analyzing the format and know how to add/delete/modify departure and destination airports and the initial time/date. I think I've ID'd the "type" byte..multi engine, etc but don't have enough samples to know al the code assignments. Anyhow, what I found that was PORKING my logbook.BIN and causing FSX to hang on the splashscreen was an incorrect "length" byte, telling FSX how many bytes are in the current record and thus a pointer to the next record. Each record starts with a "05" byte followed immediately by the length byte. Adding that hex value to the address of the first "05" byte should put you at the next "05" byte and so on. Something caused the length byte of my 3rd from last log entry to be incorrect. Once I corrected that byte my logbook was restored. Paul ... this is not for the faint of heart, but if you backup, it shouldn't be much of a problem to "dig around"... :)

>>I have made at least three posts about the logbook and also>>written to tell MS email about it.>>>>The logbook is really bad, Its not editable, I have several>>flights where it did not fill in the departure airport, and>as>>you say if you start FSX to slew around or run tests the log>>book gets updated with hours that do not belong there, and I>>have to go back and delete them. The actual logbook file is>>also in binary format and cannot be edited.>>>>I would also like a way to import my other logbook as I have>>kept a running log ever since the beginning, or if not be>able>>to export the FSX log.>>>>A fix before the FSX DX10 update would be nice. Wishful>>thinking I know but its worth a try . :-)>>>>Bill>>> Bill, you can edit the file with a HEX editor, as I have>done.> I've started analyzing the format and know how to>add/delete/modify> departure and destination airports and the initial>time/date.>> I think I've ID'd the "type" byte..multi engine, etc but>don't> have enough samples to know al the code assignments.>> Anyhow, what I found that was PORKING my logbook.BIN and > causing FSX to hang on the splashscreen was an incorrect > "length" byte, telling FSX how many bytes are in the current> record and thus a pointer to the next record.> Each record starts with a "05" byte followed immediately by> the length byte. Adding that hex value to the address of the>> first "05" byte should put you at the next "05" byte and so>on.>> Something caused the length byte of my 3rd from last log>entry> to be incorrect. Once I corrected that byte my logbook was>restored.>> Paul ... this is not for the faint of heart, but if you>backup,> it shouldn't be much of a problem to "dig>around"... :)>>Sorry or the delay in responding but I was out of town on some R&R...I guess I could use a HEX ed as you suggest, I just think MS should have done a better job with it. :-)Thanks Bill

What hex editor would you recommend.

>What hex editor would you recommend.Can't recommend any particular hex editor. The one Iuse is freeware that I D/L'd a long time ago and thesite no longer seems to be up.Just do a google search and you should find several,I suspect.As long as it displays the ASCII character equivalentsin a panel beside the hex values it should be fine. Paul

-SNIP->>Sorry or the delay in responding but I was out of town on some>R&R...I guess I could use a HEX ed as you suggest, I just>think MS should have done a better job with it. :-)>>Thanks >Bill>I agree with you 100% there Bill. Having the logbook ina BIN file is totally unnecessary. Another gripe of mineis the inclusion of the "Trusted" section in the fsx.CFG.For anyone that adds alot of aircraft and/or imports A/Cfrom FS9, that section, with it's "complete path to the gauge"will really BLOAT that file making editing a real pain.I don't know it MS's Notepad still has a file size limit asit used to, since I use a 3rd party Notepad program, but ifit does you may find you can't open the fsx.CFG with Notepad at some time in the future.FSX has alot of good changes/updates but in the process theyalso PORKED alot of things...lack of 2D side/back/diagonalviews with bitmaps comes immediately to mind.So, on with the "tweaking" and hoping that MS takes note oftheir shortcomings and corrects them in the future. Paul

Hello:Is there a way to "mass" delete entries into the log book? mines is getting huge and its a pain to highlight everyone and delete it.Also, is there a way to turn off further entries?Thanks.

[email protected] listed above posted an logbook editor for FSX. I have not tried it because I have yet to use the logbook in FSX.This file could be an answer to your problems.file is:logbookedit-2310061902

Thank you Gypsy Baron! :-)You just saved me from having to reinstall FSX (again).I took a look through my logbook.bin with a hex editor and specifically looked for that byte counter after the "05 byte", but my last log entry looked like it had the right byte count. So just to try something what I did was delete the last 05 byte (using a hex editor) and everything after it, so I basically deleted my last log entry.I then launched FSX and it didn't lock up! My 'rewards' were intact, and my logbook was intact! The only thing I lost was my last flight, so I'd say it's worth sacrificing one flight to the Microsoft Corruption God to save the rest of the records. :-)PlaidAvenger

I think you are all missing the point. Why did MS have to change the Logbook in the first place? There was nothing wrong with it the way it was. I never saw a post from anyone complaining about it, did you?The same goes for the 2D view adjustments. No one can figure out how to make adjustments that will stay. The (View) settings from FS98,FS2K, FS2K2 and FS2K4 don't work in FSX either. Did anyone complain about them? Then why did MS have to mess with them?Sorry to sound like I'm RANTING, but I just wonder what geniuses decided to make these changes. maxsdad

VERY DUMB QUESTION. I HAVE LOOKED FOR THE LOG BOOK AND HAVE NOT LOCATED IT. IS IT STILL CALLED LOGBOOKMAND WHAT'S THE PATH TO IT?THANKS.FRANK C

Look on page 2 of this forum. I posted a solution to editing the logbook about an hour ago, and it's already made it to page 2.