Hello. Hopefully one of you can help me with something here.Can anyone tell me if it's possible to rebuild the scenery.cfg file while still retaining all of the entries? In other words, I would rather not have to add all of my scenery addons again one-by-one. I think I might be having an issue with this file and am hoping there is a way to do this somehow.Any advice would be appreciated.Thanks!

Hello. Hopefully one of you can help me with something here.Can anyone tell me if it's possible to rebuild the scenery.cfg file while still retaining all of the entries? In other words, I would rather not have to add all of my scenery addons again one-by-one. I think I might be having an issue with this file and am hoping there is a way to do this somehow.Any advice would be appreciated.Thanks!

First of all, do NOT delete the scenery.cfg file - it does NOT get rebuilt in FS2004 like the FS9.cfg file does.To keep my scenery.cfg file "healthy" I use the fine little utility by Steve Greenwood called FSTscenery.exe. It works for both FS2004 and FSX and comes with easy to understand instructions.You can get it here: http://home.earthlink.net/~smgreenwood/resources-g.shtmlI use it at least once a week.

I don't know if I'll be able to do this, but, let me see if I can try to explain what's going on.Basically what's happening is my heading is all screwed up on any aircraft at any airport after the computer is restarted. Let me explain further. When I turn on the machine, load the sim and go to an airport the heading indicator is wrong. It's off by anywhere from 8 degrees and up. I've actually had it off by about 160 degrees once. However, if I go to the Scenery Library and uncheck pretty much any scenery item, close the sim, start it back up again and go to an airport, the heading seems to be fine. But, If I reboot the computer and go back in again, it's wrong once again.I know that the first time FS9 is launched it must be going through some additional setup process, check or something because, as I'm sure you have noticed to, it takes longer to load after a restart then just closing the program and reopening it.I have attached to screen shots showing the heading indicator wright and wrong. These examples are sitting on Rwy 27 at KSAN but the problem happens anywhere.I am about at my wits end trying to figure this out as I have been working on this problem for weeks trying to figure out what is causing it. I initially thought there was some corrupt addon scenery loaded as my Dad actually had the same problem on his machine. It seemed to be fixed by narrowing down to a specific scenery addon and removing it. Once that was done things seemed to be fine. However, I have gone through mine and can't find anything. Everytime I thought I had it narrowed down to a possible few the problem would come back without even turning them back on. I just don't understand what is causing this.If anyone has any suggestions I would GREATLY appreciate hearing them. I'm about ready to give up.Thanks!

Is this happening with all aircraft or just a particular one?

Any aircraft, as noted.

Any aircraft, as noted.

Sorry - I missed that in your post.You might take a look at your Realism settings and see if there is a check mark in the Gyro Drift box.Also take a look at the Heading information in the FS2004 Help section - there might be some answers there.Good luck!

The Gyro Drift box is not checked.It's definitely a corrupt or invalid something somewhere. I just have no idea where. The reason I say that is because it hasn't always been like this. This weird thing started a few months ago. I read a post here (or maybe it was someplace else) that mentioned pretty much the same thing another person was having and his (or her) problem was bad scenery. That's what turned me on to the idea in the first place. I've gone though just about all I know I can and am seriously stumped.By the way, I did run the tool you suggested but it didn't make a difference.If you, or anyone else, has any ideas I'm open to hear them.Thanks!

The Gyro Drift box is not checked.It's definitely a corrupt or invalid something somewhere. I just have no idea where. The reason I say that is because it hasn't always been like this. This weird thing started a few months ago. I read a post here (or maybe it was someplace else) that mentioned pretty much the same thing another person was having and his (or her) problem was bad scenery. That's what turned me on to the idea in the first place. I've gone though just about all I know I can and am seriously stumped.By the way, I did run the tool you suggested but it didn't make a difference.If you, or anyone else, has any ideas I'm open to hear them.Thanks!

If that is the case then you are probably going to need to "bit the bullet" and disable all of your addon scenery entries and start adding them back in, 10 or so at a time - checking to see if the problem has been cured after adding each set. Sooner or later the culprit will show up (if it indeed a scenery issue) and you will know which group it is in.Tedious I know, but probably worth the effort.

The problem is that's what I've been doing. Just when I think I have it narrowed down to a possible few the problem returns without making any changes. Everything seems okay and then out of nowhere it comes back. I guess it's possible that something is corrupting (or whatever) additional items as time goes on but that just seems very unlikely.

If I were you I'd check for FS2002 afcads in your FS2004 scenery,I seem to remember they cause the heading to be off by several degrees.Not entirely sure that is it but it can't hurt to try.cheersJP.

The problem is that's what I've been doing. Just when I think I have it narrowed down to a possible few the problem returns without making any changes. Everything seems okay and then out of nowhere it comes back. I guess it's possible that something is corrupting (or whatever) additional items as time goes on but that just seems very unlikely.

