Jump to content

FS2004 .pln


Recommended Posts

Hi,

 

Great job you've done Urs with 1.2.0 ! Bravo !

 

Just a question : when loading a saved FS2004 FPL (.pln) from "Select a route type" window I just get :

 

"le format de la chaîne d'entrée est incorrect" + "FP not valid"

 

Any idea ?

 

Thanks

Link to comment
Share on other sites

Bonjour Urs,

 

Here is one of my FS2004 FPL (.pln) that is rejected as described above :

 

[flightplan]

AppVersion=9.1.40901

title=EDDV Hannover to LFPO Paris Orly

description=EDDV, LFPO

type=IFR

routetype=2

cruising_altitude=25000

departure_id=EDDV, N52* 27.61', E9* 41.01', +000183.00

departure_position=1

destination_id=LFPO, N48* 43.40', E2* 22.77', +000291.00

departure_name=Hannover

destination_name=Paris Orly

waypoint.0=, EDDV, , EDDV, A, N52* 27.61', E9* 41.01', +000183.00,

waypoint.1=EDWW, WRB, , WRB, V, N51* 30.34', E9* 6.65', +000000.00,

waypoint.2=EDFF, RANAX, , RANAX, I, N51* 12.43', E9* 2.77', +000000.00, UN850

waypoint.3=EDFF, EDEGA, , EDEGA, I, N51* 2.08', E9* 0.47', +000000.00, UN850

waypoint.4=EDFF, AMETU, , AMETU, I, N50* 49.98', E8* 57.87', +000000.00, UN850

waypoint.5=EDFF, SOGMI, , SOGMI, I, N50* 31.65', E8* 53.95', +000000.00, UN850

waypoint.6=EDFF, BOMBI, , BOMBI, I, N50* 3.40', E8* 48.02', +000000.00, UN850

waypoint.7=EDFF, FFM, , FFM, V, N50* 3.22', E8* 38.23', +000000.00, UL984

waypoint.8=EDFF, RUDUS, , RUDUS, I, N50* 2.86', E8* 4.70', +000000.00, UL984

waypoint.9=EDFF, OBIGA, , OBIGA, I, N50* 1.85', E7* 8.30', +000000.00, UL984

waypoint.10=EDFF, ADENU, , ADENU, I, N50* 1.53', E6* 54.50', +000000.00, UL984

waypoint.11=EDFF, NOSPA, , NOSPA, I, N50* 1.23', E6* 42.68', +000000.00, UL984

waypoint.12=EDFF, NTM, , NTM, V, N50* 0.95', E6* 31.91', +000000.00, UN857

waypoint.13=EDFF, RALAM, , RALAM, I, N50* 0.87', E6* 22.52', +000000.00, UN857

waypoint.14=EDFF, DIK05, , DIK05, I, N49* 55.37', E6* 13.75', +000000.00, UN857

waypoint.15=EBBU, DIK, , DIK, V, N49* 51.68', E6* 7.78', +000000.00, UN857

waypoint.16=EBBU, IDOSA, , IDOSA, I, N49* 44.50', E5* 52.19', +000000.00, UN857

waypoint.17=EBBU, TOLVU, , TOLVU, I, N49* 37.52', E5* 22.30', +000000.00, UN857

waypoint.18=LFFF, RAPOR, , RAPOR, I, N49* 35.48', E5* 12.78', +000000.00, UN857

waypoint.19=LFFF, RENSA, , RENSA, I, N49* 31.98', E4* 53.13', +000000.00, UN857

waypoint.20=, LFPO, , LFPO, A, N48* 43.40', E2* 22.77', +000291.00,

 

hope this will help

 

Merci

Link to comment
Share on other sites

Salut Jean-Louis,

 

I just went over to "SimRoutes.com" and generated a simple FS9 flightplan to be sure which data format it is:

 

[flightplan]
title=LFBO to LFPO
description=LFBO, LFPO
type = IFR
routetype = 3
cruising_altitude=0
departure_id=LFBO, N43* 37.74', E1* 21.83', +000499.00
destination_id=LFPO, N48* 43.52', E2* 21.57', +000291.00
departure_name=Blagnac
destination_name=Orly
waypoint.0=LFBO, A, N43* 37.74', E001* 21.83', +000000.00, 
waypoint.1=TBO, V, N43* 19.93', E000* 08.74', +000000.00, 
waypoint.2=GONUP, I, N43* 27.65', E000* 45.53', +000000.00, 
waypoint.3=TOU, V, N43* 40.85', E001* 18.59', +000000.00, 
waypoint.4=FISTO, I, N44* 27.68', E001* 13.63', +000000.00, 
waypoint.5=PERIG, I, N45* 07.03', E000* 58.17', +000000.00, 
waypoint.6=DIBAG, I, N45* 47.37', E000* 47.25', +000000.00, UT210
waypoint.7=TUDRA, I, N46* 32.33', E000* 46.85', +000000.00, UT210
waypoint.8=BEVOL, I, N47* 00.72', E000* 55.85', +000000.00, UT158
waypoint.9=AMB, N, N47* 25.09', E001* 02.46', +000000.00, UT158
waypoint.10=LFPO, A, N48* 43.52', E002* 21.57', +000000.00, 

