Briant

i've got 393295

DP has to be on the Flight sim computer but the DU can be anywhere on the same network. I've just downloaded the demo and installed it on my Win10 pc which has the steam version of FSX on it and both the DP and DU are working fine on there with no issues I can see at all. I'd go with Urs suggestion and check your .net stuff.

Hi Jerry I am running the data provider on a Windows 7 pc and the display unit on a windows 10 and that works fine so maybe there is an issue with the DP running on windows 10. I don;t think my license will allow me to install on another computer otherwise I'd load it up and try it for you.

I've got the display unit working on My Win10 installation so I can't see why it wouldn't work on Win8.1

Try installing the display unit on the same PC as the dataprovider and make sure that it all works fine. then re-install the display on your other PC making sure that any AV is switched off first.

You may also wish to check this out viewtopic.php?f=5&t=1844

[attachment=0]Untitled.jpg[/attachment] I use the same. You should have an option as below to save to Aerosoft X when you tick the box you can change the path to save the file to. Ignore the name Airbus x just make sure the path is set to your a320/321 folder.

Do you mean an export function in EFB? if so there is one there already. Use the Airbus X Extended and change the path

Glad to help

I hope it helps. Even if router expires the lease on an ip address the device name never changes and so the connection should remain.

If I'm reading this correctly it seems like you are using an IP address on your Display (client) On the Client open the EFB display, go to settings/TCP Communications and change the "Server Name or IP-address" to the be the name of the computer instead.

did you use PFPX to create the flight plan? if so then there is an issue with the way PFPX presents the star to EFB. (incorrect runway assignment) If you open it in EFB then save it as an EFB file and then open that new file you should then be able to select the star.

Hi Marty, you don;t mention what aircraft you're importing the fp to, but most don't import sid's and stars as these would normal be added after instruction from atc and after the fp had been loaded.

On your dataprovider screen, click on data and then (simulator scenery data update) this will re-scan your scenery and add the new scenery. you'll need to do this every time you add new scenery.

Once you've activated your route and you have the options of Ground/Departure/En-route/Arrival/Approach/Ground displayed along the top of the screen, then towards the bottom of the screen there should be a tool-bar with icons of a plane, 2 magnifying glasses, 4 arrows, a half moon and 2 other symbols. Click on the plane symbol and the map will follow your aircraft

Hi Ray, I'm using Nav cycle 1501 and I can choose either runway 05 or 23 with a choice of 2 ILS procedures for 05 and 1 VOR/DME for 05

If you are running the display Unit on a separate PC then you need to go into the settings/TCP Communication on the display unit in the server mode box tick the remote button and in the server name box underneath this type in either the ip address or the pc name of the computer that the data provider is running on. If you are running both on the same machine then just make sure "local" is ticked in the settings/tcp communications of the Data Provider

Hi Peter, I had this until I downloaded the update (v3) to the 1413 AIRAC

Well the response from Ian at Navigraph is that the BROK1Q SID should only be assigned to 05R and not 23L therefore the issue is with PFPX as regards UDBA1A at NZQN this has now been incremented to UDBA1B I guess the original problem of the exception is becasue of EFB being presented with an invalid SID/STAR so from that point of view it's an easy fix for me to save in efb and then open it again. Is it possible one day maybe if the error in EFB could state "invalid SID/STAR? that would at least help troubleshooting.

Thanks Urs, should I let them know?

Ok well progress now I know where to look (thanks Mike) Flight plan from PFPX DepartureProcedureInfo=23L|BROK1Q|KAPAI| ArrivalProcedureInfo=23|UBDA1A|DOVOT Flight Plan after activating and saving in EFB without making any changes DepartureProcedureInfo=||| ArrivalProcedureInfo=|| As you can see from the extract from the files in bold PFPX is exporting the file with the Departure and Arrival procedure filled in. On this particular occasion this is what's causing the error if I manually delete the procedure from the txt file and then re-import the PFPX file, then EFB can select the SID just fine. On further investigation it appears that PFPX is assigning 23L as the departure using the BROK1Q SID. However EFB does not give the BROK1Q SID as an option when 23L is selected. if you change the PFPX file to show 05L as the departure then EFB will work fine and correctly and automatically assign the BROK1Q SID. I should add that I am running the latest AIRAC 1413 from Navigraph So I'm not sure if the problem is within PFPX in that it's assigning the BROK SID to 23L or if EFB is wrong in that it doesn't have the BROK SID for use with 23L Slightly less confused but feeling happier Hopefully Urs can shed some more light

Thanks for that Mike, I can also confirm that if I use another method to create the same route I don't get the exception error....JUst need to figure out now what in the PFPX flight plan is causing the error!

Hi Urs I have experienced the Unhanded Exception error also. I've attached the flight plan plus the txt file and the error occurs when I try to select a SID for NZAA. The SID Overview works fine. I would appreciate your advice on this problem Regards Brian