scenery.cfg...the best approach?

[jwight]

I am wondering how to best structure my addon scenery directory and the scenery.cfg file for best performance. I currently have 197 entries in my scenery.cfg file. Does anyone know the limit?

I have a sub-directory with scenery and texture folders for every add-on scenery. For those states or countries that have a number of add-ons I have a state folder with seperate city folders in it. For example, I have addon scenry/Alaska/ and then I have 26 seprate loctions in Alaska, each with an entry in the scenery.cfg file. I am considering dumping all of the Alaska sites into one set of scenry and texture folders under Alaska and only having one Alaska entry in my scenery.cfg file. I would then do this for the other 22 sub-directories I have in the addon scenery directory. This would cut down dramatically on the number of entries in the scenery.cfg file.

Has anyone experimented with this? Does anyone know what should work best in FS2002?

Thanks,

Jim
wightjim@yahoo.com

[rcbarend]

Hi Jim,

I had the same question, but answered it for myself.

I believe FS2000 had a problem with large amounts of entries in the scenery.cfg file (>200), but I haven't seen or heard this for FS2002.

I think the only advantage of bundling sceneries into one folder could be a faster FS2002 startup time; I have tried this for 80 addon sceneries but didn't notice any difference in startup speed.

So I decided not to bundle them.
Also, disadvantages of bundling sceneries are:
- Number of flatten statements is still limited
(excludes are usually put in exclude .bgl's nowadays)
- Possible filename clashes
- and most important: maintenance.
If you want to add a new version of an addon scenery, or have to remove an existing one, it's very difficult to find out which files belong to which scenery.

Rob