Beg your pardon guys - I meant the "scenery.cfg" file that's hidden (in win7) in: C:\ProgramData\Microsoft\FSX
The one that starts :
[General]
Title=FS9 World Scenery
Description=FS9 Scenery Data
Clean_on_Exit=TRUE
[Area.001]
Title=Default Terrain
Local=Scenery\World
Texture_ID=1
Layer=1
Active=TRUE
Required=TRUE
[Area.002]
Title=SantoriniDummy
Local=F:\Program DLs\FSX\Beta Santorini\SantoriniDummy
Layer=2
Active=TRUE
Required=FALSE
[Area.003]
Title=Default Scenery
Local=Scenery\BASE
Layer=3
Active=TRUE
Required=TRUE
[Area.004]
Title=0000 Base
Local=Scenery\0000
Layer=4
Active=TRUE
Required=FALSE
...which is quite simply a list of all the sceneries you have activated in your scenery library.
As you read DOWN the list, you will see all your active sceneries as they appear in the library from the BOTTOM UP. This is also reflected in the lines that begin "Layer=" and if you read the lines that begin "Title=" you will see that this is the case too
The [Area.nnn] number reflects the order in which you activated the scenery addon. So when you move a scenery up or down you change its' position in the layering order. FSX merely edits the scenery.cfg by moving the [Area.nnn] block of text accordingly.
As long as the "Layer" numbers run consecutively throughout the whole config file, you should have no problems. I have, however, occasionally found that the scenery.cfg has gotten itself corrupted. If and when I think I have issues I will check here too.
So to come back to the original problem
My problem: " invalid Remote scenery path in scenery aera 174 "
you have to scroll down your scenery.cfg to [Area.174] and see what's wrong. Look at the line that starts "Local=" and compare the path that you see there to the scenery's location on your hard drive. Perhaps something got moved.
Also - my mistake - the texture.cfg is in the aircraft texture and has nothing to do here. Sorry.
