What caused the Dem4km.bgl error to come up? I didn't do anything different from yesterday when FSX was working perfectly. So when that error came up, I attempted a REPAIR from Disk 1 of FSX. After the repair was finished, FSX came up with many scenery areas missing and eventually caused a fatal error so FSX couldn't start.It looks like the unthinkable has happened to me after all that I have installed: REX, ASE. UT, GEX, etc, etc. SO many planes, SO many sceneries, So many EVERYTHING. FSX was running so beautifully that it seemed real to me. Frames were up and fluidity was phenomenal. And now, it looks like I'll have to start over again.Any ideas....or has the "unthinkable" really happened to me?Stan

What caused the Dem4km.bgl error to come up? I didn't do anything different from yesterday when FSX was working perfectly. So when that error came up, I attempted a REPAIR from Disk 1 of FSX. After the repair was finished, FSX came up with many scenery areas missing and eventually caused a fatal error so FSX couldn't start.It looks like the unthinkable has happened to me after all that I have installed: REX, ASE. UT, GEX, etc, etc. SO many planes, SO many sceneries, So many EVERYTHING. FSX was running so beautifully that it seemed real to me. Frames were up and fluidity was phenomenal. And now, it looks like I'll have to start over again.Any ideas....or has the "unthinkable" really happened to me?Stan

The worst thing, is loosing scenery.cfg, but all the addons usually make a copy of it, did you check in programdata?Usually FSX files are:1) The main FSX root2) AppData/Local/Microsoft/FSX3) AppData/Roaming/Microsoft/FSX4) ProgramData/Microsoft/FSX5) My Documents/Flight Simulator X Files #4 is critical because it contains the modified scenery.cfg with all your entries and layers#5 contains logbook.bin which, if corrupted wont let FSX start.#1 contains terrain.cfg which, I think is also critical for proper scenery renderingI usuallly keep a 'mirror' of the above folders in a external backup drive.The Dem4km.bgl is part of the BASE scenery which is the most BASIC FSX scenery, getting that error means that you either have no scenery.cfg, it is corrupted OR it is referencing an incorrect PATH.So, check TWO things:1) In the FSX main folder, do you see an Scenery Folder? does it contains a subfolder called BASE/Scenery which also contains Dem4km.bgl?2) Now check scenery.cfg in ProgramData, and check the PATH for the Scenery area 002Should be something like:[Area.002]Title=Default SceneryLocal=Scenery\BASEThe 'Local' path is a RELATIVE path to your FSX main folder.

Do a Google search for the bgl, Stan: it seems not uncommon for this to become corrupt. It might fix it, but if the repair didn't work, I doubt it. On the other hand - after Bojote's first Shader mod I had all aircraft dissemble themselves. I did the repair, added SP1 - it went ok, all aircraft fixed, then SP2 - and immediately back to square one. SO i uninstalled the various bits, SP2, etc., and FSX - then deleted the whole FSX folder: did a regclean, reboot and a defrag, and then did a fresh install, but this time just the aircraft I ordinarily fly. It took one evening, and part of Saturday. Added in the old config and it's now like a new woman friend... Best of luck.

I feel better now Stan. Woke up this morning, noticed my HD that I use for storage went belly up and lost all of my FS9 and FSX downloads and back up's. I don't use an external backup (color me stupid or lazy).

The worst thing, is loosing scenery.cfg, but all the addons usually make a copy of it, did you check in programdata?Usually FSX files are:1) The main FSX root2) AppData/Local/Microsoft/FSX3) AppData/Roaming/Microsoft/FSX4) ProgramData/Microsoft/FSX5) My Documents/Flight Simulator X Files #4 is critical because it contains the modified scenery.cfg with all your entries and layers#5 contains logbook.bin which, if corrupted wont let FSX start.#1 contains terrain.cfg which, I think is also critical for proper scenery renderingI usuallly keep a 'mirror' of the above folders in a external backup drive.The Dem4km.bgl is part of the BASE scenery which is the most BASIC FSX scenery, getting that error means that you either have no scenery.cfg, it is corrupted OR it is referencing an incorrect PATH.So, check TWO things:1) In the FSX main folder, do you see an Scenery Folder? does it contains a subfolder called BASE/Scenery which also contains Dem4km.bgl?2) Now check scenery.cfg in ProgramData, and check the PATH for the Scenery area 002Should be something like:[Area.002]Title=Default SceneryLocal=Scenery\BASEThe 'Local' path is a RELATIVE path to your FSX main folder.

Yes. It's all there as you say...unfortunately, FSX still won't work. Too much missing it seems.Stan

Hope none of you get that scenery error.....it's DEADLY. Only wish I knew how it occurred.Oh well, the mass deletion has begun and is just about over. I will soon defrag the drive and slowly, ever so slowly begin the re-installation process. Thanks for your input everyone.Stan

