Sudden "Scenery not found" calls on start up

[Miggers]

Gents,
I must've been poking around "in the back" so to speak and now have 16 "scenery not found" errors to sort out.

I seem to recall there used to be a scenery management repair programme for this kind of thing but what it was and where it could be found
has obviously been lost in the mists of time to me.

Any of our resident scenery gurus any ideas please?

Ta,Miggs

 

[wolfebee89]

Perhaps give FS Scenery Config Editor a try: https://sourceforge.net/projects/fs-sceditor/ and the related user documentation: https://fs-sceditor.sourceforge.net/index.html

the particular error check that you require: https://fs-sceditor.sourceforge.net/listview.html
verbatim from the documentation "Should an area have an error, a red warning triangle will appear in the column which where there is a problem, and information explaining the error will be placed in the Errors column. The main errors that get shown like this include [amongst several]...if you have the check scenery directories exist option set, Areas where the directory the path relates to cannot be found. (Triangle appears in the path column.)"

cheers

 

[Mick]

You can check your scenery.cfg for the simplest errors without any program to do it.

Using this sample entry:

[Area.009]
Title=Eastern North America
Local=Scenery\NAME
Remote=
Active=TRUE
Required=FALSE
Layer=9

Make sure your [Area.###] numbers are in proper sequence and there no gaps.

Make sure your [Area.###] and Layer numbers match.

Make sure your Titles exactly match your scenery folder names and that you don't have any missing scenery folders.

Make sure your Local= pathway is correct.

 

[Sbob]

If you just started having problems, I would strongly suggest checking you scenery.cfg file manually, first.
As Mick wrote, having the AREA number match with the LAYER number is ideal BUT it isn't always true.
FS itself will change the LAYER number when you use its built-in scenery manager but leave the AREA number alone.

The resulting mess will be worse than trying to guess the password for a crypto wallet.

Better yet, what were you messing with when the problem began? That's what is probably causing your hassles NOW.
Manual editing can be time consuming but it is also VERY accurate. Open your scenery.cfg file with NOTEPAD and give it a quick scan.
Find the biggest LAYER number then use NOTEPAD's FIND function and search for that number. It should come up twice (AREA number and LAYER number). If it comes up three or more times, THAT's your problem. Keep working down with lower numbers until you find the problem. It might be two layers using the same number or a LAYER that is missing entirely.

The scenery layering programs work great when everything is lined up, they WILL make the problem worse if there is already a mistake.
Worst case, post a copy of your scenery.cfg file here (use the attach function) and I'll take a look at it.