ILS not aligned with runway

[Barrykensett]

I am having problems with ILS not lining up with runway, I am not talking about offset ILS or small deviation due to magnetic variation, I am talking about straight approaches which land half a mile to the left of the runway, a typical image here showing ILS needles aligned but through the windscreen the runway is off to the right. The second image of the ND shows the deviation from correct track.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12637&stc=1

http://www.mycockpit.org/forums/attachment.php?attachmentid=12638&stc=1

The Sim is P3Dv4 , sceneries are FTX Global, FTX Global Vector, FTX openLC Europe, FTX England
The pictures show approach to EGNJ20 which has UK2000 scenery, the same problem occurs on other UK2000 airports, default airports and FTX EGHI.
The problem does not appear for Zurich or Adelaide, it seems to be confined to England but I have not flown every airport.
For this reason I suspected FTX England but having posted on the Orbx forum the view there is that is not an Orbx problem, suggested something to do with Jeehell and handling of Navdata (I have latest Navigraph loaded).
On the chattersphere I hear others with similar problem.
Has anyone any knowledge to share?

Barry
www.a320sim.com

[michael1508]

sounds strange. I do have the same software and scenery installed (all but Vector) and will test it from my system tommorrow.

Any preferred Airport? EGNJ 20?

Michael

[Barrykensett]

sounds strange. I do have the same software and scenery installed (all but Vector) and will test it from my system tommorrow.

Any preferred Airport? EGNJ 20?

Michael
Thanks for your interest, EGNJ 20, EGCC 23R,EGHI 20 are typical examples.
Barry

[michael1508]

Hi Berry,

my approach on EGNJ 20 was perfectly aligned.

JL B50.0
Orbx England
Open LC

Michael

[Barrykensett]

So that more or less eliminates a scenery error, the data shows up the runway in the ND as being correct so the problem seems to be that the ILS needles are in the wrong place but the aircraft is correctly following them. Jeehell has been reloaded and recently updated. Looking for more ideas!
Thanks for your help.
Barry

[michael1508]

you tried rebuilding the.bin files, didn't you?

[Barrykensett]

Yes I rebuilt the bin files many times but I am still wondering if the problem is somewhere in that area. I think I will try copying the data directly into the Navdata folder rather than letting it update automatically.
Not sure if affects anything but I am using a remote server and looking back I wonder if that is what started the problem.
Flew into Corsica last evening and it auto landed perfectly, very strange.
Barry
www.a320sim.com

[jeehell]

Hi Barry

Did you build the navdata using admin rights? Best way is to run only FMGS_server.exe from it's folder (by default c:\A320FMGS\FMGS Server ) with right click -> run as administrator.

Also check c:\A320FMGS\Navdata\fsscenery.cfg if the path there point to your P3Dv4 install paths.it can be a problem if you had older P3D versions or even fsx installed.

Lastly, if it happens again, in the log folder you should have a logNDB.txt file. I will need it's content just after you rebuild the navdata!

Regards
Jean Luc

[Barrykensett]

Jean Luc
Thank you for your interest.
I deleted the bin files and ran the server.exe as administrator. (I usually start FMGS as admin to do the update so I can change my procedure)

My scenery cfg is as follows:

[Scenery]
scenery.cfg=
FSfolder=
AerosoftPath=C:\Users\Barry\AppData\Roaming\JeeHellWare
ip=127.0.0.1

i deleted this and ran FMGS setup again and the same file was created. Should I insert the paths manually?

i tested the sim at EGNJ20 and the ILS landing was still to the left of the runway.

I then copied the log file:

*21:44:01* Navdata module launched Server

*21:44:01*
*21:44:06*
*21:44:06* Navdata1:
*21:44:06* -ARPTliste:14045
*21:44:06* -NavaidListe:16965
*21:44:06* -FIXliste:260724
*21:44:06* -AWYsegments:98884
*21:44:06* -MarkerList:1470
*21:44:06* -Holds:23093
*21:44:06* -RWYS:34420
*21:44:06*
*21:44:06* Navdata2:
*21:44:06* -ARPTliste:14046
*21:44:06* -NavaidListe:16961
*21:44:06* -FIXliste:260773
*21:44:06* -AWYsegments:99061
*21:44:06* -MarkerList:1483
*21:44:06* -Holds:23022
*21:44:06* -RWYS:34430
*21:44:06*
*21:44:06* server started on port:8006
*21:44:53* Client connected: 192.168.1.101
*21:45:05* Client connected: 192.168.1.83
*22:02:10*
*22:02:10* Module stopped normally

.83 is the FS PC
.101 is the ND and PFD PC

Does this make any sense?

Regards
Barry

[jeehell]

Hi

yes you must have those paths filled in, I have no clues why they are not setup automatically.
They should look like
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v4\scenery.cfg
FSfolder=C:\Program Files\Lockheed Martin\Prepar3D v4

Then delete all .Bin and rebuild as I described earlier.

[Fritz]

...
[Scenery]
scenery.cfg=
FSfolder=
AerosoftPath=C:\Users\Barry\AppData\Roaming\JeeHellWare
ip=127.0.0.1
...


If P3D runs on a dedicated computer, the ip adress should be the adress from the dedicated computer ?

Best regards

[jeehell]

here the IP should be of the FMGS serve

[Barrykensett]

My file now looks like this
[Scenery]
scenery.cfg=\\PC1\C:\ProgramData\Lockheed Martin\Prepar3D v4\scenery.cfg
FSfolder=\\PC1\Lockheed Martin\Prepar3d v4
AerosoftPath=C:\Users\Barry\AppData\Roaming\JeeHellWare
ip=127.0.0.1

i rebuilt the bin files and tried again. Still landing to the left on my test airport but I will do some more rests.
just for interest where does the Aerosft entry come from?
Barry

[jeehell]

No you can't build the navdata remotely from P3D. It has to be done on the P3D computer directly (the server is installed there by default even if not used). Then you copy the bin files from P3D computer.

The aerosift entry comes from when only them provided data in my format...

[Barrykensett]

I assumed that when I moved the server that I moved the Navdata with it and I updated in the remote PC.
i have now updated in the FS PC and copied across as you said.
On limited testing do far I think my problem is fixed. Thanks for the help.
Barry