You see that especially the lines beginning with "waypoint.nn" are quite different from the plan you provided.

There is also no information about "AppVersion=9.1.40901". The later information I've only seen in FSC flightplans.

 

Can anyone shed some light on me?

Link to comment
Share on other sites

This looks like a vroute created plan, as every plan that I create via this way will always come up with an error. Maybe the FIR part at the beginning as this will show the Boundary that those waypoints are within.

 

[flightplan]

AppVersion=9.1.40901

title=EGLL London Heathrow to OMDB Dubai Intl

description=EGLL, OMDB

type=IFR

routetype=2

cruising_altitude=35000

departure_id=EGLL, N51* 28.65', W0* 27.68', +000083.00

departure_position=1

destination_id=OMDB, N25* 15.17', E55* 21.87', +000034.00

departure_name=London Heathrow

destination_name=Dubai Intl

waypoint.0=, EGLL, , EGLL, A, N51* 28.65', W0* 27.68', +000083.00,

waypoint.1=EGTT, DVR, , DVR, V, N51* 9.75', E1* 21.55', +000000.00,

waypoint.2=EGTT, DVR10, , DVR10, I, N51* 8.98', E1* 37.52', +000000.00, L9

waypoint.3=EBBU, KONAN, , KONAN, I, N51* 7.85', E2* 0.00', +000000.00, L9

Link to comment
Share on other sites

"This looks like a vroute created plan" Yes, Dave you are right ! Vroute is a pretty good tool to create FS9 valid FPLs

 

But this is not the case for the following one I just created and saved from within FS9 :

 

[flightplan]

AppVersion=9.1.40901

title=LFBO to LFPO

description=LFBO, LFPO

type=IFR

routetype=3

cruising_altitude=21000

departure_id=LFBO, N43* 37.16', E1* 22.30', +000499.01

departure_position=32L

destination_id=LFPO, N48* 43.40', E2* 22.77', +000291.00

departure_name=Blagnac

destination_name=Paris Orly

waypoint.0=, LFBO, , LFBO, A, N43* 37.16', E1* 22.30', +000499.01,

waypoint.1=LF, SAU, , SAU, V, N44* 40.61', W0* 9.18', +000000.00,

waypoint.2=LF, BEGEL, , BEGEL, I, N48* 41.37', E1* 50.17', +000000.00, UR10

waypoint.3=LF, RBT, , RBT, V, N48* 39.24', E1* 59.65', +000000.00, UG4

waypoint.4=, LFPO, , LFPO, A, N48* 43.40', E2* 22.77', +000291.00,

 

and once again it's rejected when I try to load it as a FS9 .pln into EFB ??

 

Merci

Link to comment
Share on other sites

Hi all,

 

in other words "SimRoutes.com" doesn't generate real FS9 plans? Or the other way round, are there several different flight plan formats for FS9? Obviously FS9 can read both of them (the flightplan created by SimRoutes.com and the flightplan created by Vroute) :?

Link to comment
Share on other sites

Bonjour Urs,

 

Don't know about "SimRoutes.com"

 

"are there several different flight plan formats for FS9 ? " might be true

 

As you can see a FPL created from within FS9 is not even accepted by EFB as described above.

 

There might be something wrong

 

Bonne journée

Link to comment
Share on other sites

I also have problems with the import of FS9 flightplan-files.

My VA (Leipzig Air) generates FS9-flightplans that work flawless with FSX and Active Sky Evo but not with EFB.

As a workaround i copy all waypoints via copy&paste to the EFB and then everything is fine - no big deal.

I've attached a flightplan generated by the VA-system. Maybe this helps.

 

Btw: Now running EFB on my new MacBook Pro in Parallels-Virtual Machine via WLAN completely smooth.

Fascinating feature! Now i'm able to plan my next flight from the couch in the living room!

Hope simconnect-failures will not occur again (knock on wood). Keep up the good work!

 

Cheers

Ingo

Link to comment
Share on other sites

Hi Ingo,

 

thanks for the plan. A closer look into the several plans shows that the difference seems to be only in the waypoint lines. There are either 6 or 9 elements per line. I just changed the plugin so it should work now for both versions ;-).

 

@ Jean-Louis, Patrick, Dave, and Ingo

To verify whether the plugin works fine I need you as a tester 8-). Can you please send me an email to support@aivlasoft.com so I can return you the new plugin along with the instructions on how to use it? THANKS.

Link to comment
Share on other sites

"I too would be very interested in being able to import flight plans produced by vRoute"

 

With the new FS9 plugin Urs will soon make available, it works fine for FS9 FPLs but it does not for FSX (might be a Vroute issue/version 1.0.7.5)

 

to import : first export from Vroute export tab/export format field

 

much much simpler and time saver : just copy and paste the route into the EFB "route description" field

 

regards

Link to comment
Share on other sites

@ all,

 

it seems that the FS2004 plugin now works as expected ;-).

 

I will integrate the updated plugin into the next fixpack (version 1.2.1). If anyone needs the plugin before this fixpack will be released, please email me and I send you the plugin along with the instructions on how to install it.

Link to comment
Share on other sites

×
×
  • Create New...