Jump to content

srcooke

Members
  • Posts

    50
  • Joined

Everything posted by srcooke

  1. I created and named a waypoint H4010 in pfpx to indicate a half degree N40.30.0W009.30.0, you could use N40.33.0 W009.33.0 and name in a similar fashion.
  2. Within PFPX I created H4010 which when imported to EFB:
  3. Via the route data icon and user waypoints and airways, possibly within the user database.
  4. 4410N is contained in navdata with coords of N44.00.0W010.00.0 and can bee seen as a fix in EFB. Did you add 4410N as a custom fix in PFPX as it does not appear in its data set.
  5. Urs did point out that the five character limit does not support entries including minutes Ray, an arinc limitation for and seven characters I believe. Probably why the 'H' designated waypoints were introduced for NAT HLA.
  6. Try a different browser as the link is valid.
  7. Add ZYYZ_ADEP4_FLYTAMPA.BGL as an exclude in BglSceneryExclude.txt, located in Documents\AivlaSoft\EFB2\Server\DbBuilder\Base eg: file:ZYYZ_ADEP4_FLYTAMPA.BGL Rebuild the database
  8. Hello Pete, The add-ons.cfg is from a P3Dv4 install ? Regarding the airport map have you enabled Brandenburg in the Aerosoft configuration for the airport, otherwise I believe it is SCHONEFELD is depicted.
  9. It is likely track tango expired, you would have to cross 30 West no later than 0800Z. Either construct your route with the NAT coordinates to treat as random track or replan with the new release today.
  10. Did you create the route today in Simbrief or use a suggested route ?
  11. There is not a NAT 'T' currently on the 16th, the Simbrief flightplan is not valid.
  12. Mapping 04 to 04 and 22 to 22 works, thanks Urs. This is probably the best option as the works are not 24/7 with a shift the runway thresholds at different phases with 04C/22C requiring RNP-Y approaches when active.
  13. Apologies Urs you are correct, SID's are only available for the primary 04/22 runways. I guess we'll see in the NOTAM's at the time whether these procedures are suspended as there i s no reference in the AIP Supplement.
  14. Hello Urs, For me this is occurring in P3Dv5 where the runways are listed as 04/22 in the afcad. The Navigraph airac data for other addons contains the runway entries for 04/22 and 04C/22C with SID/STAR and all approaches. EFB however only lists runway 04C/22C.
  15. I'm guessing you are using the LVFR scenery for Miami? Did you try excluding ZMIA using the exclusion file as posted by Urs. Personally I exclude the errant file ZMIA_ADEP4_RGM.bgl by adding the entry in the database exclude file BglSceneryExclude.txt, file:ZMIA_ADEP4_RGM.bgl as documented.
  16. In what respect ? If using the Flytampa addon how have you configured the runway use which will affect the EFB display.
  17. It would appear the ILS approach procedure to RWY07R has been withdrawn across airac providers. I cannot however find a source to confirm that currently as the Vietnam AIP is not accessible.
  18. I update on every AIRAC cycle Ray so as to match Navigraph. Herve also publishes an ILS/Runway update for v5 available on request by email, this updates stock data only and not that of third parties.
  19. The VOR still been retained in the P3D scenery may account for the difference I see Ray as my own sim is updated with Herve Sors navdata updates.
  20. It looks like the sim scenery.cfg located programdata has not been read due to an error.
  21. 2106 rev3 has been released and fixes the missing SID/STAR, tested in P3D.
  22. @DGF222 the rev2 of 2106 incorrectly identifies as rev1. Rev2 has problems as posted and needs a fix from NG.
  23. REV2 of NG 2106 has introduced the issue as posted on the Navigraph forum.
×
×
  • Create New...