I recently added a airport scenery, thinking I did not have it previously.Now I am getting a error saying something to the effect "Local scenery config error in LC # 83,,,,,,,,"I looked in my scenery config folder and noticed a difference in the line entries...as follows[Area.083]Title=German Airports 2 - LeipzigLocal=aerosoft\EDDP_2008Active=TRUELayer=58Required=FALSERemote= My question being the "Remote" entry is not required...correct? And I should be able to remove it and take care of the error message.Thanks,Neil-irish3

I recently added a airport scenery, thinking I did not have it previously.Now I am getting a error saying something to the effect "Local scenery config error in LC # 83,,,,,,,,"I looked in my scenery config folder and noticed a difference in the line entries...as follows[Area.083]Title=German Airports 2 - LeipzigLocal=aerosoft\EDDP_2008Active=TRUELayer=58Required=FALSERemote= My question being the "Remote" entry is not required...correct? And I should be able to remove it and take care of the error message.Thanks,Neil-irish3

Correct. I have no such line anywhere in my scenery.cfg (but 1008 entries )

I recently added a airport scenery, thinking I did not have it previously.Now I am getting a error saying something to the effect "Local scenery config error in LC # 83,,,,,,,,"I looked in my scenery config folder and noticed a difference in the line entries...as follows[Area.083]Title=German Airports 2 - LeipzigLocal=aerosoft\EDDP_2008Active=TRUELayer=58Required=FALSERemote= My question being the "Remote" entry is not required...correct? And I should be able to remove it and take care of the error message.Thanks,Neil-irish3

The 'Remote=' comment without a 1 following is default and would not be the reason for your error message. Looking at the scenery entry I did notice a problem however. The "[Area.083]" and the layer=58 is wrong and probably the cause of your problem. If the scenery entry above this one is [Area.082] and Layer=82 then you should change Layer=58 to Layer=83 in the above problem area.The [Area.xxx] and Layer=xxx numbers in each scenery entry layer should be the same and should be in numerical order.There are couple of utility programs that will correct scenery configuration errors: FlightSimManager available here at AVSIM as 'fsm285.zip' and a patch to fix a date issue 'startfsm.zip' also here at AVSIM and another named Renumber Scenery Config also at AVSIM as 'rsc_v1.2.0.zip' The latter is not flashy but gets the job done. Either one should solve your problem(s).I hope this helps you fix your problem.Best regards,Mel

All my entries have Remote= lines and it never caused a problem. AFAIK you have to either fill the Local= or Remote= but not both. Remote= causes FS9 to copy the contents of the scenery and texture folders to your FS9 HD cache.scott s..

