Bandit Posted May 6, 2012 Share Posted May 6, 2012 Hi Guys, I should have listed to the old addage - "if it aint broke dont fix it!" I was trying to get ENB working - loaded the ENB files (d2d9.dll & enbseries.ini and got it to work internittantly. Now when I start FSX it hangs a the title screen. CPU core 1 is at max (of cores 1 to 3). I have to kill the app in task manager. I tiried to delete fsx.cfg - no luck I tried to remove the ENB files (d2d9.dll & enbseries.ini) - no luck I am stuck and trying to avoid a reinstall!! :'( Any ideas? Link to comment Share on other sites More sharing options...
Bandit Posted May 6, 2012 Author Share Posted May 6, 2012 Drama solved - it was a corrupt logbook.bin file in my FSX documents directory. Deleted the file - all good, Phew! Still cant get enb to load properly when I enter the flight. I have to ALT-TAB to the desktop & re-enter to get it to start working.. Link to comment Share on other sites More sharing options...
Just Fly Posted May 6, 2012 Share Posted May 6, 2012 Have you tried SHIFT + F12 ? It is supposed to turn ENB Series on/off. Link to comment Share on other sites More sharing options...
Bandit Posted May 6, 2012 Author Share Posted May 6, 2012 Yes I have tried that. In any case its on by default but still turning it off then on again in game using the Shift-F12 doesnt help. Link to comment Share on other sites More sharing options...
Wolter van der Spoel Posted May 7, 2012 Share Posted May 7, 2012 Hi Mark, just by chance any other FPS limiters or Shader mod 3 active, or the not sure anymore MSI controlpanel for the vidcard, they don't want to play nice with Link to comment Share on other sites More sharing options...
WilliamJSS Posted May 7, 2012 Share Posted May 7, 2012 What does the logbook.bin do? Is this a fix that would also help crashing after about 3 or 4 minutes of fsx running? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Bandit Posted May 7, 2012 Author Share Posted May 7, 2012 The Logbook.bin is a binary file ('1's and '0's - hence the .bin filename extension) that stores the pilot records of flights, number of landings, hours flown etc. FSX writes to this file at the end of every flight. If interupted when writing to the Logbook.bin file (e.g. FSX hanging on end of flight, user abruptly terminating FSX from, say task manager) the file can get corrupted. FSX tries to open and read this file when it starts up before it show the main menu (eg 'Free flight' etc). If the file is corrupt FSX cant read it and just 'hangs'. (I suspect it cant detect the end of the file and keeps trying to read) If you delete the Logbook.bin file FSX will create a new, empty file and continue in its startup. Doing so will erase all your flight history but will stop the corrupt logbook.bin file being one\the cause of FSX failing to start. [before deleting any file it is a good idea to take a backup some place in case that isnt the problem and you want to replace it.] The logbook.bin file is located in your "My Documents\Flight Simulator X Files" directory Link to comment Share on other sites More sharing options...
jaje Posted May 7, 2012 Share Posted May 7, 2012 If you suspect it is a logbook corruption, there is a little application on the Avsim library which will analyse your logbook, make a backup and remove the corruption in the file. Just do a search for FSX Logbook Recovery. The file itself is named fsxlogrecovery11.zip. It has saved me on several occasions J Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.