A320 FMGS B47

**fisfro** · 06-12-2017, 06:03 PM

Originally Posted by jeehell

and post your c:\A320FMGS\logs\logNDB.txt

here it is:
*10:36:52* Navdata module launched Server
*10:36:52*
*10:36:54*
*10:36:54* Navdata1:
*10:36:54* -ARPTliste:13804
*10:36:54* -NavaidListe:17088
*10:36:54* -FIXliste:254238
*10:36:54* -AWYsegments:96473
*10:36:54* -MarkerList:1586
*10:36:54* -Holds:21098
*10:36:54* -RWYS:34065
*10:36:54*
*10:36:54* Navdata2:
*10:36:54* -ARPTliste:13804
*10:36:54* -NavaidListe:17088
*10:36:54* -FIXliste:254238
*10:36:54* -AWYsegments:96473
*10:36:54* -MarkerList:1586
*10:36:54* -Holds:21098
*10:36:54* -RWYS:34065
*10:36:54*
*10:36:54* server started on port:8006
but the date of this file seems to be old - ist from 26th of March 2017 - so it seems that this info will not help very much - right ?

**fisfro** · 06-12-2017, 06:05 PM

[QUOTE=fisfro;168440]here it is:

Originally Posted by jeehell

and post your c:\A320FMGS\logs\logNDB.txt

here it is:
*10:36:52* Navdata module launched Server
*10:36:52*
*10:36:54*
*10:36:54* Navdata1:
*10:36:54* -ARPTliste:13804
*10:36:54* -NavaidListe:17088
*10:36:54* -FIXliste:254238
*10:36:54* -AWYsegments:96473
*10:36:54* -MarkerList:1586
*10:36:54* -Holds:21098
*10:36:54* -RWYS:34065
*10:36:54*
*10:36:54* Navdata2:
*10:36:54* -ARPTliste:13804
*10:36:54* -NavaidListe:17088
*10:36:54* -FIXliste:254238
*10:36:54* -AWYsegments:96473
*10:36:54* -MarkerList:1586
*10:36:54* -Holds:21098
*10:36:54* -RWYS:34065
*10:36:54*
*10:36:54* server started on port:8006
but the date of this file seems to be old - ist from 26th of March 2017 - so it seems that this info will not help very much - right ?

**fisfro** · 06-12-2017, 06:16 PM

Hello JH,

bin files have been produced

- I have restarted everything and manualy started th fmgsserver
Also recalibration was succesfull - so thanks very much

Robert

**Leonidas** · 06-13-2017, 11:54 AM

This ILS LOC again... Almost every runway's LOC is wrong.

What I've done so far:

1. Rebuild 1706 bin files
2. Update fixes, NAVAIDs and Magvar data from www.aero.sors.fr
3. Try 1705 AIRAC
4. Disable scenery addons

Still many meters away from right path!!!
Something else happens, but what?

**spiliot** · 06-13-2017, 01:05 PM

Leonidas this might be far fetched but reminds me a similar crazy error from the past. Do you have greek regional number settings on your computer? Would you mind switching everything to english and trying rebuilding everything again? Greek use comma for decimal separation and dot for thousands separation (1.234,56) which messes up calculations with numbers in english (1,234.56) when localization is not taken into account.

**Leonidas** · 06-13-2017, 03:00 PM

Originally Posted by spiliot

Leonidas this might be far fetched but reminds me a similar crazy error from the past. Do you have greek regional number settings on your computer? Would you mind switching everything to english and trying rebuilding everything again? Greek use comma for decimal separation and dot for thousands separation (1.234,56) which messes up calculations with numbers in english (1,234.56) when localization is not taken into account.

Wow !!! yes I do, even though the enviroment is English. I had no problem in v.3.4, but anyway I'll try it tomorrow.
Thanks a lot

**jeehell** · 06-13-2017, 03:55 PM

Originally Posted by Leonidas

This ILS LOC again... Almost every runway's LOC is wrong.

What I've done so far:

1. Rebuild 1706 bin files
2. Update fixes, NAVAIDs and Magvar data from www.aero.sors.fr
3. Try 1705 AIRAC
4. Disable scenery addons

Still many meters away from right path!!!
Something else happens, but what?

Once again, you need to do the ILS/RWY fix. It is the only fix needed from aero.sors.fr, the other may be nice for your other addons. But my software only needs the ILS/RWY fix https://www.aero.sors.fr/navaids3.html

Also make sure you use admin rights, and your path in the c:\A320FMGS\navdata\fsscenery.cfg are correct.
The scenery.cfg path MUST include the scenery.cfg name!! (so it looks like scenery.cfg=c:\programdata\lockheed martin\prepar3d vx\scenery.cfg usually....)

**Gregor** · 06-14-2017, 12:10 PM

Hi JL

What are the correct entries in fsscenery.cfg in a networked configuration?

Cheers
Greg

**jeehell** · 06-14-2017, 12:17 PM

The correct entries are the same, because in a network configuration you still must build the navdata on the P3D PC. This setup IS complex, it requires you to manually copy the FMGS Server over to the P3D PC, build the navdata, etc...

**dkreiskott** · 06-14-2017, 12:36 PM

Hi All,

I have made a little tool that helps to create the navdata and distribute it to other PC's like FO and CPT Computers.
If a dedicated FMGS Server is in the Network, the tool can distribute the Navdata too.
It also checks the path for the scenery.cfg configured in FSscenery.cfg.
If the scenery.cfg can not be read it informs you.

After an update of the airac the tool can be started.
Then it makes the following steps automatically

1. Checks the fsscenery.cfg
2. delete the old navdata files
3. starts FMGS Server and wait for the process that all *.bin files are created
4. delete the navdata files on the Client computers
5. Copy all the required new files to the computers in the Network

It's easy to configure, only Network Shares are necessary.

For me it works in the Network. I would be glad if someone would like to test the tool.

Regards Dieter