in between I suppose FSNavdbc does not recognize ADE or AFX files, only AFCADs and default sceneries ???

No, it doesn't matter how an AFD file is named, FS Navigator will still identify it. However, some files (such as separate exclude files or taxi sign files) also carry headers which FSN will identify as AFD files. As it only reads the first such file it comes to, and then moves on to the next scenery, this can lead to the real AFD file being ignored. The trick here is again to move the AFD to another layer where it will be scanned after the other ones.

 

Best wishes,

 

John

Hello:

 

To set the date in the environment for only ex: 1 individual task session such as FS2004 running ex: FlightSim Manager: (without changing the overall system time for Windows itself), you can use NirSoft's freeware "RunAsDate" utility: :Idea:

 

"RunAsDate is a small utility that allows you to run a program in the date and time that you specify. This utility doesn't change the current system date and time of your computer, but it only injects the date/time that you specify into the desired application"

 

http://www.nirsoft.n...un_as_date.html

 

UnZip the appropriate downloaded 32-bit RunAsDateZIP or 64-bit RunAsDate-x64.ZIP file into the [FlightSimManager install path] folder.

 

Then follow the instructions in the included ReadMe and *.CHM help files; browse for FlightSimManager.exe as the "Application To Run"

 

IIRC, seting "Date / Time" in RunAsDate at 11/30/2005 or earlier allows FlightSim Manager to run.

 

...

 

GaryGB

 

Thank you much for this info. I've been using the FSM patch for years, not really liking the way it bounces the system time. This is much better and more direct to the app itself. It did take me a few minutes to realize, even though I'm on Win7_x64, I still had to use the 32 bit version of the RunAsDate utility to work with FSManager. I also notice how much faster FSManager starts with this utility than using the patch.

 

IMO, FSManager has the best scenery library manager utility - it's the only thing I use it for. I wish there was a way to make it work with the scenery.cfg directly located under th appdata path, instead of the FSX root path. I still have to remember to copy the cfg before and after using the FSManager.

No, it doesn't matter how an AFD file is named, FS Navigator will still identify it. However, some files (such as separate exclude files or taxi sign files) also carry headers which FSN will identify as AFD files. As it only reads the first such file it comes to, and then moves on to the next scenery, this can lead to the real AFD file being ignored. The trick here is again to move the AFD to another layer where it will be scanned after the other ones.

 

Best wishes,

 

John

 

most valuable info (because it is correct!)

 

from process monitor I got the info that FSNavDBC processes the bgls in reversed alphabetically order.

So I renamed AF2_edbk1.bgl to ZAF2_edbk1.bgl

 

and now the file was processed first and no longer ignored

 

:excl:

 

For these tests I had only a small part of my layers active to avoid the annoying hang ups (CPU loops!) with some

of my sceneries ...

 

(I have a Vista 64 with 8GB memory and a Core 2 E8500 CPU at 3.5GHz)

 

the hang ups appear at different sceneries. Some are more often involved, it is very strange ...

 

So re-creating the whole FSNav Database can take a lot of hours :angry:

 

regards

Guenther

 

P.S.: the tips and tricks on your homepage are very valueable too

So re-creating the whole FSNav Database can take a lot of hours

Yes, indeed it can but once you have got it right, you should be fine. Occasionally if you add a new scenery you need to do a little shuffling.

 

For me it is worth the effort, because the FSN map is so useful.

 

John

I got it now, just 10min ago!

 

and I solved some layers by my renaming.

 

"zzz" is even better than "Z" when bgls have lower case names ...

 

greetings from Bavaria

Guenther