What caused the Dem4km.bgl error to come up? I didn't do anything different from yesterday when FSX was working perfectly. So when that error came up, I attempted a REPAIR from Disk 1 of FSX. After the repair was finished, FSX came up with many scenery areas missing and eventually caused a fatal error so FSX couldn't start.It looks like the unthinkable has happened to me after all that I have installed: REX, ASE. UT, GEX, etc, etc. SO many planes, SO many sceneries, So many EVERYTHING. FSX was running so beautifully that it seemed real to me. Frames were up and fluidity was phenomenal. And now, it looks like I'll have to start over again.Any ideas....or has the "unthinkable" really happened to me?Stan

You have probably uninstalled/reinstalled FSX but here is the probable solution - a corrupt logbook.bin. Running a simple repair to the logbook would have solved your problem. Here's the link to the solution: http://forums.flightsim.com/vbfs/showthread.php?t=179544. In the future, as Paul J. mentioned, it's best to google the error message or the .bgl and see if there's a solution out there. Could save you some pain and suffering uninstalling and reinstalling FSX and all of your addons!Best regards,Jim

Hope none of you get that scenery error.....it's DEADLY. Only wish I knew how it occurred.Oh well, the mass deletion has begun and is just about over. I will soon defrag the drive and slowly, ever so slowly begin the re-installation process. Thanks for your input everyone.Stan

Stan-So sorry to hear of your troubles. Hope you are back up soon.I was complaining to my wife the other day-computers/cable tv/cell phones/technology (and I love them all)-are supposed to improve our lives. It seems sometimes they have complicated our lives 10 fold and ultimately not improved anything. However as we know flight simming is one of those improvements and a mandatory life need here is to you getting all back rapidly!

Stan-So sorry to hear of your troubles. Hope you are back up soon.I was complaining to my wife the other day-computers/cable tv/cell phones/technology (and I love them all)-are supposed to improve our lives. It seems sometimes they have complicated our lives 10 fold and ultimately not improved anything. However as we know flight simming is one of those improvements and a mandatory life need here is to you getting all back rapidly!

Hi Geofa,You know, it happens eventually to everybody. There's just no reason to get upset when you think of the "positive" side of things: I look forward to taking my time, piece by piece, running each, and defragging along the way. Life does indeed get "cluttered" some time, and Flight Simming is no different. I had tons of planes I never flew, and now I will try to keep my sim under control. I re-downloaded GEX, and REX last night and put them safely in a folder. I fortunately kept all of my stuff on a separate hard drive with serial numbers and license keys.I guess at this stage of life it's better to see the glass as "half-full", and look foward to the future.Thanks, Stan

You have probably uninstalled/reinstalled FSX but here is the probable solution - a corrupt logbook.bin. Running a simple repair to the logbook would have solved your problem. Here's the link to the solution: http://forums.flightsim.com/vbfs/showthread.php?t=179544. In the future, as Paul J. mentioned, it's best to google the error message or the .bgl and see if there's a solution out there. Could save you some pain and suffering uninstalling and reinstalling FSX and all of your addons!Best regards,Jim

"Logbook Recovery"? Wow...who would've ever thought of that? Incredible, if true. Thanks.Stan

Stan,Sorry to hear what happened. But it sounds like you've got the right attitude about starting over. If you need any help (or just moral support) from your simming "neighbor" here in Emmaus, just let me know.John

simming "neighbor" here in Emmaus

Emmaus? is that a 'place' or are we talking about the catholic retreat groups?

It's a town in eastern Pennsylvania, adjacent to Allentown.John

you've got the right attitude about starting over.

Yup! Just look at Stan's avatar pic! :( Hang in there Stan.

What caused the Dem4km.bgl error to come up? I didn't do anything different from yesterday when FSX was working perfectly. So when that error came up, I attempted a REPAIR from Disk 1 of FSX. After the repair was finished, FSX came up with many scenery areas missing and eventually caused a fatal error so FSX couldn't start.It looks like the unthinkable has happened to me after all that I have installed: REX, ASE. UT, GEX, etc, etc. SO many planes, SO many sceneries, So many EVERYTHING. FSX was running so beautifully that it seemed real to me. Frames were up and fluidity was phenomenal. And now, it looks like I'll have to start over again.Any ideas....or has the "unthinkable" really happened to me?Stan

---------------------------------------------------------Sorry to hear your woes, Stan. I suggest an external USB-2 WD 1TB My Book, one defragment run, and a FULL IMAGE original backup and subsequent backups as you install/modify your system. This has saved me already once or twice. Something screws up...you go into the repair system...and pick FULL SYSTEM RECOVERY. Come back in 20 minutes, and you have everything perfect again. Just a tip for the future.Mitch