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
Printable View
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
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
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
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
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
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.