tanjix

Feature request regarding export to IvAp

10 posts in this topic

Hello,

 

I just bought PFPX and want to Export flightplans to IvAp as well (Export Feature to "IVAO/IVAP (Default.fpl)"

 

I encountered the same prolems as described in this thread: http://forums.x-plane.org/index.php?/forums/topic/79233-x-ivap-how-do-i-load-a-plan/

 

I did some more Tests and were able to determine what the problem is: PFPX is using wrong Syntax for the export!

 

This is an example file that is created through PFPX export - The errors are marked red and how it should be is green one line below:

Orange lines below are not exported so it would be nice to get them added to a bugfix!

 

[FLIGHTPLAN]
ID=BOX981

CALLSIGN=BOX981
RULES=I
FLIGHTTYPE=S
NUMBER=1
ACTYPE=A332
WAKECAT=H
EQUIPMENT=SDE1FGHIJ1RWXYZ
TRANSPONDER=S
DEPICAO=ZSPD
DEPTIME=1540
SPEEDTYPE=K

SPEEDTYPE=N (or maybe M)
SPEED=0875

SPEED=0467 (value according to SPEEDTPE=N or M)
LEVELTYPE=S

LEVELTYPE=F
LEVEL=1220

LEVEL=380
ROUTE=K0875S1220 SUF11D SUF W167 SASAN R343 WHA B213 ENH V38 GAO B213 LXA B345 NONIM/N0470F390 B345 NARAN L626 ONISA/N0470F400 L626 DPN G333 TIGER G202 RK J173 SK G214 PG G665 ASVIB N312 KHM A453 MIDSI UA453 SOGAT SOGAT1

ROUTE=N0467F380 SUF11D SUF W167 SASAN R343 WHA B213 ENH V38 GAO B213 LXA B345 NONIM/N0470F390 B345 NARAN L626 ONISA/N0470F400 L626 DPN G333 TIGER G202 RK J173 SK G214 PG G665 ASVIB N312 KHM A453 MIDSI UA453 SOGAT SOGAT1
DESTICAO=OBBI
EET=0929
ALTICAO=OEDR
ALTICAO2=
OTHER=PBN/A1B1C1D1L1O1S1 NAV/RNVD1E2A1 DOF/170417 REG/DABOG EET/ZHWH0057 ZPKM0156 VNSM0451 VIDF0546 OPKR0640 OIIX0742 OBBB0905 RVR/75 PER/D
ENDURANCE=1048
POB=168

PIC=<Name of the Pilot in Command>

LIVERY=<>

AIRLINE=<AIRLINE ICAO CODE>

 

The remarks-section is too long and because of that, the import to IvAp fails. When one shortens the RMK manually by editing "Default.fpl", importing works... Maybe it is possible to select, which kind of remarks should be exported and which not?

 

Hopefully this message gets to the responsible persons to get a patch as soon as possible!

 

Thank you!

0

Share this post


Link to post
Share on other sites

I wasn't aware China had moved away from the metric system?

 

ICAO Speed entries for planning:

True airspeed for the initial or whole cruise segment of the flight, indicated as:

“N” for Knots, followed by a four-digit figure:

“M” for Mach number followed by a three-digit representation of ratio,

or “K” for Kilometers/hour followed by a four-digit number.


i.e. K0830, N0485, M082..


 

Quote

 

Quote form the IVAO flightplan guide:

The cruising speed is the
True Air Speed expressed in one of the three possible units:

N = Knots: N followed by 4 digits which will be the speed in knots (N0220 = 220KT)

M = Mach: M followed by 3 digits which will be the mach number without the dot character (M079 = 0.79 Mach)

K = km/h : K followed by 4 digits which will be the speed in kilometre per hour (K0350 = 350km/h)

 

 

 

ICAO Flight level:
Planned cruising level for the initial or whole cruise segment of the flight, indicated as:

“F” for Flight Level in 100s of feet,

“A” for plain altitude in 100s of feet (both three-digit),

“S” for Standard Metric Level in tens of metres,

“M” for plain altitude in tens of metres (both four-digit),

i.e. F330, M0840, A045


 

Quote

 

Quote from IVAO flightplan guide:

The cruising altitude or flight level is expressed in one of the three possible units:

F = flight level: followed by 3 digits expressed in hundreds of feet above transition altitude. (Example: F130 = 13000ft).

A = altitude: followed by 3 digits expressed in hundreds of feet below transition altitude. (Example: A025 = 2500ft).

S = standard metric level: followed by 4digits expressed in tens of meters above transition altitude (Example: S1130 = 11300m)

M = metric altitude: followed by 4 digits expressed in tens of meters below transition altitude (Example: M1130 = 11300m)

 

 

0

Share this post


Link to post
Share on other sites

srcooke, you are - in general - absolutely right!

 

But at least X-IvAp (IvAp for X-Plane) does not "know" the speed-group "K" - only "N" and "M" is allowed.

 

Maybe it might make sense to add a new Export Option to Export to "X-IvAp" which has a modified Export structure with the correct variables...?

0

Share this post


Link to post
Share on other sites

In which case surely the X-IvAp application should be updated rather than degrading the correct format ?

0

Share this post


Link to post
Share on other sites
vor 2 Minuten, srcooke sagte:

In which case surely the X-IvAp application should be updated rather than degrading the correct format ?

 

I doubt that X-IvAp will get any updates as there haven't been any since a long period of time.

 

Updating/Patching PFPX would be much faster and - indeed - I am quite sure that this will help a lot of more People than just me.

 

For me PFPX is quite unusable right now when I cannot export to my X-IvAp correctly.

0

Share this post


Link to post
Share on other sites

Ok, so this not a bug at all with PFPX v1.28.8 and the IvAp application.

 

You are requesting a new export function for X-IvAp.

0

Share this post


Link to post
Share on other sites
vor 5 Minuten, srcooke sagte:

Ok, so this not a bug at all with PFPX v1.28.8 and the IvAp application.

 

You are requesting a new export function for X-IvAp.

 

The current export functionality to IVAO/IVAP is a bug, as e.g. some variable indicators are wrong (ID being used instead of CALLSIGN (to get the aircraft callsign correctly imported to IvAp)), missing PIC etc.

It's not just the thing with the speed-group "K", which is unknown to X-IvAp.

0

Share this post


Link to post
Share on other sites

ID= is also used by other well known planning tools including Simbrief, has the format changed?

 

Quote

[FLIGHTPLAN]
ID=BOX0000
RULES=I
FLIGHTTYPE=S
NUMBER=1
ACTYPE=B77W
WAKECAT=H
EQUIPMENT=SDE1E2E3FGHIJ2J3J4J5M1RWXY
TRANSPONDER=LB1D1
DEPICAO=ZSPD
DEPTIME=1805
SPEEDTYPE=K
SPEED=0924
LEVELTYPE=S
LEVEL=0980
ROUTE=SUF11D SUF W167 SASAN R343 WHA B213 ENH V38 GAO B213 LXA B345 NONIM/N0484F390 B345 NARAN L626 ONISA/N0477F400 L626 DPN G333 TIGER G202 RK J173 SK G214 PG G665 ASVIB N312 KHM A453 MIDSI UA453 SOGAT SOGAT1
DESTICAO=OBBI
EET=0839
ALTICAO=OEDF
ALTICAO2=
OTHER=PBN/A1B1C1D1L1O1S2 DOF/170417 REG/N713SB EET/ZHWH0053 ZPKM0141 VNSM0411 VIDF0504 OPKR0557 OIIX0657 OBBB0821 OPR/BOX RMK/TCAS
ENDURANCE=1004
POB=302

 

As you can see virtually the same format as PFPX

0

Share this post


Link to post
Share on other sites
vor 12 Stunden , srcooke sagte:

ID= is also used by other well known planning tools including Simbrief, has the format changed?

 

I do neither know whether there is/was any change in formats / syntax nor am I a programmer to get this checked and sorted.

 

The only thing I know for now is that exporting to IVAO/(X-)IvAp is not working for me and that I am not alone with this (see link in my initial post). I gave some input on how this could be solved.

Maybe anyone who is responsible can check this and provide an update? I (and others) would surely appreciate it.

0

Share this post


Link to post
Share on other sites

Neither ID= or CALLSIGN= are used in loading the flightplan as tested here IvAp v2.0.2 b2773, the aircraft identification is called from the IvAp connection as noted in the manual:

 

Quote

I t e m 7 – A i r c r a f t I d e n t i f i c a t i o n ( m a x 7 c h a r s )
This field is pre-filled with the callsign from the IVAO connection window

 

The same applies to the Pilot in Command, taken from the connection settings.

 

Neither are populated by the flightplan.

 

EDIT: both of the above data are called from the pilot.cfg file and not the flightplan.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now