OleGreyGhost

i know I am late to the party, but might I suggest the Logbook Editor by Dan Downs. Just look in the library for " logedit3_364661.zip. It is an excellent Program & easy to use. FYI. The technical term for your problem is a corrupted EOF {end of file} marker. It usually happens quite often when you close down FSX too quickly. As always, make a backup of the file first. Then remove the last logbook entry, restart FS. If it boots, you are done. If not repeat & rinse. It should only take a few deletions to restore the logbook. Hope this helps....

@Sweetd31, That is what I had to do. Rebuild my scenery files, the scenery cfg. & the scenery indexes. It seems FS is a little sloppy with its' housekeeping; doesn't like adding & deleting the A/P scenery files. Yeah, it seems most of the old support sites (avsim.net & sim-outhouse.com) aren't functioning any more. I know it's not available at the flightsim store anymore But you can try this old e-mail address, it might help!! [email protected] Take care.....

@Luis Hernandez Been away from this for too long. Rebuilding FSX X from the ground up, one piece at a time, is a nightmare. About 20 or so planes & 50 plus airports, (mostly freeware) not to mention the extra scenery, effects & utility programs. Now, I just have to update a few utility programs. I tried an old unorthodox method from back in the days of DOS. I just had to edit & rebuild about 180 files. Job's done. Wish I thought of this first. Deleted everything to get a fresh start. Lost some good programs (ORBX Trees). I just got lucky. What convinced me to try this was when I tried to load in ORBX Trees (company is defunct) plus the headache with DX10 Fixer, & I could not remember how to fire up the nuclear reactors near the airport. Take care.....

If it is just traffic you want you can go into the settings, open the traffic tab and adjust the sliders to your hearts content. (bboats, planes & vehicles). Editing afcads is a deep learning curve; but scruffy ducks Airport Design Editor is the way to go. You can find it in the library......

Luis, Yes. I ran out of ideas also. So I uninstalled it. Installed updated version 3_4_108 with an ".exe" dated 11/6/2117. Received the message "install successful". Was kind of surprised that only 6 files were updated. Flew a couple of test flights, everything appears normal. Cockpit shadows & nighttime traffic over the bridge look great. Also found the problem for the error. When I reinstalled FSX, I used a different directory setup. DX10 ini files was pointed to the wrong location. Thanks for taking an interest, Luis. All replies are much appreciated. Can consider this problem solved.....

Well, I tried loading it again. A little bit of activity; then it stopped. Displayed the message: Error creating working copy - file - fx_AfterBurnerFire1.fx - system error was 3. It repeated the error for the version 2 & 3 ".fx". It repeated the error for all (over 300) entries after that. Hopefully someone is familiar with this error & knows the solution. Ciao....

Luis, Thanks for the interest. Yes, I want to take up where I left off 5 yrs ago. I'll take this up in another post. Hopefully I can get an answer as to what caused the error# 3 in Steves' DX10 fixer, so I can load that in. Ciao, olegreyghost...

Just recovered from corrupted scenery objects and performed a reinstall of FSX Acceleration (boxed edition). The prior install ran well for 7+ years. It consisted of FSX, DX10 fixer & the SDK. A/C & A/P scnery were freeware with a couple of updated local A/P. Lost my notes on the load order So far I have a stable operating FSX with the DX10 preview functioning well on my D drive. Added some recommended fsx.cfg & nVidia tweaks without any problems. Not sure as to which should be loaded first (SDK or fixer); I attempted to load in Steves' DX10 fixer, but that failed ( libraries were greyed out). I received the reason as error # 3. (what does # 3 refer to?) Did not remember getting any error on the previous install. So before I screw anything up, I am seeking some knowledgeable guidance.