NedHamilton

Once again the default directory that Navigraph is using to install Data cycle 1407 for FSX has changed. If you are not careful the new data will be installed into a different directory than has been done in the past. You can look at the Settings->Navigation Data tab to see where the data is supposed to go and then change the location when Navigraph asks where to install.

The .NET 4.5 version on Windows 8 includes .NET 3.5.

Urs, Thanks just what I wanted.

Hi Urs, Does EFB DataProvider program read the runways.txt file when it starts or when a " Request for Airport" is received from DisplayUnit? Because if the runway.txt file is read when a request is received, I can leave the DataProvider running when I see that there is a missing airport assignment. Then edit the runways.txt file and then trigger a new request by asking for a new route. This way I won't have to stop and start the DataProvider when I edit the runways.txt file. By the way, this is a wonderful program. Extremely well written, robust, user friendly, intuitive, and broadly featured. Oh yeah, good support too!

When runways for an airport in the latest cycle don't conform to the runways in FSX, I know we have to edit runways.txt to fix this. But is there any way to find out which runways don't conform without running EFB and the data provider? Because if I'm flying to say LTBA which has non-conforming runways. I have to look at the messages in DataProvider window or the log file, then stop DataProvider, then edit the runways.txt file and then re-start the dataProvider program. Lots of work which would be easier if I could find out which runways EFB knows about for LTBA before I start the DataProvider program.

You have added an option to allowing saving a flight plan in a format that can be used by Prosim which is very useful. But there is a slight 'bug' or inconvenience. If a flight plan is saved to the Prosim companyroutes.xml file and that route is exactly the same as another route already in the companyroutes.xml file the new flight plan will be added with a numbered suffix as the route name. Prosim doesn't save any SIDs or STARs in its company routes so if a user changes an EFB route's SID or STAR and presses the save button, and if the user isn't careful, the new route will be saved in the Prosim routes even though it is the same as the previous one. Seems like if the flight plan is the same as an existing one in a Prosim company route it shouldn't be saved again.