1.0.5 no more Airbus extended CORoute (.flp) ?

[Tchou]

I saw that you hardened the Company routes loading,

Have you removed support from .flp files created with PFPX or Simbrief ? 

 

[tkyler]

yes we have removed it.  It seems that some other software used that file extension but with a different internal format.  With two different file formats using the same extension, we thought that was risky and so removed it until we can sort it out.  Stability against soft crashes is the priority and I think we will soon start looking at all possible formats users will want to enter and evaluate those and come up with a solution.

-tkyler

[Tchou]

This one would be pretty usefull as it is used by a lot of other planes as well so I configured PFPX to export in this format so I can use it regardless of the plane I Fly. 

can you tell me which format I can use ?

 

 

[tkyler]

I couldn't say for sure as I don't know a lot of those; however, page 12 of the Interface Guide in the Docs outlines the particulars of the fpl format we implement.  Perhaps you can correlate one of those in the list with the requirements of the *.fpl format we use? 

-tkyler

Edited May 28, 2016 by tkyler

[Tchou]

Sadly, that's what I did when I Buyed the plane but didn't find any of those ressembling the format you describe in the Manual. I was really Happy when I realized you supported Airbus Extended format because that's one of Simbrief and PFPX native formats. 

Maybe there is something to do with Either Simbrief webmaster of PFPX devs to let them know what you want to include in your native format so they can export for IXEG directly.

[daemotron]

You can copy the route in PFPX (go to the route edit window, it's in the lower left corner). Just don't copy SID, STAR and transitions. Paste into notepad and add departure and arrival airport, save file as .fpl and that's it. The same holds true for Simbrief.

[Tchou]

it's a workaround, but in case of step climbs there is some cleaning to do...

[daemotron]

If you copy from the route editing page and not the flight plan document, there's no step climbing to be cleansed.

Gesendet von meinem SM-G920F mit Tapatalk

[Tchou]

Didn't see it like that, thanks. 

 

[henrimarch]

I entered this as a flightplan: KSFO CZQ J110 FUZZY KLAS

and got the message file type not supported, see also attached file ?

I am not sure why ?

ksfoklas.flp

[theaviator13]

8 minutes ago, henrimarch said:

I entered this as a flightplan: KSFO CZQ J110 FUZZY KLAS

and got the message file type not supported, see also attached file ?

I am not sure why ?

ksfoklas.flp

Where did you place this file?

[Tchou]

The extension should be .fpl not .flp

sorry for the dyslexic among us ;-)

[henrimarch]

Thanks Tchou, yes I am famous for that, also for trying to connect a ssd drive up side down and wondering why it isn't working.

[Rodeo]

I wonder whether the .txt extension could also be supported? This way we could easily copy coroutes to and from J.A.R. Design planes' coroutes folder. The format (ICAO SID WP1 WP2 … WPn STAR ICAO) is the same.

[Tom Knudsen]

Not sure why this happend, but think there is a small bug in Gizmo @Ben Russell

Version 1.0.5 just updated..

 

G64: 441.502: Trigger: ScriptedReboot..
G64: 441.502: Run('OnBeforeReboot')
G64: 441.503: GizmoCore::Stop()..
G64: 441.572: GizmoCore::Start()..
G64: 441.573: Boot Count: 5
G64: 441.604: deployment.key contents:(062c01aa48d7774119bcddd6c28ace33)
--=={This application has crashed because of the plugin: Gizmo64}==--

 

Included is the log file

Log.txt

GizmoLog.txt

 

Hope you could look at it

 

Edited May 31, 2016 by Tom Knudsen

[Ben Russell]

5 hours ago, Tom Knudsen said:

Not sure why this happend, but think there is a small bug in Gizmo @Ben Russell

Version 1.0.5 just updated..

 

