This was based on a Navigraph Charts generated flight plan for high altitude flight from LRCK to EGPK. The INIBuild A310 FMS returned the error ‘Waypoint not in database’.
Hi Mark,
I assume a Inibuild A310 issue because I have looked in the source and in the MSFS database and all reported navaids and the two waypoints are included. You can do a simple test by yourself, when you search these points in the WorldMap. The WorldMap uses our data and my information is, that the Inibuild A310 uses these in-game BGLs. So, the all aircrafts, WorldMap, … which use the in-game MSFS data should return the same equal information. When not, something goes wrong in the aircraft, like the Inibuild A310
Here a few examples, searched via the WorldMap:
BRV VORDME
Also, when I try the default MSFS A320 as an example, I also can enter all navaids and the waypoints without any issue. I have used the same examples as above:
You see, the navaids and waypoints are searchable and selectable in the WorldMap and in the MSFS A320, both use the in-game MSFS data which we provide. You can be sure, that all waypoints, navaids, terminal procedures, … what we have in the charts for flightplanning, what you use in SimBrief, … are included in the MSFS data. It looks like a Inibuild issue as you see and as you can test by yourself on your system.
Please report this to Inibuild, but that´s not a navdata issue. The navaids and the reported waypoints are included in the MSFS, in our dataset.
Mark,
as I have suggested, have you checked if you see these navaids, waypoints in MSFS (ie on the WorldMap), or if you can enter these points in any other standard/default aircraft (ie A320, TBM, …)?
When yes, and you can enter it without any issue, you can be sure that this is a Inibuild issue because than, the points are available in the MSFS.
This is not a navdata issue, because all reported points are in our MSFS database as you see in the screenshots above and the same can be tested by yourself.
As I have written - when you plan a flight with our chart app you can be 100% sure, that all waypoints/navaids are available in our MSFS database too. So it must be any other reason, when you can’t find these waypoints.
So, I can´t really re-produce at least the “missing” navaids in the Inibuild A310 …
But, the A310 has an issue to find RNAV waypoints, like the PIKIL or HOIST. Named waypoints are working correctly, but RNAV waypoints will not be found.
ABBOT (EG 52.01611111, 0.59958056) Named waypoint - working as expected
That happens for all “RNAV waypoints” - such waypoints can´t be used in the A310. Possible some other waypoint types too but it´s clear, that these waypoints are included in the data and the A310 can´t use it. PIKIL and HOIST are both defined as “RNAV Waypoints” too and therefore “not in database”:
I did verify that with other aircraft (A320NEO and TBM930) the waypoints are there and in the cases of BRV and CLJ VORs, the FMS/ FMGC comes up with more than one VOR to choose from. I believe that this is where the INIBuild FMGC may need improvement; if there is more than one waypoint, the A310 does not always show them.
I normally input all my waypoints manually, using the SimBrief log sheet for flight planning. As you stated, if the SimBrief flight plan and Navigraph Charts map show the same waypoints, then it is an aircraft issue. I will use that as a basis for future flight planning.