Thanks gents, appreciate the inputs. Now I have a path to follow.... :( Cheers,irish3

Irish,When you get a resolution, I'd be glad to know as I have a similar problem.I decided to go through my add-on scenery entries in the FSX scenery menu, and edit them to tick the 'cache scenery' boxes, which I hadn't done when adding them, including the Horizon GenX sceneries, series 1-3 and Scotland. After that exercise, I get loads of error messages for most all of the extra scenery.cfg lines.I'll be using the kind advice, and the utilities recommended here too.Thanks all.Phil

Phil,Have downloaded the rcs_V1.2.0.zip, but it did not excute for me. Will try another download today.The fsm285.zip was a bit of a maze trying to get it downloaded. Went thru several steps, but gave up after Five minutes.Will keep plugging away and let you know.irish3

With all due respect Mel, most of what you state here is simply inaccurate.

The 'Remote=' comment without a 1 following is default and would not be the reason for your error message.

FWIW, the Remote= line will be a path, not a 0 or 1. This line would only be useful if you are storing scenery files on a medium that reads slower than your harddrive, like a CD or maybe on a server. FS would then copy those files, when needed, to a temporary folder on the faster harddrive.Note that you should not have a path in both Local= and Remote=, it's one or the other.I remember reading somewhere that there was a payware scenery that came with an installer that edited the scenery.cfg. This installer failed to add the Remote= line and this caused problems such as double entries in the scenery.cfg. I can't remember which addon it was, if I can find my notes I will post back.

Looking at the scenery entry I did notice a problem however. The "[Area.083]" and the layer=58 is wrong and probably the cause of your problem....The [Area.xxx] and Layer=xxx numbers in each scenery entry layer should be the same and should be in numerical order.

This is a common misconception.There is absolutely no relationship between the [Area.nnn] entry and the Layer= entry.They do not need to be the same for any given [Area.nnn] and they do not need to be in order in the scenery.cfgHaving mismatched [Area.nnn} and Layer= entries is not a problem or an indication of a corrupted scenery.cfg.The [Area.nnn] entry is a number assigned by FS when you add a scenery area. The only rule for [Area.nnn] is that they must be unique.The Layer= entry tells FS in what order to load scenery areas (scenery priority) and is an inverse reflection of what you see in the Scenery Library, meaning that [Area.001] is at the bottom of the Scenery Library and not the top.

There are couple of utility programs that will correct scenery configuration errors: FlightSimManager available here at AVSIM as 'fsm285.zip' and a patch to fix a date issue 'startfsm.zip' also here at AVSIM and another named Renumber Scenery Config also at AVSIM as 'rsc_v1.2.0.zip' The latter is not flashy but gets the job done. Either one should solve your problem(s).

As already stated, nothing mentioned in this thread should be seen as a "scenery.cfg error". However, having a "cleaned up" scenery.cfg does make it easier to read. I prefer to use Steve Greenwood's utility to keep mine in order. It is a small, simple to use app that does one thing and does it well.You can find it here, third one down- http://home.earthlink.net/~smgreenwood/resources-g.shtmlregards,Joe

FS9 SDK on "Terrain and Scenery Configuration Files":The Scenery Configuration FileThe Scenery.cfg file tells Flight Simulator where scenery files are located and whether to empty the Cache upon exit. It can also be used to exclude certain types of scenery. The [General] SectionThe [General] section applies to all of Flight Simulator scenery. You will not need to edit this section of scenery.cfg. [General]Title=FS9 World SceneryDescription=FS9 Scenery DataClean_on_Exit=FALSEClean_on_Exit=FALSE or TRUE when a “TRUE” setting tells Flight Simulator to delete all files from the “Cache” folder upon exiting, and the “FALSE” setting tells Flight Simulator not to delete all files from the “Cache” folder upon exiting.Scenery AreasThe scenery area entries tell Flight Simulator where scenery is located. A typical scenery area entry in the Scenery.cfg looks like the following example:[Area.001]Title=Default TerrainTexture_ID=1Local=Scenery\WorldRemote=Layer=1Active=TRUERequired=TRUEEntry Title [Area.XXX] when XXX is the scenery area entry number (i.e., 077). XXX must be an unique number.Scenery Title Title=XXXXXX when XXXXXX is the title of the area. This text will be shown under the “Scenery Area” column in the Flight Simulator Scenery Library.Path Designation Local=path or Remote=path When using the “Local” designation the scenery is read directly from the path shown. When using the “Remote” designation the scenery is copied from the path shown to a uniquely named folder created automatically by Flight Simulator. The scenery files are then read from the new folder in the “Cache” folder. The “Remote” designation is very useful when reading scenery files from a location that cannot be accessed as quickly as the local hard drive (i.e., CD drive, remote server).Path Formats: Both “Local” and “Remote” Path Designations can use various formats for designating the path to the scenery:Drive:\path Typical path designation (i.e., C:\MyScenery)[Volume]\path Uses the volume name of the drive and then the path (i.e., [MySceneryCD]\MyScenery)\\Machine\share\path Uses a server path (i.e., \\MyServer\MyScenery) Status Active=TRUE or FALSE in which a “TRUE” setting tells Flight Simulator to display the scenery and a “FALSE” setting tells Flight Simulator not to display the scenery. This will be shown in the Flight Simulator Scenery Library under the “Enabled” column.Required=TRUE or FALSE in which a "TRUE" setting means the directory must be there for Flight Simulator to run and you cannot delete it or turn it off in the Scenery Library dialog. Layer Number Layer=XX in which “XX” is a number typically equal to the Entry Title area number (i.e., 77). Higher numbered layers have priority over lower numbered layers. This number is shown in the Flight Simulator Scenery Library under the “Priority” column. Miscellaneous Texture_ID=0 and Texture_ID=1 are very special settings that most likely should NEVER be changed. Texture_ID=0 sets the global default texture directory to be searched if the requested texture cannot be found in its sister texture directory. This is also the location of Flight Simulator's global textures that have no sister texture directory to reside in. Texture_ID=1 is the default terrain texture directory.scott s..

Hey Irish, was it that RSC was hard to install or was it that you couldn't get a copy of it? If you want a copy, I'm using 1.2.1 and can send it to you if you PM me with your email address. Since I wrote it, I can help you to get it setup if you want and will provide further explanations if required.It's fairly straight forward to get it installed. You basically unzip the contents to a folder using pathnames. Then try to run the rsc.exe file and see if the app opens. The reason that you're doing that is to know if you need to install Microsoft's VB6 runtime files or not. If the app opens then you probably don't need the runtime files because they're already on your system. If it doesn't open or you get a runtime error then you need to install the VB6 Runtime files. That's it for the install.After you get it installed, copy your scenery.cfg file to the FS9 Renumber folder. Then start the app, select the "FS9 Renumber Folder" option on the dialog and then load the scenery.cfg file that you copied to the FS9 Renumber folder. Once the file is loaded, click the "Renumber" button. Then it's simply a matter of copying the newly renumbered scenery.cfg file back to your Flight Simulator 9 folder so it can find it.By the way, the app makes a backup copy of your orignal scenery.cfg file in the "FS9 Renumber" folder so you can always revert back to a previous version if you want. The app simply appends the current date a time to the file before it renumbers it so you'll always have a backup copy. So let me know if you want a copy of 1.2.1 and if you need any help installing it.Mark

No offense taken Joe. If I am in error then I am in error. I would prefer to be politely corrected the way you went about it, and learn from my mistake(s), rather than suffer from some misinformation that I honestly believed was accurate. Thank you.Best to you,Mel

Hey Joe, I've tried to use Steve Greenwood's utility but have always received a "Runtime Error 9 : Subscript Out Of Range" message. That error is probably due to his app attempting to populate an array that doesn't have enough room. Translation, I have more the 1200 installed sceneries and Steve's app may have a fixed number of sceneries that it can work with.What's really funny is that I never would have written rsc if I could have gotten Steve's app to work! Ironic isn't it. So I took me all of about 5 days in total to write rsc and I think it shows...but at least it works well for me :)Mark

Mel,it's all good. ;)Mark,Steve's readme states-Maximum Areas: 2000Maximum lines per Area: 50...and...This is a Visual Basic Application and requires MSVBVM60.DLL for VB runtime support on your computer. This file can be placed in the folder with this application if youwould rather not install it, but it is normally installed in the Windows\System folder. If this file is not present, you can download and install it from:http://www.microsoft.com/downloads/details.aspx?FamilyID=bf9a24f9-b5c5-48f4-8edd-cdf2d29a79d5&DisplayLang=enOther than that, I'm not much help with VB stuff, a little outta my league.I can say I've recommended this utility to many people and never heard anyone say it wouldn't run.regards,Joe[edit]I just ran a test by moving that .dll out of Windows\System32 and fsscenery.exe throws a warning that it can't find that file and won't run, so that's not your problem. Sorry.[\edit]

Thanks Joe...I also tried to think out of the box on this one. I thought it was because I had a bunch of comments in my scenery.cfg file so I took them out and still got the same error. Mark

Mark,Maybe you could extract the original scenery.cfg from your discs, make a couple simple edits and see if that file will run through Steve's ute.That would indicate if the problem is either your scenery.cfg or the ute simply won't run on your system.FYI, the scenery.cfg is on disc #4. Actually there's two of them, one each in folders named COMPACT and COMPLETE.regards,Joe