Localiser alignment and general database issues (solution)

[Soarbywire]

If you are having issue with the localiser alignment or general database issue ensure the scenery paths are correct.

A320FMGS\navdata\FSScenery.cfg

The database will not build correctly if the path for P3D has been incorrectly set.

Ensure you delete the 11 *.bin files in A320FMGS\navdata and FMGS will rebuild them the next time you restart.

You will need to copy all the *.bin files to the navdata folder in all client computers where you have setup PFD/ND (EIS.exe) screens.

Note - Jeehell FMGS monitors the default Navigraph install folder and will automatically update the database recreating the *.bin files when you update the cycle.

More information on displaced ILS here - https://forum.navigraph.com/t/displaced ... graph/4471 (Thank you Rainer)

[bbruechmann]

Ensure you delete the 14 *.bin files in A320FMGS\navdata

ehm... aren´t these only 11 bin files?! Or did i miss something?

Regards
Bernd

[Soarbywire]

Actually I just double checked the manual and it says 10 .bin files. Corrected to 10.

Thanks.

[Mato68]

I also have 11
ARPT
AWY
FIX
HOLD
MKR
MORA
NAVAID
NAVDB
PROC1
PROC2
RWY

[balu69]

Hello Soarbywire
I have the MCDU, PFD and ND on a second PC and have never copied the BIN files until now and everything worked fine in my opinion.
what is the purpose of copying these BIN files?

[Soarbywire]

Hello Soarbywire
I have the MCDU, PFD and ND on a second PC and have never copied the BIN files until now and everything worked fine in my opinion.
what is the purpose of copying these BIN files?

Perhaps with the new EPGWS implementation this is no longer needed.

[jeehell]

It's less critical that in quite older versions, though it cannot do ham to copy the navdata. I don't recall which app do need those

[michael1508]

I am still having an issue.

Since reinstalling FMGS on my main P3D PC, I am missing a number of SIDs and STARs.
For example., for EDDL 5R there are no SIDs shown at all.

All paths in FSscenery are set correctly.
If I regenerate the .bin files, it goes pretty fast (much faster than usual).
According to the logNDB the number of file look good to me, but maybe someone with Navigraph AIRAC can doublecheck:

*18:14:12* Navdata1:
*18:14:12* -ARPTliste:13753
*18:14:12* -NavaidListe:16334
*18:14:12* -FIXliste:230484
*18:14:12* -AWYsegments:104877
*18:14:12* -MarkerList:1134
*18:14:12* -Holds:26926
*18:14:12* -RWYS:34890

Thanks

[jeehell]

Try running FMGs server with admin rights and with p3d closed.
Check your antivirus does not prevent anything as well.

[michael1508]

I have turned FW and AV off on all machines.
Running FMGS as Admin on all machines.

Recreated again the .bin files.
Unfortunately still not seeing any SID's for EDDL 5R...

This is my FSscenery.cfg on the P3D main pc:

[Scenery]
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v5\scenery.cfg
FSfolder=P:\P3Dv5
AerosoftPath=C:\Users\A320\AppData\Roaming\JeeHellWare
Add-ons.cfg=C:\Users\A320\AppData\Roaming\Lockheed Martin\Prepar3D v5\add-ons.cfg
Add-ons.cfg2=C:\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg
ip=192.168.178.12

The IP is of the FMGS server pc.

[jeehell]

If you can share with me only your navdrecord from aerosoft?
Is it only on add on airports?

[michael1508]

If you can share with me only your navdrecord from aerosoft?
Is it only on add on airports?

I use Navigraph data on Navdata 1 as my main database and an old Aerosoft AIRAC on Navata 2 as a backup. But the Aerosoft link from the scenery.cfg is not used. The folder doesn't exist. For every new AIRAC I just copy the data for both Navdata folders from another drive.

