
How To...Avoid Scenery.Cfg Problems
By Nigel Grant
ince
the introduction of FS2000 there has been a lot of anguish expressed
about the erratic behavior of the "scenery.cfg" file, particularly
when add-on sceneries and the default scenery layers exceed about 200
layers. In addition, FS loading took a long time when there were
many scenery layers. I eventually got round these problems with my
own system so I would like to share my way of dealing with this
irritating file.
There are several general principles to keep in mind when
manipulating scenery within the FS2000 library.
- Do not add more than one scenery at a time or all h..l breaks
loose, scenery priorities get changed, areas are duplicated then
don't show.
- Always re-boot FS2000 after you have installed a new scenery.
- Do not delete a scenery layer within the FS2000 library, the layer
gets deleted but always seems to move an adjacent layer to the top of
the list. I get round this by de-activating the unwanted scenery
layer and moving it to the top of the list. I then exit FS2000 and
delete this scenery layer from the "scenery.cfg" file. Seems to work
fine.
- Use Wordpad for editing the "scenery.cfg" files since Notepad has
a limited file size, which makes it impossible to use in busy scenery
regions.
Now to my system. I have created several "scenery.cfg" files for the
different regions of the world I want to fly in, viz:
CANADA (my bias) - includes Canadian airports plus some principal
airports in the States, particularly down the two seaboards,
including Alaska; all relevant mesh scenery.
NORTH AMERICA - includes US airports plus some principal airports in
Canada and Mexico; all relevant mesh scenery.
CARIBBEAN/CENTRAL AMERICA - includes airports in those areas plus
some principal airports in the States on the western, eastern and
southern seaboards; all relevant mesh scenery.
EUROPE - includes European airports and some principle airports in the UK.
UK - includes UK airports and some principle airports in Europe; all
relevant mesh scenery.
ASIA - so far this includes Japan, Hong Kong, China, Malaysia etc.;
all relevant mesh scenery.
OCEANA - so far this includes New Zealand, Australia, Indonesia,
Malaysia; all relevant mesh scenery.
AFRICA - so far this includes Capetown, Nairobi, Kilimanjaro, Lagos,
Cairo; all relevant mesh scenery.
WORLD - only the principal airports around the world where I might
want to fly trans-ocean or trans-continental flights; all relevant
mesh sceneries.
DEFAULT - most important to have the original "pristine" FS2000
"scenery.cfg" file with no add-ons, not even mesh!
I have also created another couple of "scenery.cfg" files, one called
DEMO since I have demonstrated FS2000 to computer clubs and it is
convenient having a minimum size "scenery.cfg" file for only the
scenery to be used in the demo. And TEST which I use for testing my
new scenery design (which I have not succeeded at yet but I am still
trying).
So how do I do it:
- Create a folder called "world" in your drive of choice; I put
mine in G: drive, which is where I have FS2000 installed.
- Inside this folder create a folder called "bup" - short for
"back-up"; copy your current "scenery.cfg" file into this folder; we
can delete this folder when the whole process is complete.
- Inside the "world" folder, create a folder called "default".
- Start up FS2000, go to the scenery library and de-activate all
add-on sceneries and move all these layers to the top; exit FS2000 and
delete all these de-activated sceneries from the "scenery.cfg" file;
copy the "scenery.cfg" file to the "default" folder; open the
"scenery.cfg" file in Wordpad and on the top line type ;DEFAULT -
this now tells you what the file is and the ; stops FS2000 from trying
to read that line.
- Now, most important, within the "default" folder create a folder
called "bup" and this is where you will keep the back-up for your
individual regional "scenery.cfg" files; so copy your new
"scenery.cfg" file to the "bup" folder.
- Now let's create a regional "scenery.cfg".
- Copy the "scenery.cfg" file in world\bup back into FS2000 and
overwrite the existing modified "scenery.cfg" file.
- Inside the "world" folder, create a folder called "canada" - for
Canadian regional sceneries/airports (or you could create another
region you want to fly in, with its own name).
- Start up FS2000, go to the scenery library and de-activate all
add-on sceneries AND MSFS default sceneries that you do not want to
be in your Canada region (however do not remove the following
defaults since they are universally used:
[Area.001] World Scenery
[Area.002] FS2000 Default Scenery
FS2000 Propeller Objects
FS2000 Airport Libraries
FS2000 Generic Libraries
FS2000 Vehicle Libraries
FS2000 Airport and Facilities Data
FS2000 Additional Facilities Data
(the latter six are best left above any mesh scenery)
- Move all these layers to the top; exit FS2000 and delete all these
de-activated sceneries from the "scenery.cfg" file; copy the
"scenery.cfg" file to the "canada" folder; open the "scenery.cfg"
file in Wordpad and on the top line type ;CANADA - this now tells you
what this file is and the ; again stops FS2000 from trying to read that
line
- Now, again most important, within the "canada" folder create a
folder called "bup" and copy your new "scenery.cfg" file for Canada
to its "bup" folder
Now repeat this process for the other regional areas above, or the
regional areas you want to fly in, i.e., create the regional folder,
its "scenery.cfg" file and its backup folder for each region.
Now you are ready to create the batch files. The purpose of the batch
file is to copy the "scenery.cfg" file for the region you want to fly
in, into the FS2000 folder. The first batch file will have to be
created in DOS but once one is up and working, it is easy to create
all the others in Windows. A small working knowledge of DOS is
required. Let's do the Canada batch file first.
Firstly, create a folder in the FS2000 folder called "test"; this is
your practice folder before copying the "scenery.cfg" to FS2000.
Open MS-DOS from the prompt in Windows; make sure it is showing the
C: prompt; then type "edit"; a screen with typical menu will appear,
click on "file" then "new".
Type the following lines:
g:
cd \world\canada
copy "scenery.cfg" g:\fs2000\test
g:
then hit ctrl-Z
then enter
then save-as "canada.bat" (without the " ")
These entries above assume the file structure I am using for FS2000;
you will have to modify these entries according to your own file
structure.
Exit MS-DOS then copy the "canada.bat" from "c:" into your new
"world" folder. The bat file icon should have a golden cogwheel.
Now we will create a "default.bat" file, but this is a lot easier
than the above process. Make a copy of "canada.bat" and rename it to
"default.bat" and place it in the "world" folder. Right click on its
icon and left click on "edit"; now change the canada entries to
default entries. It should read like this:
g:
cd \world\default
copy "scenery.cfg" g:\fs2000\test
g:
Now for the moment of truth. Double click on "canada.bat" and
wondrous things should happen on the screen in a MS-DOS window; when
finished review what's there then close the MS-DOS window and go to
the FS2000\test folder, open it and see if your Canada "scenery.cfg"
file is there. If so, well done! Now let's try a double click on the
"default.bat" file and check in the FS2000\test folder. If
everything has been entered correctly the default "scenery.cfg" file
should have overwritten the Canada "scenery.cfg" file. If all is
working you can delete the \test in the two bat files. This means
the "scenery.cfg" files will now be copied directly to your FS2000
folder.
You now repeat this process for all the regions you want to create
for your own flying preferences. When all is working properly, you
can delete the original "bup" folder that you put your starting
"scenery.cfg" file in.
Several Warnings!
- Always make sure the correct regional "scenery.cfg" file is in
FS2000 before adding a new scenery.
- After adding a new scenery and placing it in its correct layer and
you have confirmed it is working properly, then copy the
"scenery.cfg" file from FS2000 to its correct regional folder,
otherwise you could lose your latest entry.
- Periodically, copy the "scenery.cfg" in a regional folder into its
own "bup" folder to safeguard your new entries.
I also use this technique of batch file interchangeability for
alternative textures such as those of
Lennart Arvidsson and
Ruud Faber.
Nigel Grant
pngrant@smartt.com
Learn more
about adding scenery by reading this addendum.