Route - Not in database
-
I have a route which I put into
C:\Users\James\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\justflight-aircraft-rj\work\JustFlight\FlightPlans
I also put it into
C:\Users\James\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\justflight-aircraft-rj\work\
The route file is as follows from Simbrief
Its named
EGLCEGPF01.RTE
[FlightPlan] EGLC 51.505278 0.055278 APT --- BPK 51.749736 -0.106736 WPT 117.50 POTON 52.084533 -0.427161 WPT --- UN601 BEDFO 52.225000 -0.563281 WPT --- UN601 EBOTO 52.359250 -0.694342 WPT --- UN601 PIPIN 52.610017 -0.941678 WPT --- UN601 LESTA 52.740858 -1.072061 WPT --- UN601 EMBOR 52.963333 -1.295903 WPT --- UN601 XAPOS 53.291275 -1.630903 WPT --- UN601 BOLBI 53.466597 -1.812519 WPT --- UN601 ULSAX 53.598333 -1.950000 WPT --- UN601 POL 53.743778 -2.103286 WPT 112.10 UN601 NELSA 53.863333 -2.184797 WPT --- UN601 RIBEL 54.016111 -2.289656 WPT --- UN601 EGPF 55.871944 -4.433056 APT ---
I have updated Navigraph data for this addon.
When I go and enter this into the FMC I get this error.
NOT IN DATABASE
I've not found a solution and I am unsure if this is a bug? Or am I doing this wrong? I don't really want to have to enter my flight plans manually each time.
-
@Yetty Could you confirm if you locally saved the flight plan before or after the flight was loaded? If it was after the flight was loaded, try restarting the flight.
Just to confirm, the first file directory you posted it the correct one:
C:\Users*USERNAME*\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\justflight-aircraft-rj\work\JustFlight\FlightPlans
Mark - Just Flight
-
Little thing I would like to question rather than create a new thread similar to this, on the POS INIT page. It doesn't allow a gate number to be entered - is this expected?
-
@jeffbadgers Yes, that is expected. It's a limitation we have at the moment as the gate numbers/positions don't exist in the Navdata that we are using with the FMS. It is on our list of things we would like to find a solution for in the future, but we're unable to provide a timescale for that at the moment.
Mark - Just Flight
-
Thanks Mark not a big deal just wondered - This will be a great jet to fly I can tell already!
-
I had a similar problem, the rate file was saved with <src icao><dst icao>01.rte, so for KMRY to KLAS, KMRYKLAS01.rte. initially I tried to load KMRYKLAS in coroute, but that would fail, when I tried KMRYKLAS01 in coroute, that loaded the plan correctly. So maybbe cheek if this is the problem for you.