PDA

View Full Version : LOC signal & FSX runway center line



masterp
07-21-2015, 10:57 PM
Hi all,

I have noticed on some airports (addons & default sceneries), LOC signal and RWY center line are not matching.
eg, VVTS 25L (108.3/249) ; VVTS 25R (110.50/249) ; VVDN 35R (111.50/353)
Those LOC signals are working correctly when I fly with other aircraft models (Aerosoft, PMDG, FSX stock aircraft) However with Jeehell A320 & Navdatapro, Autoland brings my A320 to the grass instead of runway :roll:

Could you guys please help me to check on your sim? :cool:

Thanks & have a great day!
Vu

I attached 2 screenshots at VVTS&VVDN
http://www.mycockpit.org/forums/attachment.php?attachmentid=10420&stc=1http://www.mycockpit.org/forums/attachment.php?attachmentid=10421&stc=1

OmniAtlas
07-22-2015, 03:46 AM
Have you updated your magnetic variations?

http://flightsystem.wix.com/airbus#!Magnetic-Variation-Update/c1d1w/554893a30cf2731335169e1e

masterp
07-22-2015, 04:03 AM
Oh Thanks OmniAtlas (http://www.mycockpit.org/forums/member.php?u=17848)
I will update and report the result later :p

masterp
07-23-2015, 04:10 AM
Have you updated your magnetic variations?

http://flightsystem.wix.com/airbus#!Magnetic-Variation-Update/c1d1w/554893a30cf2731335169e1e

I have updated magnetic variations, however LOC & rwy center line still not aligned on some runways. Could you please check on VVTS 25L (108.3) 25R (110.5); VVDN 35R (111.50) :-o
Thanks

OmniAtlas
07-23-2015, 05:59 AM
I loaded up VVTS 25L and yes the localizer is slightly off the runway. This might be more of a scenery problem (using default P3D VVTS).

jeehell
07-23-2015, 10:45 AM
Masterp: please go into your A320FMGS\Navdata fodler on the server computer.
There, in the FSscenery.cfg add the line:
MonitorARPT=VVTS

then erase all the .bin files. Launch the software, wait for the navdata to load, then paste here the results in logNDB.txt file4.

I tried at VVTS on 25L&R, and at VVDN on 35R. I get a few meters off the centerline, but well on the runway. This may be an issue with the scenery.cfg path which is in your FSScenery.cfg file. make sure it points to the correct path, particularly if you use addon scenery.

JL

masterp
07-23-2015, 11:47 AM
Hi JL: Here is logNDB.txt as your suggestion:
*10:40:05 PM* Navdata module launched Server
*10:40:05 PM*
*10:40:05 PM* -BGL scan:
*10:40:05 PM* -ScenerycfgPath:
*10:40:05 PM* -FSroot:
*10:40:05 PM* -Folders Nb:0
*10:41:08 PM*
*10:41:08 PM* Navdata1:
*10:41:08 PM* -ARPTliste:15399
*10:41:08 PM* -NavaidListe:18172
*10:41:08 PM* -FIXliste:188902
*10:41:08 PM* -AWYsegments:98493
*10:41:08 PM*
*10:41:08 PM* Navdata2:
*10:41:08 PM* -ARPTliste:15399
*10:41:08 PM* -NavaidListe:18172
*10:41:08 PM* -FIXliste:188902
*10:41:08 PM* -AWYsegments:98493
*10:41:08 PM*
*10:41:08 PM* server started on port:8006
*10:41:08 PM* Client connected: 127.0.0.1
*10:41:08 PM* Client connected: 127.0.0.1
*10:41:16 PM* Client connected: 192.168.0.105





Ahhh I found that FSScenery.cfg shown P3D path, while I am using FSX. I am modifying the path for FSX and try again.
FYI, that with Aerosoft Airbus X (Navigraph & Navdatapro) has LOC and center line have correct alignment at same addon scenery. VVTS25L/R
http://www.mycockpit.org/forums/attachment.php?attachmentid=10423&stc=1http://www.mycockpit.org/forums/attachment.php?attachmentid=10423&stc=1

masterp
07-23-2015, 12:15 PM
Hi JL,

I have Changed the path for FSX without success.http://www.mycockpit.org/forums/attachment.php?attachmentid=10424&stc=1

[Scenery]
scenery.cfg=E:\FSX\scenery.cfg
FSfolder=E:\FSX\
AerosoftPath=C:\Users\Panda-Lipice\AppData\Roaming\JeeHellWare
ip=127.0.0.1

jeehell
07-23-2015, 12:45 PM
did you delete the bin file and restart everything after the change of the scenery.cfg path?

masterp
07-23-2015, 11:02 PM
Yes JL I think that I added MonitorARPT=VVTS and deleted bin files after change FSX's path in FSscenery.cfg.

jeehell
07-24-2015, 02:40 AM
Could you delete the bin files again, then after they are built again paste the logNDB.txt file here again?

masterp
07-24-2015, 04:18 AM
Thanks JL, here you go:

*3:11:50 PM* Navdata module launched Server
*3:11:50 PM*
*3:11:50 PM* -BGL scan:
*3:11:50 PM* -ScenerycfgPath:E:\FSX\scenery.cfg
*3:11:50 PM* -FSroot:E:\FSX\
*3:11:50 PM* -Folders Nb:122
*3:14:24 PM* -FS ILS Nb:3625
*3:15:47 PM*
*3:15:47 PM* Navdata1:
*3:15:47 PM* -ARPTliste:15399
*3:15:47 PM* -NavaidListe:18172
*3:15:47 PM* -FIXliste:188902
*3:15:47 PM* -AWYsegments:98493
*3:15:47 PM*
*3:15:47 PM* Navdata2:
*3:15:47 PM* -ARPTliste:15399
*3:15:47 PM* -NavaidListe:18172
*3:15:47 PM* -FIXliste:188902
*3:15:47 PM* -AWYsegments:98493
*3:15:47 PM*
*3:15:47 PM* server started on port:8006
*3:15:48 PM* Client connected: 127.0.0.1
*3:15:48 PM* Client connected: 127.0.0.1

jeehell
07-24-2015, 05:04 AM
In your fsscenery.cfg, I asked you to add the line:
MonitorARPT=VVTS

can you repeat the ini, file process again?

masterp
07-24-2015, 05:14 AM
Hi JL, I have to report that after I paste the post logNDB.txt at 3:18AM; I then test again on VVTS25L, VVDN35R....LOC is now aligned with runway center line :p
Maybe yesterday I rebuild bin files with scenery path still for P3D (I do not remember, sorry). However with correct FSX's path, after rebuild bin files, I think it is correct now
(*3:11:50 PM* -Folders Nb:122
*3:14:24 PM* -FS ILS Nb:3625)

I think my problem has been solved. Many thanks JL for your quick support :D
Cheers,
Vu