G64: 441.502: Trigger: ScriptedReboot..
G64: 441.502: Run('OnBeforeReboot')
G64: 441.503: GizmoCore::Stop()..
G64: 441.572: GizmoCore::Start()..
G64: 441.573: Boot Count: 5
G64: 441.604: deployment.key contents:(062c01aa48d7774119bcddd6c28ace33)
--=={This application has crashed because of the plugin: Gizmo64}==--

 

Included is the log file

Log.txt

GizmoLog.txt

 

Hope you could look at it

 

Haven't seen one of those in a looong time. Thanks Tom. Adding it to the list.

[Richdem]

On 5/28/2016 at 2:55 PM, tkyler said:

yes we have removed it.  It seems that some other software used that file extension but with a different internal format.  With two different file formats using the same extension, we thought that was risky and so removed it until we can sort it out.  Stability against soft crashes is the priority and I think we will soon start looking at all possible formats users will want to enter and evaluate those and come up with a solution.

-tkyler

This is a real shame,

I used PFPX since day one with no issues whatsoever. If I use the text document work around do I need to put the departure airport airport as well as the way points or just the waypoints? 

CYUL YUL YOW CYYZ

Or

YUL YOW 

Richard

[Rodeo]

Airports must be included.

[Tchou]

you can also include airways like : 

UMMS KOLOS T52 BUSIN L999 PINUG T52 RAVOK P851 VALOL M984 KOTEK T709 SOPAV L156 HLV M984 MIKOV DCT DETSA UQ984 VAMTU UM984 PADKO UL127 FJR LFBO

[Richdem]

Thanks guys,

I will use this method until the issue are resolved

Richard

[Richdem]

12 hours ago, Tchou said:

you can also include airways like : 

UMMS KOLOS T52 BUSIN L999 PINUG T52 RAVOK P851 VALOL M984 KOTEK T709 SOPAV L156 HLV M984 MIKOV DCT DETSA UQ984 VAMTU UM984 PADKO UL127 FJR LFBO

I still cannot load the following flight plan loaded created with notepad

PAJN LVD YYD UAB J488 TRENA CYVR

Did I miss something?

PAJNCYVR01.flp

[tkyler]

15 hours ago, Richdem said:

This is a real shame,

I don't disagree Richard and we'll get back to it.  Having a few conflicts early on just made us want to be a bit cautious, that's all.   We selected the most common and shortest format we could find.

7 minutes ago, Richdem said:

I still cannot load the following flight plan loaded created with notepad

 

The file extension needs to be .fpl.     you have .flp  Also, you need to account for 'Direct To' using DCT   (except the first point after the departure airport).  So try:

Quote

PAJN LVD DCT YYD DCT UAB J488 TRENA CYVR

Page 11 of the Interface Guide in the Docs folder covers the particulars of the file format.

-tkyler

Edited June 3, 2016 by tkyler

[Richdem]

2 hours ago, tkyler said:

I don't disagree Richard and we'll get back to it.  Having a few conflicts early on just made us want to be a bit cautious, that's all.   We selected the most common and shortest format we could find.

The file extension needs to be .fpl.     you have .flp  Also, you need to account for 'Direct To' using DCT   (except the first point after the departure airport).  So try:

Page 11 of the Interface Guide in the Docs folder covers the particulars of the file format.

-tkyler

Awesome Thank you so much,

I did try including the DCT but the format was wrong.

This is exactly what I had to do for the JAR A330.

WIll try again after landing in Vancouver

[Richdem]

1 hour ago, Richdem said:

Awesome Thank you so much,

I did try including the DCT but the format was wrong.

This is exactly what I had to do for the JAR A330.

WIll try again after landing in Vancouver

All working now

2nd leg of the day from CYVR to KSFO

Cannot get enough of this bird !

[Rodeo]

5 hours ago, tkyler said:

Page 11 of the Interface Guide in the Docs folder covers the particulars of the file format.

It doesn't cover wether latitude/longitude coordinates are supported, and how they should be formatted if they are