After my first unscussesful trials with Navigraph data on Navdata1 only, I restored the main fmgs/Navdata folder from a backup from last week, where all worked great. However,even with this data and redistributing the old .bin files across all pc, it does not work.

Do you still need the navrecord.dat file? IF yes, how can I share with you?

Thanks for your support!

[michael1508]

I have updated to B57.1.3, just installed over the existing version. This has solved the Navdata issue.

Not sure, what happened here. However I am now running again into my previous issue of no liftoff, which I have since trying B57.
I will open a new thread for this.

Thanks

[D-AJMF]

Hello,

what is if Jeehell server and P3D are installed on different PCs?
I do so, I've shared the folder C:\ProgramData\Lockheed Martin\Prepar3D v5 of the P3d-PC and set the Path accordingly to that A320FMGS\navdata\FSScenery.cfg file, but I still have issues.

Jean Luc, do you know if there is an Issue if these PCs are different for server and P3d?

Kind regards
Michael

[michael1508]

Hi Michael,

this perfectly works. Follow the 'how to' in the Jeehell Advanced SetUp guide

[bbruechmann]

Hello,

what is if Jeehell server and P3D are installed on different PCs?
I do so, I've shared the folder C:\ProgramData\Lockheed Martin\Prepar3D v5 of the P3d-PC and set the Path accordingly to that A320FMGS\navdata\FSScenery.cfg file, but I still have issues.

Jean Luc, do you know if there is an Issue if these PCs are different for server and P3d?

Kind regards
Michael

Important: make sure you create the bin files on the P3D PC! Then copy them to the FMGS-Server PC after they created.

[SIM320]

I have an issue in my Fmgs Airbus concerning ils, not solved
after having read the above posts.
I see glide slop on ND that does not work.
The magenta diamond ils (localizer) is not shown on nav display or sometimes it is out in a very wrong position (not aligned) but, for an unknown reason to me, guidance is usually engaged by FCU and only the horizontal path works.
The NAV and PFD DISPLAYS are installed in client pc 1.
Fmgs server is installed in pc 2 (not P3d v5) where the two MCDU are connected, correctly configured and working.
P3d in a separate machine - pc3.
Cockpit hardware by Skalarki.
Navigraph nav data file correctly set in folders nav1 and nav2 in fmgs server pc 2 and in the corresponding folders in NAV and PFD DISPLAYS pc 1.
Bin files deleted and regenerated in FMGS SERVER pc 2 then copied in NAV and PFD DISPLAYS pc1.

I don’t understand why ILS does not duly work since I installed the last released version of FMGS AIRBUS.
Can someone help me indicating the exact content of scenery.cfg file to be found in Fmgs navdata folder in each of my three different pc, according to the above mentioned distribution of resources I made?
Any way, which IP should be found in the scenery.cfg
(intended the file inside fmgs navdata folder in the different pc)?
Many thanks for a kind help.
Best regards.
Massimo


P3d v5

[SIM320]

I have an issue in my Fmgs Airbus concerning ils, not solved
after having read the above posts.
I see glide slop on ND that does not work.
The magenta diamond ils (localizer) is not shown on nav display or sometimes it is out in a very wrong position (not aligned) but, for an unknown reason to me, guidance is usually engaged by FCU and only the horizontal path works.
The NAV and PFD DISPLAYS are installed in client pc 1.
Fmgs server is installed in pc 2 (not P3d v5) where the two MCDU are connected, correctly configured and working.
P3d in a separate machine - pc3.
Cockpit hardware by Skalarki.
Navigraph nav data file correctly set in folders nav1 and nav2 in fmgs server pc 2 and in the corresponding folders in NAV and PFD DISPLAYS pc 1.
Bin files deleted and regenerated in FMGS SERVER pc 2 then copied in NAV and PFD DISPLAYS pc1.

