The A2A Simulations Community

Is there a way to get the numbered "area" scenery items NAMED ??

Are you referring to the 4-digit numbered scenery areas?

Those are the grid coordinates for the global default
terrain coverage.

In the SDK there is a map that shows the row/column
numbers and the grid that covers the entire globe. Look
in the SDK - Terrain SDK - Terrain and Scenery - Base File Information.

Looking at that 'map' is the only way I know to identify
what area is covered by a particular entry. It looks like this:



Paul

Thank you for the response Gypsy B. It covered new territory for me. But I was referring to the list of "areas" in the scenery settings tab of FSX. I show 7 Major cities, Some continents, and then 93 numbered areas "1107 Base" thru "0001 Base" .
I would assume these numbers correspond with scenery's that could be named for better reference so that a user could move them to a more prominent spot in the hirearchy, or delete, or whatever. Not sure if this is the correct way to acknowledge your answer, Im new to the A2A site. Thanx again, Gary Q.

Those numbers, 1107 Base, 0001 Base, refer to the mapping I posted.
Area 1107 is the quadrant in Column 11, Row 7 which is a slice of Antartica
while 0001 refers to Column 0, Row 1 which covers the Aleutians.

Thus, the "93 numbered areas" are defining those quadrants as depicted
on the map and can't be renamed. FSX uses those scenery.cfg entries
to determine what to load for a given area and some of those are
"Required" for FSX to load.

Paul

OKAY !!! Got it. and thank you for this detailed explanation. Gary Q.

You are welcome. Glad I could help.

As a side note here, I utilize multiple 'scenery.cfg' files that have various scenery areas
enabled or disabled, depending upon where I intend to fly. I keep these tailored scenery.cfg
files in folders in the same folder as the 'active' scenery.cfg, with names like "Hawaii",
"USA", "OZ", "Europe", USA_Europe".

Before starting FSX I go to the scenery.cfg file location (via a shortcut on my desktop)
and simply copy the cfg file I want or use and over-write the current active cfg.

I started doing this when, using a file logging utility, I found FSX accessing
scenery BGL files that were on the opposite side of the world from where I was
flying, so to prevent 'unnecessary' file operations I disabled all areas that were
not required or in the region I was flying. Saves a tad bit of time on FSX loading
but not enough to notice with all of the myriad other file accesses that FSX
goes through on startup!

Paul

_________________
Paul


i5-2500K @4.3Ghz OC - GA-P67A-UD7-B3 - 8GB Corsair 1600mHz

Superb, I'd wondered about this too. This is good to know, thanks Paul.

John.

_________________
~ Make love to the sky, don't shag it.

You are welcome, John.

Just be aware that there is one scenery area, one of the numbered ones,
that has to be enabled. I seem to recall it was somewhere out in the
South Pacific. Anyhow, FSX will let you know if you happen to disable it.

In my scheme, I keep a named copy of each of my custom cfg files
in their own folder..."Hawaii_scenery.cfg" in the "Hawaii" folder along
with the custom "scenery.cfg" file. They are identical and the named one
just serves as a backup and 'cues' me so that I know I am in the
folder I intended to be in

In my Explorer window I always have the folder view enabled on the
left and open the folder containing the area I want to use, then do the
CTRL-drag and drop of the custom scenery.cfg file into the main folder,
overwriting the one that is currently there.

One should, of course, have a folder with the 'default' scenery.cfg file
in it, or as mine is call "ALL_scenery.cfg".

Another 'trick', if you use addon gauges like the Airport Chart gauge
and others that must scan the scenery.cfg file to build a database,
is to keep a copy of the "all' scenery.cfg file but with ALL the
'Addon Scenery" cut and pasted ABOVE the default areas.

I call it my "Reversed_scenery.cfg". The reason being, in the case of
the Airport Chart DB builder routine, it takes the data from the FIRST
occurrence of an airport as it scans the cfg file and BGL's. Thus
if the scenery.cfg is in the regular order, modified airfields will not
display properly. For instance if parking or facilities are added, they
won't appear to the Airport Chart application. Using the 'reverse
order' solves this issue.

On another note, I also have multiple copies of "fsx.exe" named
to suite my desired configurations. "fsx_MP.exe" when run,
creates a new fsx cfg file named "fsx_MP.cfg". That allows me
to enabled/disabled various classes of sim objects like my AI
aircraft that are all in their own directory on a separate drive.
Since I don't want or need them in MultiPlay that unique cfg
file disables them as well as enables a bunch of add-on paints
for the A2A aircraft that I expect to 'see' in a MultiPlayer session.

I have an "fsx_Propliner.exe/cfg" setup for days without tubeliners
Another "fsx_A6.exe/cfg" for times when I just want to fly the Intruders
that I have.

In the fsx.cfg file "Main" section you call out the paths to the simobjects
that you wish enabled and, since you have to supply the FULL path,
that means you can locate you 'special' folders or 'hangars' anywhere
you wish on your system and if you break out various classes that
means you can selectively disable them as well.

I fly a lot of MultiPlayer with the 91st Bombardment Group and have
a folder named "91st BG Aircraft" over on my "Y:" drive. In that
folder are folders for the A2A Spit, P40, P47, B17 and a few other
aircraft. I still have the DEFAULT A2A folders in my main "simobjects"
folder so that updates will work without problems but I have copies
of those folders MINUS the DEFAULT A2A aircraft in my 91st folder.
The 53 add-on B-17 paints for the 91st BG reside in that folder.
Thus when I am NOT flying MP, that 91st folder is disabled, removing
all those 'extra' thumbnails and FSX doesn't go loading them

Paul

I have a great deal to learn in that sector, I've not dabbled far beyond reckless mouse clicking with scenery files. Thank you very much for your time Paul.

Paul, whilst this thread has your focus; I wish to apologise to you, for my rather crass, and asinine response to a thread about two weeks ago, I was wrong to be so abrupt, and came across as bloody rude. No excuse.

John.

_________________
~ Make love to the sky, don't shag it.

NP John. You had no way of knowing the circumstance at the time.

I jumped in there just to curtail any further comments.

Paul