Testing without the EGPH addon as this had the issue so i decided to use just stock.
As you can see with LOC captured RWY 06 the aircraft is positioned to the left of the runway!
I’m using prosim 737 and latest Navigraph database.
Anyone help please?
Hi,
thanks for the report - I have checked the localizer antenna in MSFS (I assume you use MSFS for the scenery) and the antenna position in ProSim. Both are correct so far. Also, when I try this approach with the FBW A320 in MSFS, I don´t see any offset here:
Is it possible that you have installed a 3rd party scenery for EGPH and after removing it, that you don´t have re-organize the ProSim database? I´m not a ProSim user, nor do we have any license to test this - but I can remember, that ProSim needs a database comparison between the sim-sceneries and the navdata.
Sorry, but my knowledge ends here … I can only check the data and the seems to be correct so far.
Cheers,
Richard
Hi Richard,
I just uninstalled the Pyree EGPH to test the stock and both still have that issue.
Prosim said a while back:
Prosim is not using the FS2020 ILS generated signal, but creating its own signal based on navdata merged with some BGL info (like antenna position), to avoid these mismatches.
All other default aircrafts are using the FS2020 generated ILS signal.
If signal is wrong, then it is most probably because BGL data has some differences from the P3D/FSX one. Yes, there are differences, but a lot of differences are undocumented.
Hi,
I know, that ProSim doesn´t use the MSFS data but the data must be the same because we create both from the same source. So, when the antenna position is wrong in MSFS, it´s also wrong in all other addons.
In this case, I have checked the localizer antenna position - not only in the MSFS (see the in-flight screenshot), but also directly in the ProSim database:
Here, the record directly from the ProSim database AIRAC 2310:
Now, when I transfer this coordinates into google-maps, you will see, that the antenna position is exact on the real-world position:
Therefore my assumption of any other issue which results in this offset. Sorry, but I can´t see any issue here … by the way, I have looked into the previous cycle too (2309 and 8) and in both were the same coordinates.
Cheers,
Richard
Thanks for your efforts. I have posted this on the prosim forum to get a response.
I done a test and rebuild prosim navdata with P3D V5 data instead of MSFS and it alligns up…
Oh - strange (but good idea, well done) …
May I ask, if you can update this posting when you have any news to this issue … I´m curious what cause this offset …
I will remove the “auto-close” feature from this topic because I guess, they need time too to look into it 
Thank you,
Richard
You can try prosim out as a demo version? Maybe look into it…
