Jump to content

Briant

Members
  • Posts

    100
  • Joined

  • Last visited

Posts posted by Briant

  1. Hi All

     

    Having the same issues. I note that it has not been tested on W10. Am running W10 Pro Build 10240. Was running previously on W8.1 Pro. 

     

    Installation, activation runs ok. Error encountered when trying to run the DU. Same error message:

     

    Thanks and regards

    OK I was on build 10166 when I last replied I've now upgraded to TH1 Professional 10240 and that's working fine as well I can post screen grabs of my settings if anyone wants them 

     

     

  2. I suppose something has change internally in Windows that doesn't play nicely with EFB. I have these settings attachicon.gifCapture.PNG

     

     

    That's my guess. I get this weird letters as well attachicon.gifCapture 1.PNG.

     

    Thank you for the offer. I have another PC with Windows 7, but because P3D is not installed there, I wont be able to install the DP, right? I might try it the other way around (DU on W7 and DP on W10) and see how that goes. 

     

    Regards

     

    Jerry

    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.

  3. [attachment=0]Untitled.jpg[/attachment]

    I used A320/321 Aerosoft not Airbus extended.

    Where you can choose export function ?

    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.

  4. 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.

  5. 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

  6. 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

  7. 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.

  8. 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

×
×
  • Create New...