Jump to content

Exporting flight plans from efass


ptwparkinson
 Share

Recommended Posts

Why do you export the flight plan in all formats in the coroute folder?

For exemple, the path of X-Planeflight plan should be for you C:\User\woodsie50\Desktop\X-Plane 10\Output\FMS plans (by the way, the IXEG don't need a flight plan here, only in the coroute). iFly Boeing has nothing to do in the coroute folder, etc

Then the IXEC should be installed in X-Plane/Aircraft/X-Aviation, not in ExtraAircraft.

Claude.

 

Link to comment
Share on other sites

  • 2 weeks later...

I typed your suggestion into EFASS for the path -- I put the 737 into the x-aviation folder --- still says file not found ( not showing on this attachment but I replaced the one shown )

The other thing is that on Wycliffe Barretts video he says

Press menu

Press FMC

Press pos in

Then I think you type into the scratchpad your departure AP and add that to top left -- this gives you co ordinates of where you are -- click the co-ords on the right and they appear in the scratchpad and then there should be empty boxes where you put the co ordinates from the scratchpad ----- well , I never see these empty boxes --- might this be a clue --- if I cant get this sorted I will just give up on x plane until x plane 11 is released and start over ---- how on earth will we move all our sceneries like the Horizon UK scenery and all of the payware AC , the free AC and free sceneries into x plane 11 --- and there is another whole question !!!x plane export from efass.JPG

Link to comment
Share on other sites

This is in notepad from the ixeg co routes folder --- does it make any sense to you ??

 

Kind regards

Paul Woods .

 

company        =    "IXEG",
name        =    "DDHDDF",
depA        =    "EDDH",
arrA        =    "EDDF",
depRwy        =    "05",
sid            =    "AMLU7C",
sidt        =    false,
route        =    {
                    {via    =    "DIRECT",     to    =     "AMLUH"},
                    {via    =    "UM852",    to    =    "ULSEN"},
                    {via    =    "T155",        to    =    "ALOSI"},
                    {via    =    "T157",        to    =    "KERAX"}
                },
start                =    false,
star                =    false,
appt                =    "KE07S",
app                    =    "ILS07C",
arrRwy                =    "07C",
rwyX                =    false

Link to comment
Share on other sites

This is a file or folder in the ixeg folder entitled IXEG_FMS_debug.txt ---- does this give any clues ( the other thing is that I can`t delete all of the flywithlua stuff --- maybe this is getting in the way )

path to this was X-Aviation to IXEG 737 Classic to IXEG_FMS_debug.txt

 

 

 

====================================================================================================
                                           ROUTE SUMMARY
====================================================================================================
ROUTE STATUS:  initial

Using version: 1.0.6
DEPA:        EGCC
ARRA:        EGBB
CRUISE:   None
PERF:     Data is not complete
SID:      None
SIDT:     None
START:    None
STAR:     None
APPT:     None
APP:      None
DEP Rwy:  None
ARR Rwy:  None

Plane is on the ground
Current Altitude:  25.8 ft.

Route has no points

====================================================================================================
                                        PRINT 2 SHELL OUTPUT
====================================================================================================
LNAV: TK: Successful Arrival airport match, EGBB loading procedures into arrA
LNAV: TK: Successful Arrival airport match, EGBB loading procedures into arrA
default: TK: Looking for coroute EGCCEGBB
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: egccegbb
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute EGCCEGBB
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: egccegbb
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: Looking for coroute FILE NOT FOUND
default: TK: Building list of all files in coroute folder
default: TK: iterating 1 files for coroute: file not found
default: TK: EXEC pressed
====================================================================================================
                                           CDU KEYLOGGER
====================================================================================================
CDU Key: INIT REF
CDU Key: MENU
CDU Key: LSK 1L: <FMC
CDU Key: LSK 1L: 737-300
CDU Key: LSK 6R: POS INIT>
CDU Key: E
CDU Key: G
CDU Key: G
CDU Key: CLR
CDU Key: CLR
CDU Key: C
CDU Key: C
CDU Key: LSK 2L: ----
CDU Key: LSK 2L: EGCC
CDU Key: LSK 6R: ROUTE>
CDU Key: RTE
CDU Key: LSK 1L: -----
CDU Key: LSK 1L: EGCC
CDU Key: CLR
CDU Key: CLR
CDU Key: CLR
CDU Key: CLR
CDU Key: B
CDU Key: B
CDU Key: LSK 1R: #####
CDU Key: LSK 1R: EGBB
CDU Key: LSK 1R: EGBB
CDU Key: LSK 1R: EGBB
CDU Key: CLR
CDU Key: CLR
CDU Key: CLR
CDU Key: CLR
CDU Key: C
CDU Key: C
CDU Key: E
CDU Key: G
CDU Key: B
CDU Key: B
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: MENU
CDU Key: LSK 1L: <FMC
CDU Key: LSK 6R: POS INIT>
CDU Key: LSK 6R: ROUTE>
CDU Key: RTE
CDU Key: LSK 6R: ROUTE>
CDU Key: LSK 6R: 
CDU Key: PREV
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: CLR
CDU Key: CLR
CDU Key: E
CDU Key: G
CDU Key: C
CDU Key: C
CDU Key: E
CDU Key: G
CDU Key: G
CDU Key: CLR
CDU Key: CLR
CDU Key: B
CDU Key: B
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: LSK 2L: ------
CDU Key: EXEC
====================================================================================================
                                         VERTICAL PATH DATA
====================================================================================================
No valid End of Descent Index, no data exported
====================================================================================================
                                      DESCENT GRADIENT SUMMARY
====================================================================================================
  Name    dGrad1    dGrad2   dGrad3
 

IXEG_FMS_debug.txt

Link to comment
Share on other sites

Still not exporting --- I created a new flight plan egcc to eglc and pressed export in efass --- you will see that it did not export the legs ???

Also why is LUA still showing in the plug ins when I have deleted form my hard drive ?? And could this be causing the problem

This what I do 

press menu

press fmc

press pos in on lsr and put the position in the scratchpad then I press route and in wycliffes tutorial a line of empty boxes appear and you are suposed to put the pos from the scratchpad into the lsr which fills these boxes with the pos --- but the empty boxes do notr show on my fmc

type in destination egcc and press top left for airport

type in eglc and press lsr for destination which fills in the boxes

type in egcceglc and press co route lsl and save then ececute and the whole flight plan shoud be there but all I get on therte page is HON and DTY and none of the legs -- the whole thing is weirder and weirderx plane fmc showing lua and track wycliffe.JPG

x plane fmc plug ins wycliffe.JPG

x plane fmc efass page wycliffe.JPG

x plane fmc route wycliffe.JPG

x plane fmc pos in wycliffe.JPG

Link to comment
Share on other sites

1 hour ago, ptwparkinson said:

Nothing showing in here

x plane fmc lua plug ins for wycliffe.JPG

You have extracted the FlyWithLua folder directly in the plugins folder. That can mess things up.

FlyWithLua folder structur is this:

4Rw1P4X.png

 

So you should clean up your plugins folder. Pretty sure the 32 and 64 is the FlyWithLua in your plugins folder.

 

Edited by Tom Stian
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...