I don’t understand why ILS does not duly work since I installed the last released version of FMGS AIRBUS.
Can someone help me indicating the exact content of scenery.cfg file to be found in Fmgs navdata folder in each of my three different pc, according to the above mentioned distribution of resources I made?
Any way, which IP should be found in the scenery.cfg
(intended the file inside fmgs navdata folder in the different pc)?
Many thanks for a kind help
Best regards.
Massimo


P3d v5

[bbruechmann]

Bin files deleted and regenerated in FMGS SERVER pc 2 then copied in NAV and PFD DISPLAYS pc1.

Important: make sure you create the bin files on the P3D PC! Then copy them to the FMGS-Server PC after they created.

[SIM320]

Thanks Bernd,
please, can you say me how to do it?
What is the action to do?
Many thanks for your help.
Best regards
Massimo

[bbruechmann]

make sure, you have the paths to P3D and the add-ons etc. correctly set in the scenery.cfg in the navdata folder of FMGS on the Machine where you run P3D itself.
Make sure, no bin files are in de Navdata folder. run only fmgsserver.exe with admin rights on this computer and wait until the 11 bin files are created. Then copy these bin files to your Computer where you run the FMGS software and to the PC where you run the PFD/ND portion.

[SIM320]

Many many thanks!
I will do it.
Best regards
Massimo

[thierryd]

I had what seems to be a very similar issue in the past. It got resolved by making sure I was running FMGS Server with Administrator rights (as indicated by Bernd). I just wanted to stress that point.

[SIM320]

Thierry, please,
could you post me the content of your scenery cfg in FMGS server and Fmgs in P3d pc?
Many thanks in advance if you can.
Nice day
Massimo

[thierryd]

Here is the content of my FSscenery.cfg file in the Navdata folder on the P3D computer, which in my case is also running the FMGS Server:
[Scenery]
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v5\scenery.cfg
FSfolder=C:\Prepar3D v5\
AerosoftPath=C:\Users\Thierry\AppData\Roaming\JeeHellWare
Add-ons.cfg=C:\Users\Thierry\AppData\Roaming\Lockheed Martin\Prepar3D v5\add-ons.cfg
Add-ons.cfg2=C:\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg
ip=127.0.0.1

Here is the content of my FSscenery.cfg file in the Navdata folder on the computer running the (FO) MCDU and PFD/ND:
[Scenery]
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v5\scenery.cfg
FSfolder=C:\Prepar3D v5\
AerosoftPath=C:\Users\Thierry\AppData\Roaming\JeeHellWare
Add-ons.cfg=C:\Users\Thierry\AppData\Roaming\Lockheed Martin\Prepar3D v5\add-ons.cfg
Add-ons.cfg2=C:\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg
ip=192.168.1.121

In this file the IP address is the one of my P3D/FMGS Server computer.

And here is the content of logNDB.txt file in the Logs folder on the P3D computer, which in my case is also running the FMGS Server:
*10:21:08 AM* Navdata1:
*10:21:08 AM* -ARPTliste:13762
*10:21:08 AM* -NavaidListe:16391
*10:21:08 AM* -FIXliste:230924
*10:21:08 AM* -AWYsegments:104856
*10:21:08 AM* -MarkerList:1131
*10:21:08 AM* -Holds:27154
*10:21:08 AM* -RWYS:34915
*10:21:08 AM*
*10:21:08 AM* Navdata2:
*10:21:08 AM* -ARPTliste:13753
*10:21:08 AM* -NavaidListe:16334
*10:21:08 AM* -FIXliste:230484
*10:21:08 AM* -AWYsegments:104877
*10:21:08 AM* -MarkerList:1134
*10:21:08 AM* -Holds:26926
*10:21:08 AM* -RWYS:34890
*10:21:08 AM*

This is with:
AIRAC cycle : 2212
Version : 1
Valid (from/to): 01/DEC/2022 - 29/DEC/2022

All files are generated on the P3D computer as described in the posts above, then copied to my two client computers, one for the FO. one for the Captain.