Localizer offset

[steinbach72]

Hi, I noticed significant localizer offset inside P3Dv2 during landing after last update / tested on LOWW rwy 29 and LOWS rwy 16 /. Aircraft lands right next to the runway when using autoland. Thanks Jiri, Prague

[jeehell]

Hi,

Can you look on Server PC in the folder navdata if you have a file called oldILS.bin. If not, make sure everything is closed down (FS and FMGS) then run the application called navDBapp.exe (still in navdata folder). Let it run for a few minutes (until oldILS.bin file appears).

Regards,
JL

[steinbach72]

Hi,

Can you look on Server PC in the folder navdata if you have a file called oldILS.bin. If not, make sure everything is closed down (FS and FMGS) then run the application called navDBapp.exe (still in navdata folder). Let it run for a few minutes (until oldILS.bin file appears).

Regards,
JL

Hi JL, yes, I have oldILS.bin in this folder. I tried to remove it and run NaVDBapp.exe, but new file did not appear. Jiri

[jeehell]

Did you make sure you closed FS before running the application?
There is a log file called logNDB.txt. I need to see what's in it.

JL

[steinbach72]

Did you make sure you closed FS before running the application?
There is a log file called logNDB.txt. I need to see what's in it.

JL

Hi, yes sim was closed, but I noticed in logNDB.txt that there is route to FSX, but I use P3D now on another disc /D> Jiri

[jeehell]

In that case, you simply need to modify the FSscenery.cfg file to adjust the paths in there to your actual P3D paths. They should look like this on a W7 64bit:
scenery.cfg=C:\Program Files (x86)\Lockheed Martin\Prepar3D\scenery.cfg
FSfolder=C:\Program Files (x86)\Lockheed Martin\Prepar3D\

Then do the navdbapp.exe again (with P3D closed).

JL

[steinbach72]

In that case, you simply need to modify the FSscenery.cfg file to adjust the paths in there to your actual P3D paths. They should look like this on a W7 64bit:
scenery.cfg=C:\Program Files (x86)\Lockheed Martin\Prepar3D\scenery.cfg
FSfolder=C:\Program Files (x86)\Lockheed Martin\Prepar3D\

Then do the navdbapp.exe again (with P3D closed).

JL

Hi JL, everything changed by your advice, but still the same, the localizer offset during CAT 3 dual AUTOLAND tends to be worse and worse around 5 NM from the runway threshold, tested at LOWW rwy 29 default P3Dv2 scenery. Landed next to the runway [on the right side, wind is 8 knots slightly form the left]. GS capture works perfectly, localizer capture too at longer distance from threshold too. Do you have any other reccommendations? Thanks Jiri

[jeehell]

add this line to FSScenery.cfg:
MonitorARPT=LOWW

Then launch navdbapp (without P3D again) and put the logNDB.txt here again.


By the way, on PFD/ND, how is the LLZ deviation scale? Centered?

JL

[jeehell]

I've just tried with P3D 1.4 default scenery and it is a perfect ILS alignment and AUTOLAND.
So you probably have an issue with the navdata base installation process. Once I see your latest logNDB I should see what's happening more clearly.

[steinbach72]

I've just tried with P3D 1.4 default scenery and it is a perfect ILS alignment and AUTOLAND.
So you probably have an issue with the navdata base installation process. Once I see your latest logNDB I should see what's happening more clearly.

Hi, when I am standing on the runway before T.O. and tune ILS, localizer is perfectly aligned-centered. But during the autoland the localizer dot on PFD tends to shift to the left as I approach runway. Thanks Jiri