ILS LOC not appearing or capturing

[saustin89]

Gday All,

Currently on the latest version of FMGS

We aren’t seeing the magenta bugs for LOC and it never captures the LOC on an ILS.

Photo attached

[saustin89]

Photo of no LOC on approach

[jeehell]

Seems either a navdata issue (compilation or data itself) or a manually tuned ILS? Are you visually aligned with the runway?

[saustin89]

Did some testing.

Reloaded Navdata 2410.

Doesn’t capture the LOC from HDG or NAV mode.

Aligns if we’re in NAV mode but doesn’t capture. Tried manually tuning as well, no difference.

[jeehell]

Is this on all airports / runways? what is the airport used on your picture?

[jeehell]

ok it is Canberra, I found it.
I don't have any problem with this ILS here, using Navigraph 2410.
Do you use an addon airport?
Post your FSScenery.cfg file.
Also please recompile one more time your bin files and post the c:\A320FMGS\logs\logNDB.txt right after bin files are created.
And let me know if it happens on other airports.

[saustin89]

Will do, thanks Jean Luc

[saustin89]

Here is our FSScenary.cfg, not really sure what it should look like as our FMGS Server is not located on the Prepar3d machine. Anyhow, we have shared the folders over the network.

image.jpg

We've rebuilt the Nav Data a couple of times now and have noticed that when programming the approach for ILS into YSSY 34L, with the ISN 110.10, JeeHell was loading the CRS as F309 when it should be F335. We also noticed that departing on RWY 25 the CRS was ~219 (Can't exactly remember but it was near 242 - ISW 109.7)

We still could not get the LOC to lock and there was no ILS horizontal diamond indicated, nor was there a chevron indicating it was either to the left or right.

Hope that helps.

[jeehell]

…
Do you use an addon airport?
...
Also please recompile one more time your bin files and post the c:\A320FMGS\logs\logNDB.txt right after bin files are created.
And let me know if it happens on other airports.

[Limelines]

Hi JL,
Apologies for the delayed response. We did manage to get it working, by updating the FSScenery.cfg. I ended up mapping the network drives to letter and updated the `FSScenery.cfg` to point to the correct locations. After waiting for the navdata to build the problem was solved.

[Scenery]
scenery.cfg=Q:\scenery.cfg
FSfolder=p:\
AerosoftPath=C:\USERS\JeeHell\AppData\Roaming\JeeHellWare
Add-ons.cfg=R:\Scenary\AppData\Roaming\Locheed Martin\Prepare3D v5\add-ons.cfg
Add-ons.cfg2=Q:\addon.cfg
ip=127.0.0.1

Once the navdata is build I copied it onto the individual pilot and co-pilot pcs? Is this still required or is the data sent over the network?

[jeehell]

Yes you need to copy the bin files.

[Limelines]

Hey JL,
Just trying to update the nav data for the new cycle and I cannot get the scanned bgl in the log to show folders other than 0.

All my paths seems to be right but it never seems to scan. FSScenary.cfg is as above.

image.jpg

image.jpg

Any thoughts? Do the paths that have spaces require quotes?
Thanks,
Jamie

[jeehell]

Are you sure your network mapped drives are still working?
They may not be working if you use admin rights and you set them up without admin rights.

[Limelines]

Hi JL,
I set them up with everyone read access. When I copy the path in the FSScenery.cfg into the file explorer the location opens and the drives are accessible from explorer.

I’ll try running without admin rights.

Update, yep that seemed to work. So something with running the starter as non admin worked but as admin did not work.

Thanks the the idea, not sure why that worked though

Kind regards,
Jamie

[jeehell]

This has to do with windows.
I have some network mapped drives as well for some other stuff, and use some command line script to set the drives. Whenever I reboot, I need to run the script twice (with & without admin rights).

[Limelines]

Wow, that’s wild. Any chance your working on a Linux version?

Thanks for your help and quick response. Much appreciated.

[jeehell]

No nothing related to linux