If you have not done so already I would suggest using the ScanAfd utility to scan your setup for duplicate afcads.You can it at Flightsim.com since our library is still down.Name: scanafd.zip Size: 160,221 Date: 03-16-2004 Downloads: 2,173 FS2004 ScanAFD v1.0. This utility is intended to help streamline the managing of AFCAD2 files. The program reads ICAO codes from each add-on AFD file installed and provides a straightforward means of identifying duplicate airports and renaming or deleting these files. The program can also search for AFDs within scenery add-ons and identify conflicting files across different sceneries. By Eliot Rogers.Might be worth a shot as duplicate afcads can cause all sorts of strange things to happen.

If you have not done so already I would suggest using the ScanAfd utility to scan your setup for duplicate afcads.You can it at Flightsim.com since our library is still down.Name: scanafd.zip Size: 160,221 Date: 03-16-2004 Downloads: 2,173 FS2004 ScanAFD v1.0. This utility is intended to help streamline the managing of AFCAD2 files. The program reads ICAO codes from each add-on AFD file installed and provides a straightforward means of identifying duplicate airports and renaming or deleting these files. The program can also search for AFDs within scenery add-ons and identify conflicting files across different sceneries. By Eliot Rogers.Might be worth a shot as duplicate afcads can cause all sorts of strange things to happen.

Already checked.

If I were you I'd check for FS2002 afcads in your FS2004 scenery,I seem to remember they cause the heading to be off by several degrees.Not entirely sure that is it but it can't hurt to try.cheersJP.

I'm pretty certain I don't have any but how would I distinguish between the two?

Does anyone at least know what FS9 is doing during its load process after a computer is turned on or restarted that is different than just shutting the program down and opening it again? This may provide a clue.

This isn't going to help much with your current situation but you might want to give it some thought for the future. I've gone through something like this before, when something corrupted everything so badly that I had to do a reinstall of FS9 because I couldn't find the offending file. Ever since then, I keep really good online and offline backups. That way I can simply delete what's on the hard drive and copy what's on the backup.Another thing I did was to create a folder structure where I put all of my addon scenery which lends itself to re-creation. The folder is completely external to the Flight Simulator 9 folder. So if I do have to nuke the FS9 folder and bring it back, none of the addon sceneries are affected. All of my static object libraries and Afcads are externalized also. You will run into issues with the FS9 global Texture and Scenery folders but once again, they need to be backed up regularly so you have a restore point. Refrain from putting anything into the FS9 folder as much as possible. I've been working on a SQL Server 2005 database which tracks changes to all installed sceneries by size, date, and name. I've built up a list of the add-ons so a stored procedure will automatically regenerate the last know good configuration. It's apparent that I went to extremes with FS9 but at a peak install, I might have had more then 3 million files on my hdd. I was installing a ton of freeware and sometimes I would run into a single texture or bgl that would crash FS9 and got tired of it. Any texture or bgl that is replaced now is known and since I keep really good backups, can be reverted almost immediately. I know it sucks, (sorry about that), but you need to come up with some type of a schema to avoid a reinstall. This happens to almost everyone I think.Mark

This isn't going to help much with your current situation but you might want to give it some thought for the future. I've gone through something like this before, when something corrupted everything so badly that I had to do a reinstall of FS9 because I couldn't find the offending file. Ever since then, I keep really good online and offline backups. That way I can simply delete what's on the hard drive and copy what's on the backup.Another thing I did was to create a folder structure where I put all of my addon scenery which lends itself to re-creation. The folder is completely external to the Flight Simulator 9 folder. So if I do have to nuke the FS9 folder and bring it back, none of the addon sceneries are affected. All of my static object libraries and Afcads are externalized also. You will run into issues with the FS9 global Texture and Scenery folders but once again, they need to be backed up regularly so you have a restore point. Refrain from putting anything into the FS9 folder as much as possible. I've been working on a SQL Server 2005 database which tracks changes to all installed sceneries by size, date, and name. I've built up a list of the add-ons so a stored procedure will automatically regenerate the last know good configuration. It's apparent that I went to extremes with FS9 but at a peak install, I might have had more then 3 million files on my hdd. I was installing a ton of freeware and sometimes I would run into a single texture or bgl that would crash FS9 and got tired of it. Any texture or bgl that is replaced now is known and since I keep really good backups, can be reverted almost immediately. I know it sucks, (sorry about that), but you need to come up with some type of a schema to avoid a reinstall. This happens to almost everyone I think.Mark

Don't take this the wrong way... I appreciate any and all suggestions. However,I do keep good backups. The problem is this issue apparently started quite some time ago and I didn't realize it. Therefore a current backup does me no good. Also, it's nice, for you, that you are able to develop such tools to help you. But, that doesn't really help the rest of us.I might be getting closer to narrowing down the problem at hand. I spend a few more hours on it yesterday and so far so good. I'm sure I have several more to go but hopefully I can find the culprit(s).