Hello! Been trying to fly out of Bogata SKBO lately and I think there may be malformed data with one or more waypoints in the area
Hi Andrew,
Welcome.
In order for your issue to be addressed please provide details in Posting Guide
Cheers
Ian
A little more info as per the Posting guide:
Windows 10
XP12(current version)
Aircraft Felis 747 Classic (LTN92 INS)
AIRAC 2402
I believe it’s either wapoint OSUSU or GIKPU where the problem lies. Basically the HSI (when in INS mode) “breaks” when navigating along the route (OSUSU4 GIKPU)
Communicated on the FELIS discord about this issue, and multiple replys of this problem being due to malformed nav data
Will stand by if any more information will be needed!
Hi,
thanks … I don’t know anything about a FELIS 747Classic, nor have/had we any contact to the devs there. Also I don’t know which data format they use.
Therefore are general answer:
I have checked both waypoints OSUSU and GIKPU and both coordinates are correct in the XP12 navdata.
You can also simple try that with any stock aircraft from XP12.
Again, we have no information which dataset they use therefore, nor have we any contact to the devs there.
I would ask the FELIS devs, if they can contact us with a exact description of the issue and why they mean that this is a navdata issue.
Thank you
Richard
I have heard from Felis himself who gave me the following
" 1. it uses default XP format. And if there is a Custom Data installed - i use that instead.
- [10:36 AM]
Although would be cool to have airports and runways in a separate file. For now i read that huge default apt.dat and get data from it, but only for the airports coordinates. No runways yet. And then i save it in my own airports cache file with my own format, which is much smaller and therefore reads faster.
- [10:37 AM]
I have seen they made their special format for KLN-90 and they reformatted SIDs and STARs. However i still have no idea what is all that means there, as there is no documentation. Even reading default files would be a problem for me, because i simply cannot find any good explanation for that CIRC or ARINC or whatever it is there. Just a mistery."
Hi,
thank you very much for the information.
to #1:
As I have written before, here the two waypoints which are included in the dataset for XP12 (so in the Custom Data folder):
5.255341667 -73.927594444 OSUSU SKBO SK 4464707 OSUSU
6.024130556 -73.757275000 GIKPU ENRT SK 4464727 GIKPU
In my eyes absolutely correct - so it seems more an addon issue rather a navdata issue (when FELIS uses the Custom Data too correctly).
to #2:
When this devs contact us, we can produce any file in any format what they need but also here, there was no contact and they never have requested any files from us. So “a wish” isn´t enough - they must act too, when they expect something
to #3:
It´s similar to point 2 - the KLN90 is a own designed format. The developer from the KLN90 had contacted us and we have created this own format for this addon together. When the FELIS dev needs any specification, he must contact the KLN90 dev, or us, than we can built also a own FELIS format, which fits perfect to their addons.
So, I can´t see any issue on our side sorry. The XP12 data (in the Custom Data folder) are correct and we have no request from the FELIS developer about anything what they need.
Hope that helps,
Richard
Hey Richard,
Thank you for looking into the matter, I will get ahold of the dev and let him know what you told me. Thanks for the help!
You’re welcome … As I wrote, we help where we can and we support all 
Cheers
Richard
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.