News:

Status: CAVOK

Main Menu

X-Plane 11, error loading a PlanG Flightplan

Started by KDO_Snakebyte, January 27, 2020, 08:51:10 PM

Previous topic - Next topic

KDO_Snakebyte

Hello everybody.
Today i received an error window saying:
"Invalid Flightplan.
This flightplan contains a line that is not according to the FMS plan specification.
The exeption is:
Latitude must be between -Pi/2 and Pi/2.
I will not load this flight plan
."

I read the txt of this flightplan but didn't find nothing wrong. I used to export FP from PlanG to X-Plane as i did in the last 5 years .....
Someone know this problem?

The text of the flightplan is:
I
3 VERSION
1
18
1 LOWK 0.000000 46.649862 14.323876
28 +46,658_+014,277  7500 46.657684 14.277420
28 +46,625_+014,213  7500 46.625274 14.212704
28 +46,612_+014,039  7500 46.612068 14.039497
28 +46,620_+013,845  7500 46.619733 13.844833
11 TP FDR+46,570_+013,806  7500 46.570000 13.805556
11 CONFINE+46,530_+013,640  7500 46.530000 13.640000
11 TARVISIO+46,500_+013,590  7500 46.500000 13.590000
11 PONTEBBA+46,510_+013,310  7500 46.510000 13.310000
11 CHIUSAF+46,410_+013,310  7500 46.410000 13.310000
28 +46,373_+013,098  7500 46.373227 13.097763
28 +46,406_+013,006  7500 46.405907 13.006096
28 +46,418_+012,788  7500 46.417506 12.788429
28 +46,421_+012,582  7500 46.420583 12.581749
28 +46,463_+012,426  7500 46.462930 12.425880
28 +46,423_+012,358  7500 46.422772 12.358332
28 +46,265_+012,300  7500 46.264867 12.299881
28 +46,180_+012,281  7500 46.180306 12.280655
1 LIDB 7500 46.165874 12.249069


Thank You for your time.
Andrea.

tim arnot

I think you need to update Plan-G to the current release (build 167, on the main page). The two main problems I see there are waypoint names are being written as lat/lon coordinates, and they're being written with the wrong number format. That's all fixed in the current release.

Tim. @TimArnot

KDO_Snakebyte

Thank You Tim, now i'll try to update.
See You!!

KDO_Snakebyte

Quote from: KDO_Snakebyte on February 01, 2020, 07:03:26 PM
Thank You Tim, now i'll try to update.
See You!!

Sorry and excuse me.
I upgrade to last release 3.2.2.167 last week .......
Now i try to uninstall everything and reinstall PlanG ..... Hoping it will work again ...

KDO_Snakebyte

OK, after uninstalling and reinstalling PlanG, this is the result:
1) Made the Flightplan as usual, exported it for X-Plane fms ........... Error Message as i reported in the first post;
2) Made the same flightplan changing some waypoint (i jumped the Villach city ....) ........ Error Message as i reported;
3) Made another Flightplan, traking off from LOWK (so, same start airport) directed South to LJCE (Cerklje pri Krki) , NO Errors ......

I think that there is something wrong in the coordinates system departing from LOWK direct WEST but don't know which.

Solutions?
YES ....... I didn't create a flightplan and fly Visual ....  8) 8) 8)

(now i try to export for Prepar3D)  ;D :P :P

KDO_Snakebyte

Updating:

Exported the same Flightplan for Prepar3D (i have version 4) and all works well!!!

Something wrong in X_Plane 11.41?

KDO_Snakebyte

Try by try by try ..........
I decided to manually set the flightplan looking at old FPs made with previous version on PlanG.
This is the result:
I
3 VERSION
1
13
1 LOWK 0.000000 46.649771 14.323879
28 +46,570_+013,806  10600 46.570000 13.805556
28 +46,530_+013,640  10600 46.530000 13.640000
28 +46,500_+013,590  10600 46.500000 13.590000
28 +46,510_+013,310  10600 46.510000 13.310000
28 +46,410_+013,310  10600 46.410000 13.310000
28 +46,380_+013,120  10600 46.380000 13.120000
28 +46,413_+012,789  10600 46.413245 12.789459
28 +46,421_+012,583  10600 46.420583 12.582779
28 +46,460_+012,412  10600 46.460329 12.411804
28 +46,267_+012,302  10600 46.266528 12.302284
28 +46,186_+012,286  10600 46.185535 12.286148
1  LIDB 10600 46.165874 12.249069


It work well, so i think there is something wrong in the coordinates system of Plan G but only for that place or that route. Other routes made for anf from other airports works as ususal.

tim arnot

Could you attach the flight plan in either .plg or p3d format, and I'll see what it does here.

Tim. @TimArnot