IXEG 737 Flightplan Export Plugin for EFASS available

[mokny]

1. Same Airac Cycle in IXEG as in EFASS? 
2. Legs on airways that only consist of 2 points are interpretet as Direct by the IXEG, the airwayname won't appear in the FMC
3. Why don't you post the complete route here? Or better the file? It's hard to find out without details..

[helios123]

the export plugin seems not to work now.  

It seems the word 'DIRECT' needs to be on the fpl file.  For example EFASS Exported this:  KMIA SID WINCO LAL SZW MEI LIT TUL ICT SOSPE OATHE STAR KDEN

and it said "Point not found".

When I manually and save the route you get this:  KMIA WINCO DIRECT LAL DIRECT SZW DIRECT MEI DIRECT LIT DIRECT TUL DIRECT ICT DIRECT SOSPE DIRECT OATHE KDEN

[mokny]

In case you're not using airways, the route in EFASS itself should always look like WPT DCT WPT DCT WPT   ...

[helios123]

17 hours ago, Cosmopilot said:

In case you're not using airways, the route in EFASS itself should always look like WPT DCT WPT DCT WPT   ...

Are you saying that one has to manually put in "DCT" into EFASS?  Because EFASS does not automatically do that if you auto find route, nor if you grab a route from other services.  Wouldn't it be better to have the export plugin fill in the "DCT" where required?

 

thanks

Edited June 28, 2016 by helios123

[mokny]

Dependant on where EFASS got the route from (route cloud for example), there may be no DCTs inside. But following the rules, the DCTs should be present. I won't update the plugin anymore, as the new EFASS-Version is on the way and it will be more strict on route formatting. Looking forward to this (The export plugin for the IXEG is already included)...

Edited June 28, 2016 by Cosmopilot