tomcjones

Urs I am sending you more information via support. You will get it shortly

Sirs When I try to attach the efbr file I get a message saying "The extension efbr is not allowed" so i do not know is the file actually got attached. So I copied and pasted the content of the efbr file below. Tom [AivlaSoft EFB Route - www.aivlasoft.com] //Saved 3/14/2013 2:22:32 PMz, EFB Version=1.3.7.21189 //AIRAC cycle 1101 / Rev.1, Valid 13/JAN/2011 - 09/FEB/2011 Format=1 ATS=KDAL GARL3.GGG AWDAD6.BTR KMSY Generator=ATS Description Origin=KDAL Destination=KMSY CruiseAltitude=33000 DepartureProcedureInfo=13R|GARL3|GGG| ArrivalProcedureInfo=10|AWDAD6|BTR ApproachProcedureInfo=10|RNAV Rwy 10Z|RQR [END]

I will send you the plan today. Tom

Sirs OS is Win7 64 bit Ultimate The attached IFly flight plan contains no SID, STAR or waypoints. This is a first time installation using OS Win7. I had no problems with OS Win XP. Just a guess but it may be an Export Module problem. I have done 3 installations very carefully going by your installation procedures. When I load the KDAL-KMSY file into the IFly FMC it get only the origination and destination airports in the FMC. It appears to be the same on any aircraft when I try to load the file. Help Pleas Tom

I just emailed, KDFWKSEA001.rt2., to support. Thanks Tom

I have Aivlasoft ver 1.3 Navigraph cycle 1103 for Aivlasoft and the PMDG 747-400. I have not been able to make a flight plan that is correct. I can make a flight plan using the Aivlasoft software being careful to put in the departure rwy and destination rwys. I then save the plan as an rt2 file using both the airport and procedures option. I save the plan to the PNDG Flightplan folder as an rt2 file. File is like KDFWKPHL001. I then bootup the PMDG 747 and put KDFWKPHL001 into the FMC scratch pad and click on co Route. The FMC processes the file but many of the waypoint that are in the Aivlasoft file are missing errors show in the scratch pad . Sometimes when processing other Aivlasoft flight plans files with the PMDG 747 FMC I may get only two or three of the waypoints. Am I missing a file? Help would be appreciated Tom

Hello The Flightplan folder for the LD 767 resides in the LevelD folder under navdata/flight plans. When I make a flight plan with AlviaSoft, the plan is saved to the default FS flight plan folder with a .pln extension. If instead I save the ALviaSoft flightplan to the LevelD folder as mentioned above, boot up the LD767, I cannot load this plan into the LD 767 FMC for reason I do not know. Comments from anyone appreciated Tom

The flight plan is an FSX plan I assume from what you are saying that once you have prepared a flight plan exactly as you want it and press the SAVE button, you cannot save the flight plans as KDFW-KPHX-1 and make it work with the CoolSky MD80 FMC.

Sirs Per the CoolSky MD80 manual, one form of flight plan must be as follows: KDFW-KPHX-1. Is is possible to save a plan with your program in the above format. If so, please tell me how. Regards Tom

Thanks for the inputs. I looked at those files and I just could not figure them out. When in doubt reinstall. I reinstalled FSC version 8.6 and she works great. Must have been some missing or corupted files in the folder. Actually I dont use FSC any more but EFB instead. I would have to rate EFB much higher than FSC although FSC is a great program. Tom

Hello I have been using EFB for some time now and I have not tried to load FSC until today. FSC want load. It gets just to the point of showing the map then the program goes back to desk top. Would this problem be related in anyway with EFB? Open for suggestions. Regards Tom

The ATC routing is very nice. As you know FlightAware gives the exact flight plan of and aircraft on a particular flight. All I have to do is copy the FlightAware flight plan to clipboard and past it in EFB as an ATC route and make a few changes to make it work. I also use Flight Commander to create flight plans for FSX, convert them to XML format and load them into EFB. I really do not think Reality GNS 430/530 will load EFB flight plans, however in my first post I find that EFB can read a GNS430/530 flight plan. On the GNS 430/530 you right press the mouse on the FLP button and that saves the plan to the default FSX flighplan folder.

Hello I was really suprised that by using the Reality GNS 430/530 that I could create a flight plan that EFB can read. That is great Flight plans created with the GNS 430/530 have very strange names and they reside in the same default folder as all FSX flight plans. The manual describes how to load EFB flight plans into the Garmin. I assume that this is the default gps unit. I have replaced all the default gps's with either the Reality GNS 430/530. My question is can a flight plan cereated by EFB be loaded into the Reality GNS 430/530. If this is possible how is it done. Best Regards Tom

Problem solved. When all else fails make a backup copy of your FSX.CFG file and then delete the FSX.CFG file. Reboot FSX and it will build another. Thats what I did and now the program in running very smooth with no stutters on my second monitor. Just a slight hit of FPS which is to be expected. There are all kinds of recommendations on how to change the FSX.CFG file for better performance. I believe my default CFG file is fine just as it is. This has got to be one of the top addon's for FSX. Tom

In my case as previously desctibed the stutters are in sync with the miniture aircraft moving along the EFB display. You can count on it every time. I have three other moving map programs where simconnect is used to show the miniture aircraft on the map. I run all of these programs on a seperate monitor, not a network. With these other programs on the second diaplay FSX runs very smooth The altitude and airspeed indications also stutter in sync with the miniture aircraft. I have run with no weather and all sliders set at minimal. That does not help. The only way I can run EFB without getting stutters is to run it on the same monitor as FSX. When running like this FSX runs very smooth. I always run FSX in the windowed mode. Regards Tom