Microsoft Flight Simulator X: Steam Edition

Microsoft Flight Simulator X: Steam Edition

aladino52 Oct 3, 2016 @ 3:38am
Scenery 120 Error
FSX-SE is giving me the following error following error: Scenery.cfg file error .Invalid remote scenery path in scenery 120. I really need your help I dont want to unistall FSXE and start again
Last edited by aladino52; Oct 5, 2016 @ 12:27pm
< >
Showing 1-15 of 30 comments
APUtech Oct 5, 2016 @ 11:21pm 
Did this error occur after adding on new scenery?
aladino52 Oct 6, 2016 @ 6:03am 
Yes, an thanks for your a reply Im a disabled vet what ever help please go easy on me in explain the fix. I apprciate it.
Speedy Oct 6, 2016 @ 9:10am 
Ok did you install add on scenery then remove it. Basically what that errornis telling us is you a entry in line 120 of your scenery.cfg that has not been removed correctly. If you go to your steam/steamapps/common/fsx folder locate a file called scenery.cfg open it up scroll down to the entry that is numbered 120 and delete that entry. Click yes to save changes then load fsx up. When it loads if you still get the error then go to your scenery library via the settings. And scroll down to entry 120 tick the box then delete it that will remove the error
aladino52 Oct 6, 2016 @ 1:22pm 
I did exactly as you stated and still showing the error.
Kabacus Oct 6, 2016 @ 1:44pm 
The scenery.cfg that is used by FSX lives in C:\ProgramData\Microsoft\FSX (ProgramData is a hidden folder so you will need to set these to be visible (Google)).

Rather than delete the entry I would suggest checking what section 120 holds. It may be something that can be corrected, for example if it lists a path that contains spaces, enclosing the path in quotes will probably fix things.

It may be worth posting the section here to see if anybody could offer further advice.

EDIT: Corrected the path originally thought it was in Appdata but forgot this is the even quirkier location that I always forget about. Sorry for the confusion.
Last edited by Kabacus; Oct 6, 2016 @ 2:01pm
aladino52 Oct 6, 2016 @ 1:53pm 
too late I delete the files area 120 should I get it back?
Kabacus Oct 6, 2016 @ 2:07pm 
The one you have deleted section 120 from is the default scenery.cfg that is copied to the (now corrected) path outlined in my previous post. This copy is then changed as you add/remove scenery, if you can remember what was there putting it back would be good, but it is unlikely that you will copy that file again as it would usually be easier doing a full re-install if things ever got that bad.

If you do want to put it back mine reads as follows:

Title=Addon Scenery
Local=Addon Scenery

Don't forget to re-check the box in your FSX library (at least for now)

If you could paste the same section but from C:\ProgramData\Microsoft\FSX\scenery.cfg somebody may be able to offer a remedy.
aladino52 Oct 6, 2016 @ 3:26pm 
I put your back on mine is the followin area required>? it is part of fsx-steam?

Kabacus Oct 6, 2016 @ 3:42pm 
Yes that is part of the default installation of FSX, though I thought you were getting an error with Area.120
aladino52 Oct 6, 2016 @ 3:56pm 
yes I do. and I just want to ask the question. and I can run fsx but that error message is annoing. still have the problem.
Last edited by aladino52; Oct 6, 2016 @ 3:57pm
aladino52 Oct 6, 2016 @ 4:00pm 
You mention the follwowin : Rather than delete the entry I would suggest checking what section 120 holds. It may be something that can be corrected, for example if it lists a path that contains spaces, enclosing the path in quotes will probably fix things.

How can I check the are 120?
aladino52 Oct 6, 2016 @ 7:11pm 
now it stays at 37 percent loading terrain data
mitsoswu Oct 7, 2016 @ 5:54am 
Did you maybe accidentally, deleted this folder here ?
D:\Steam\steamapps\common\FSX\Addon Scenery
Kabacus Oct 7, 2016 @ 9:19am 
My understanding of scenery.cfg is as follows:

When you first launch FSX for the very first time a copy of the default C:\Program Files(x86)\Steam\steamapps\common\FSX\scenery.cfg is placed in c:\ProgramData\Microsoft\FSX. This “new” copy is then used by FSX for tracking the scenery used for the program.

Initially there are 120 areas that are supplied with FSX, as you install additional scenery the one of two things has to happen for FSX to use the scenery. EITHER the installation program edits C:\ProgramData\Microsoft\FSX\scenery.cfg to add the details of the new scenery OR you have to add the scenery location via the scenery library within FSX.

An example of added scenery in c:\ProgramData\Microsoft\FSX\scenery.cfg:

[Area.003] {The area number)
Title=ORBX!VECTOR_AEC {It,s name as displayed in the FSX library}
Layer=3 {It’s layer number, usually matches AREA}
Active=TRUE {True will show a tick in the library}
Required=True {Will error if not found}

*Local= entries are local to the FSX folder unless a full path is specified i.e. D:\Data\SomeScenery

For each entry in scenery.cfg there will be an entry in your FSX library tab. To confuse things though they are listed in reverse layer order. The entry in c:\ProgramData\Microsoft\FSX \scenery.cfg that has Layer=1 in the section will be at the bottom with the section that has Layer=2 above etc.

If you get a scenery error immediately after installing new scenery it usually means that there is a problem with the path, correcting the relevant Local=… will remedy things. If there are errors later on it could mean that the files are missing or corrupt, or the scenery cache needs rebuilding (there is a checkbox for that on the scenery library tab in FSX).

As I have stated at the beginning of this text wall, this is my understanding of how things work and I would encourage corrections from anybody if I have the wrong end of the stick. To the OP, I hope this gives you a better idea of how to find what is wrong.
Last edited by Kabacus; Oct 7, 2016 @ 9:21am
chelmo Oct 7, 2016 @ 10:15am 
Kabacus.....What about backing up/renaming both fsx.cfg and scenery.cfg and then re-launching FSX. This will create a new fsx.cfg, which can be replaced with the backed up one if necessary, and also create a new scenery.cfg which should, hopefully, be trouble-free. Would that work?

Add-ons will have to be re-installed though....
< >
Showing 1-15 of 30 comments
Per page: 15 30 50

Date Posted: Oct 3, 2016 @ 3:38am
Posts: 30